Announcement

**oshunluvr** · Jan 07, 2014, 08:59 AM

You messed up because you don't want sdb1 to be extended, correct? Well, I see several issues I would correct, but let's start with sdb1: Simple enough to copy the contents of sdb1 somewhere (thumb drive or other partition), delete and re-create sdb1, copy the files back. Once you have to delete and then re-create sdb1, the partitions will goes through a re-numbering, leaving them in the wrong order, but fdisk will correct them with the "f" command from the "x - experts only" menu.

This should be able to be done without booting to a Live USB or CD, but you should have one handy just in case. Be aware that fstab and grub use UUID's to mount/select filesystems and when you re-format a partition, it gets a new UUID. If you create your new filesystem(s) using the terminal and mkfs.ext4, you can specify a particular UUID. Here's what I would do:

1: open a terminal, type sudo blkid -s UUID /dev/sdb1. Write down or copy the current UUID.
2: copy the entire contents of sdb1 somewhere.
3: run sudo fdisk /dev/sdb and delete sdb1. recreate sdb1 as a linux (rather than extended) partition (type 83), then do "x" and then "f" to correct partition order. exit fdisk.
4: run sudo fdisk -l and verify visually that your partitions are in the correct order before proceeding.
5: run mkfs.ext2 -U <INSERT UUID HERE> /dev/sdb1 to create your new filesystem.
6: copy the contents of sdb1 back to the new sdb1.

This should work.

The other problems I see are:

#1: Why have a separate /boot partition at all? This used to be a common practice but is no longer recommend unless you are using a filesystem grub does not recognize or possible RAID or encryption. Copying the contents of sdb1 into the /boot partition on sdb2 and running update-grub should leave you bootable without sdb1 needed.

#2: Why the reverse format selection? If you require or desire a separate /boot along with / and /home; /boot should be ext2 and / and /home should be ext4, not the other way around. ext4 offers some data loss protection and benefits. ext2 does not but operates with less reserved space and a bit quicker.

#3: Using the MBR drive format with your current partitioning scheme will leave that unallocated 110GB unused forever. I suggest once you reformat sdb1 that you delete sdb4, re-create it as an extended partition, then recreate your swap as a logical partition. Then if you want to use the rest of your disk, you need only add more logical partitions. Note that the -U switch works for mkswap just like it does for mkfs so you should do it the same way as above to reain the UUID and avoid having to edit fstab and/or grub.

**Bumpalot** · Jan 07, 2014, 12:13 PM

SUMMARY OF SEQUENCES:
Current kubuntu drive:

Please excuse my lack of knowledge on this topic - am a newbie trying to learn the fundamentals!!
NOTE: The previous snapshot was the original format before Fstab changed it.
1. Open a terminal, type sudo blkid -s UUID /dev/sdb1. Write down or copy the current UUID.
Done: UUID="38DC9DBDDC9D75BA"
2. Copy contents of sdb1 (using Dolphin-Split screens)
Copied to /Data Storage/Copy_of_sda1
Unable to copy any System.map files (3) or vmlinuz****. Files (2) (Could not read)
I AM STUCK HERE !

After the above is completed, my interpretation of your excellent suggestions is as follows:
3. run sudo fdisk /dev/sdb <<this returns Command (m for help): fdisk help f: unknown command.

(and delete sdb1.
Recreate sdb1 as a linux (rather than extended) partition (type 83),
then do "x" and then "f" to correct partition order.
4. Delete sdb4 (swap)
5. Re-create sdb4 as an extended partition.
6. Create swap as a logical partition.

Then if you want to use the rest of your disk, you need only add more logical partitions.
MY NOTE: Is the following switch for using fdisk ? If so what would the command be?
Note that the -U switch works for mkswap just like it does for mkfs so you should do it the same way as above to regain the UUID and avoid having to edit fstab and/or grub.

**oshunluvr** · Jan 07, 2014, 12:59 PM

#2: Those files are owned by root, so you have to be root to move them. In a terminal, type kdesudo dolphin and this will get you a root file manager

#3: This is the correct response: "Command (m for help):". You would then type "m" for the list of commands, and use this program to delete and create partitions among other things. The instructions to do "x" will bring up the "Advanced" options, and then "f" will correct the partition number sequence. DON'T DELETE sdb1 until you have saved the files using step #2.

A little basics about how partitioning and file systems work using Linux (when you use Windows, all of this is done, just without you knowing it or having any control over it):

When you split up the space on a drive, that is called a partition. A partition cannot be accessed directly because the system doesn't know how you want it to do that. So we must create a filesystem. With Linux, you have many - dozens - of different filesystems you can choose from. Why you would choose one over the others has mostly to do with what you are going to store in the filesystem. For general purposes (and certainly for a beginner

) stick with ext2/4 as they are the most common. I recommend using ext4 except for small devices like thumb drives or for /boot partitions. For these use ext2 for /boot and ext2 or fat32/ntfs for thumb drives if you need windows compatibility.

So to recap: a portion of space on a drive is a partition. On these partitions, we create filesystems. Files are stored in a filesystem - not on a partition.

fdisk is a partitioning program. It does not create filesystems (also known as formatting). fdisk only manipulates drives at the partition system level. Once you created a partition, you must then create a filesystem on it so you can use it.

mkfs (MaKe File System) is the command (actually a set of scripts) that creates the filesystems. We use mkfs.ext2 for ext2 and mkfs.ext4 for ext4. There are a series of options available you can list by typing mkfs.ext4 --help . One of these options is to set the UUID as I suggested in the previous post. To create swap partitions, the program is mkswap. You must have root privileges to use these programs, so you preface the commands with sudo: The command to format /dev/sdb1 with ext2 is sudo mkfs.ext2 /dev/sdb1 and so on. Also, the filesystem you are formatting or re-formatting must not be mounted for these to work. To unmount /boot, you would enter sudo umount /boot and to redo the swap partition the command is sudo swappoff --all

The -U switch does not work using fdisk because fdisk does not create filesystems and therefore does not create UUIDs.

**Bumpalot** · Jan 07, 2014, 02:17 PM

PROBLEM:
kdesudo dolphin returns:

Code:

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Keywords in "/usr/share/applications/firefox.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/calc.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/draw.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/impress.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/math.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/writer.desktop" is not compliant with XDG standard (missing trailing semicolon). 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QObject::connect: Cannot connect (null)::resourceScoreUpdated(QString, QString, QString, double) to NepomukPlugin::resourceScoreUpdated(QString, QString, QString, double)
QObject::connect: Cannot connect (null)::recentStatsDeleted(QString, int, QString) to NepomukPlugin::deleteRecentStats(QString, int, QString)
QObject::connect: Cannot connect (null)::earlierStatsDeleted(QString, int) to NepomukPlugin::deleteEarlierStats(QString, int)
kactivitymanagerd(6698)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.kde/share/config/activitymanager-pluginsrc
QPixmap::scaled: Pixmap is a null pixmap
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting                        
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting                        
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting                        
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting                        
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.   
QDBusObjectPath: invalid path ""                                                                        
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

How can I correct the above errors?

Despite this, I was able to save the grub files.

**Bumpalot** · Jan 07, 2014, 04:55 PM

oshunluvr - this problem was not answered! How can I correct these errors?
kdesudo dolphin returns:

Code:

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Keywords in "/usr/share/applications/firefox.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/calc.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/draw.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/impress.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/math.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(6691) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/writer.desktop" is not compliant with XDG standard (missing trailing semicolon). 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QObject::connect: Cannot connect (null)::resourceScoreUpdated(QString, QString, QString, double) to NepomukPlugin::resourceScoreUpdated(QString, QString, QString, double)
QObject::connect: Cannot connect (null)::recentStatsDeleted(QString, int, QString) to NepomukPlugin::deleteRecentStats(QString, int, QString)
QObject::connect: Cannot connect (null)::earlierStatsDeleted(QString, int) to NepomukPlugin::deleteEarlierStats(QString, int)
kactivitymanagerd(6698)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.kde/share/config/activitymanager-pluginsrc
QPixmap::scaled: Pixmap is a null pixmap
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting                        
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting                        
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting                        
dolphin(6676)/nepomuk (library): Could not find virtuoso to connect to. Aborting                        
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.   
QDBusObjectPath: invalid path ""                                                                        
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

After completing all the previous stuff, when I now open Dolphin, it is totally blank.
Shows small message "Could not start process Unable to create io-slave: klauncher said: Unknown protocol 'file'.

**Buddlespit** · Jan 07, 2014, 05:42 PM

Originally posted by oshunluvr View Post

#1: Why have a separate /boot partition at all? This used to be a common practice but is no longer recommend unless you are using a filesystem grub does not recognize or possible raid or encryption. Copying the contents of sdb1 into the /boot partition on sdb2 and running update-grub should leave you bootable without sdb1 needed.

uefi

**SteveRiley** · Jan 07, 2014, 05:48 PM

For UEFI, /boot does not need to be separate. UEFI does require a separate EFI system partition, with a FAT-32 file system, and this partition must be mounted at /boot/efi.

**Bumpalot** · Jan 07, 2014, 07:31 PM

Would you be so kind as to translate your message in beginner's terms - I have no clue what that means!
Will it get Dolphin back?

**Bumpalot** · Jan 08, 2014, 09:50 AM

MY UNDERSTANDING OF FORUM SUGGESTED ACTIONS BEFORE IMPLEMENTATION:
Current kubuntu 13.10 drive (as of 7.40am, Pacific Time Jan 8 2014):

CURRENT INFO:
Disk /dev/sdb: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004a04a
Device Boot Start End Blocks Id System
/dev/sdb1 2046 10000383 4999169 5 Extended
/dev/sdb2 * 10000384 209999871 99999744 83 Linux
/dev/sdb3 209999872 409999359 99999744 83 Linux
/dev/sdb4 409999360 410998783 499712 82 Linux swap / Solaris
/dev/sdb5 2048 10000383 4999168 83 Linux
SUGGESTED PROCEDURES
1. Open a terminal, type sudo blkid -s UUID /dev/sdb1
Write down or copy the current UUID. << DONE: UUID="0110cb19-48b1-49b1-95fa-a3cfeed1edf7"
2. Copy contents of sdb1 as follows:
Terminal: type kdesudo dolphin -this opens Dolphin as a root file manager.
Used Split Screen: Copied to /Data Storage/Copy_of_sdb1 folder << DONE
HAVE NOT COMPLETED THE FOLLOWING
3. run sudo fdisk /dev/sdb <result shows: Command (m for help): m
type m -(shows list of commands)
type d -(delete a partion) >> (removes sdb1)
type n -(creats a new partition)
NOT SURE HOW: > ?? recreate sdb1 as a linux partition (type 83) - rather than extended)
type x and then f -to correct partition order. Exit Terminal
4. In KDE Partition Manager:
a: Delete sdb4 (swap)
b: Type -U (makes swap )- Re-creates sdb4 as a logical partition
?? Will this happen automatically ??
YOUR NOTE> the -U switch works for mkswap just like it does for mkfs so you should do it the same way as above to regain the UUID and avoid having to edit fstab and/or grub.

5. Check swap – Terminal: sudo blkid -s UUID /dev/sdb4
to make sure it's the same as 0110cb19-48b1-49b1-95fa-a3cfeed1edf7

Please note: As a “novice-in training” I would appreciate confirmation/recommended changes on the above procedures before I implement them. Your input will be most welcome. Thanks.

**oshunluvr** · Jan 09, 2014, 01:20 PM

A reboot should bring the root dolphin back. Before I continue, please be sure anything you can't afford to lose is backed up.

fdisk is not a complicated program but it is powerful. Take a deep breathe to calm yourself and take your time. If this is too concerning for you, maybe waiting until your next install would be easier on you. However, there's no time like the present. Look: We all learned to do these things by trying, messing up, breaking our installs, deleting important data, etc. Continue if you wish:

Step 3:
Copy your UUID for later use:

sudo blkid -s UUID /dev/sdb1

Copy the UUID.

Recreate sdb1 as a primary partition:

sudo fdisk /dev/sdb

starts you out by opening fdisk and nothing else. Type m to list the commands available. To complete step 3 you are simply going to delete partition 1, recreate it and exit. Here are the entries in bold and explanations of what each one does:

d > delete a partition
1 > select the first partition for deletion
n > create the new partition
p > for primary partition type
1 > the new partition number (same as the old)
enter (twice) > select default sectors for start and finish
p > print out (view on screen) your handwork

You will now see a list of your partitions and 1 will have the Id 83 rather than 5. Look at it and decide if you've done it correctly or not. NONE OF THIS HAS TAKEN EFFECT YET! You can still back out by typing q to quit.

To continue and commit to these changes:

w > write out the new partition table and quit

If you get a warning message about the partition table numbering order, you will want to fix that. However, you should be OK if you do all of it as I listed above. You will now need to create the file system on sdb1 and move your /boot files back to it.

sudo mkfs.ext2 -U <INSERT UUID> /dev/sdb1

Then launch dolphin using kdesudo and move the files back. At this point, I recommend you attempt a reboot into linux to make sure all is well before we continue with re-doing the swap partition.

**Bumpalot** · Jan 10, 2014, 07:35 AM

oshunluv-
Sorry to bother you again..
I opened dolphin with kdesudo dolphin & successfully copied /dev/sdb1 to a temp folder on a different drive.
Then I noticed bash had been busy doing this:

Code:

bumpy@bumpyputer:~$ kdesudo dolphin
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
"KConfigIni: In file /usr/share/kde4/services/muon-knsplasmoids-backend.desktop, line 113: " Invalid entry (missing '=') 
"KConfigIni: In file /usr/share/kde4/services/muon-knsplasmoids-backend.desktop, line 114: " Invalid entry (empty key) 
"KConfigIni: In file /usr/share/kde4/services/muon-knsplasmoids-backend.desktop, line 115: " Invalid entry (missing '=') 
kbuildsycoca4(2273) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/calc.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(2273) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/draw.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(2273) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/impress.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(2273) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/math.desktop" is not compliant with XDG standard (missing trailing semicolon). 
kbuildsycoca4(2273) KConfigGroup::readXdgListEntry: List entry Actions in "/usr/lib/libreoffice/share/xdg/writer.desktop" is not compliant with XDG standard (missing trailing semicolon). 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QObject::connect: Cannot connect (null)::resourceScoreUpdated(QString, QString, QString, double) to NepomukPlugin::resourceScoreUpdated(QString, QString, QString, double)
QObject::connect: Cannot connect (null)::recentStatsDeleted(QString, int, QString) to NepomukPlugin::deleteRecentStats(QString, int, QString)
QObject::connect: Cannot connect (null)::earlierStatsDeleted(QString, int) to NepomukPlugin::deleteEarlierStats(QString, int)
kactivitymanagerd(2280)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.kde/share/config/activitymanager-pluginsrc
QPixmap::scaled: Pixmap is a null pixmap
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)                  
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)                
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.   
QDBusObjectPath: invalid path ""                                                                        
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.   
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.   
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.   
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)                  
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)                
libv4l2: error getting pixformat: Invalid argument                                                      
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)                  
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)

I don't want to continue until I here from you, OK

**oshunluvr** · Jan 10, 2014, 11:25 AM

Personally, I don't see anything in there to worry about. Most or all those errors are related to the fact that that on a *buntu system, the root user has no real account (no desktop or associated settings). Any GUI program is going to search for config files and the like that just don't exist. I suspect many of those same messages will flow across the screen if you launch dolphin as yourself also. Most of them are harmless and meaningless except when you're having a problem. This is why, when trouble shooting a particular program, launching from the terminal is a good first attempt at finding out where the problem lies.

Oh, and by the way, when you launch dolphin using kdesudo, the blank screen you see at the start is the empty home folder of the root user. This is also normal.

**Bumpalot** · Jan 10, 2014, 05:33 PM

REALLY MESSED UP!

Sorry about that!
Hope my system keeps running long enough to get an answer!
If you don't get an answer Saturday, it will be Monday or Tuesday
before I get back to you as am moving to another place on Sunday.

Cannot find "code" icon to add the following:
This was the status after messing up:
bumpy@bumpyputer:~$ sudo fdisk -l
[sudo] password for bumpy:

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004a04a

Device Boot Start End Blocks Id System
/dev/sda1 2046 10000383 4999169 5 Extended
/dev/sda2 * 10000384 209999871 99999744 83 Linux
/dev/sda3 209999872 409999359 99999744 83 Linux
/dev/sda4 409999360 410998783 499712 82 Linux swap / Solaris
/dev/sda5 2048 10000383 4999168 83 Linux

Disk /dev/sdb (Sun disk label): 255 heads, 63 sectors, 14593 cylinders
Units = sectors of 1 * 512 bytes

Device Flag Start End Blocks Id System
/dev/sdb1 0 234340155 117170077+ 83 Linux native
/dev/sdb2 u 234340155 234436545 48195 82 Linux swap
/dev/sdb3 0 234436545 117218272+ 5 Whole disk

Disk /dev/sdd (Sun disk label): 255 heads, 63 sectors, 243201 cylinders
Units = sectors of 1 * 512 bytes

Device Flag Start End Blocks Id System
/dev/sdd1 562036736 528941057 2130935808+ 417 Unknown
/dev/sdd2 2956968255 399884607 868941824 7403 SunOS swap
/dev/sdd3 2567669076 2535163219 2131230719+ 7d88 Unknown
/dev/sdd4 u 475382079 3934334867 1729476394 be01 Boot
bumpy@bumpyputer:~$ sudo blkid
/dev/sdb1: UUID="38DC9DBDDC9D75BA" TYPE="ntfs"
/dev/sda2: UUID="0110cb19-48b1-49b1-95fa-a3cfeed1edf7" TYPE="ext2"
/dev/sda3: UUID="1a76da42-45d6-4662-9870-1c759cc6c039" TYPE="ext2"
/dev/sda4: UUID="b32b0388-d9c7-4b97-9de5-5794758b9071" TYPE="swap"
/dev/sda5: UUID="3cc8acfc-f516-4946-91a7-1e079719ab00" TYPE="ext4"
/dev/sdd1: LABEL="Local Disk" UUID="185C5BAF5C5B8682" TYPE="ntfs"
/dev/sdd5: LABEL="Data Storeage" UUID="14FC9FECFC9FC700" TYPE="ntfs"
bumpy@bumpyputer:~$

**oshunluvr** · Jan 10, 2014, 11:20 PM

How did you swap your a drive with your b drive?

Announcement

Drive Partition problem

Drive Partition problem

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment