$ cat fstab # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # #proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sdb1 during installation UUID=649ffd64-17b4-4a95-aebe-360413cc3203 / ext4 errors=remount-ro 0 1 # swap was on /dev/sdb5 during installation UUID=dfe16a55-80c3-42c8-937a-4341cb2886c8 none swap sw 0 0
Where is /dev/sdb6, which was /home?
I can't deal with this tonight. I can't feel too discouraged, after escaping from the botch-install hell of the last couple of days. Maverick looks and feels GREAT! It's just bizarre to have no settings, and no content whatsoever, not even my old backup. Amarok is lonesome with no music.
Maco asks, in IRC, if the partition is still on the harddisk, which of course has been my question.
sudo fdisk -ltells me:
Disk /dev/sda: 400.1 GB, 400088457216 bytes 255 heads, 63 sectors/track, 48641 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000c403c Device Boot Start End Blocks Id System /dev/sda1 * 1 2432 19530752 83 Linux /dev/sda2 2432 48642 371178497 5 Extended /dev/sda5 2432 2918 3905536 82 Linux swap / Solaris /dev/sda6 2919 48642 367271936 83 Linux Disk /dev/sdb: 7958 MB, 7958691840 bytes 245 heads, 62 sectors/track, 1023 cylinders Units = cylinders of 15190 * 512 = 7777280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ee8a7 Device Boot Start End Blocks Id System /dev/sdb1 * 1 1023 7769654 c W95 FAT32 (LBA) Partition 1 has different physical/logical endings: phys=(1023, 244, 62) logical=(1022, 244, 62)
At this point,
sudo blkid /dev/sda6to get the UUID for /dev/sda6, which says:
/dev/sda6: LABEL="home" UUID="1e3555c0-f248-446e-a9a7-6a42ab95eced" TYPE="ext4"Yay! It's still there on the disk, still with it's nice label. Thanks, Thomas!
Now it's time to edit fstab, and add the line:
UUID=1e3555c0-f248-446e-a9a7-6a42ab95eced /home ext4 errors=remount-ro 0 1
I did that by using Kate, which is somewhat unorthodox, but it's what I like.
kdesu katethen append the line above, save as fstab. Finally, I moved my present $HOME in case I need some of the settings or files from the last few days.
sudo mv $HOME /oldhomeand then restart. Let's see if it works!
===========
I want to report success! My /home is all happy, and my /oldhome dotfiles mostly copied back over. This time around, Chromium built OK, and I'm actually editing this blog in it now. Hallelujah, Maverick rocks! If I can build Amarok from source again, I'll be in heaven.
PPS: Amarok built without a hitch!
"kdesu kate" not "sudo kate" -- sudo is for command line stuff only
ReplyDeleteI will change my advice above to the correct command. Thanks, Maco!
ReplyDeleteCongratulations!
ReplyDelete