Drive Partition problem

[oshunluvr]

fstab has to be edited manually. It's only automatically created at install. After that, it requires manual intervention. You can use the UUIDs or the device name (e.g. /dev/sda3) in fstab.

[Bumpalot]

CURRENT DRIVES AT JAN 11
According to KDE Partition Manager:
I can't believe this change from the screenshot I posted earlier this morning!

As long as I don't reboot, is it possible to edit this using KDE Partition Manager?
Am guessing here, so please advise accordingly..
Unmount all.
1. Remove sda1 extended partition.
2. Recreate sda1 as a primary ext2 partition /boot – 95 GiB (it already contains the boot files)
3. Copy files from /dev/sda2 to /dev/sda1
4. Delete /dev/sda2 & the extended partition
5. Delete /dev/sda3 & the extended partition
6. Create /dev/sda3 as ext4 /home – 95 GiB
7. Copy previously saved /home files to /dev/sda3
8. Remove /dev/sda4 & the extended partition.
9. Recreate swap as a logical partition.
10. Close Partition Manager.
11. Reboot.

Question: Will fstab change accordingly?
Have to complete this the above today as I have to pack the computer & all peripherals tonight,
so hopefully will receive your response. If not, on next reboot, I would imagine that fstab will have its way. Will cross that bridge when I come to it!!
Thanks again for your patience with an 80 years young guy!!

[oshunluvr]

Since you're starting over:

You need a / partition of about 20GB for the install. You need a partition for /home for your personal files. If you decide to use a swap, it should be the same size as your RAM.

[Bumpalot]

Sorry - don't know how this happened! Most likely because am exhausted getting ready to move Sunday.
I Guess I will have to reinstall kubuntu 13.10 from my CD on the same drive.?
As you said earlier - "Why have a separate /boot partition at all? Copying the contents of sdb1 (which I have) into the /boot partition on sdb2 and running update-grub should leave you bootable without needing sdb1"

I am going to take your advice! Unless you suggest otherwise, I will use KDE Partition Manager to create the 2 primary partitions plus swap.

However, this isn't going to happen until next Tuesday or Wednesday, as I will be busy unpacking at my new place!

Thanks again for your superb help - I really appreciated that!

[oshunluvr]

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

[Bumpalot]

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]

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]

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:

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]

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]

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.

[Bumpalot]

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?

[SteveRiley]

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.

[Buddlespit]

#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

[Bumpalot]

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

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'.

[Bumpalot]

PROBLEM:
kdesudo dolphin returns:

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.