fsck died with exit status 8

[aged hippy]

I've decided to dual-boot Hardy, i have a long-lasting (for me ) Hardy 3.5.10 install on sda 2 & 3, and have now installed it also on sda 5 & 6, and will install the kde4-core and bits-and-pieces later on tonight (when it's free).

Booting back into 3.5.10. the boot process dies, and leaves the following error log:

Log of fsck -C3 -R -A -a
Sun Oct 12 22:52:52 2008

fsck 1.40.8 (13-Mar-2008)
/dev/sda3: clean, 70451/2506752 files, 1616226/10010503 blocks
/dev/sdb2: clean, 66045/1228800 files, 1331972/4905849 blocks
/dev/sda7: clean, 69876/2809856 files, 1907105/11229427 blocks
fsck.ext3: Unable to resolve 'UUID=41adfbe1-6002-426c-b129-927d5c4cf261'
fsck died with exit status 8

It's having problems finding either sda 5 or 6, which is where the new install dwells.

Could someone help me out with some guidance, please?

[dibl]

Re: fsck died with exit status 8

When you format a partition, it changes the UUID number.

So, you need to run

sudo blkid

and then fix /etc/fstab

[aged hippy]

Re: fsck died with exit status 8

What it tells me is:

/dev/sda1: UUID="EA04DAC004DA8F47" TYPE="ntfs"
/dev/sda2: UUID="2105df24-f2bf-4416-bc32-4d8a385c5abf" TYPE="ext3"
/dev/sda3: UUID="5fd29541-b5b4-4acd-a586-c10615c2c6f2" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda5: UUID="58fd6ec2-bfe6-4f41-b07a-b8f2b2feeb4f" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda6: UUID="a9888695-3e70-426b-af33-5a7bbfd316af" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda7: UUID="6215f702-718b-4d4d-92ee-843dc63728ec" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda8: TYPE="swap" UUID="7b41826a-74e6-48b7-93a0-42f78e9eacc2"
/dev/sdb1: UUID="2BDAE8CE1FBBF0FB" TYPE="ntfs"
/dev/sdb2: UUID="853570ad-1e59-427b-80e6-8915ddb0bdba" TYPE="ext3" SEC_TYPE="ext2"

and the fstab says:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda2
UUID=2105df24-f2bf-4416-bc32-4d8a385c5abf / ext3 relatime,errors=remount-ro 0 1
# /dev/sda3
UUID=5fd29541-b5b4-4acd-a586-c10615c2c6f2 /home ext3 relatime 0 2
# /dev/sda6
UUID=41adfbe1-6002-426c-b129-927d5c4cf261 /usr/local/Local-home ext3 relatime 0 2
# /dev/sdb2
UUID=853570ad-1e59-427b-80e6-8915ddb0bdba /usr/local/Non-local ext3 relatime 0 2
# /dev/sda7
UUID=6215f702-718b-4d4d-92ee-843dc63728ec /usr/local/Storage ext3 relatime 0 2
# /dev/sdb1
UUID=2BDAE8CE1FBBF0FB /windows/Non-local ntfs defaults,umask=007,gid=46 0 1
# /dev/sda1
UUID=EA04DAC004DA8F47 /windows/XP ntfs defaults,umask=007,gid=46 0 1
# /dev/sda8
UUID=7b41826a-74e6-48b7-93a0-42f78e9eacc2 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

I'm unsure of how to actually hack fstab; i can see that the UUID numbers go there somewhere, but....

[dibl]

Re: fsck died with exit status 8

OK, you can consider the blkid output to be "current reality" and the /etc/fstab numbers to be "was real when originally installed". For example, blkid shows

/dev/sda6: UUID="a9888695-3e70-426b-af33-5a7bbfd316af" TYPE="ext3" SEC_TYPE="ext2"

but in /etc/fstab, /dev/sda6 is shown as:

# /dev/sda6
UUID=41adfbe1-6002-426c-b129-927d5c4cf261 /usr/local/Local-home ext3 relatime 0 2

So, you want to open a kate session in Super User mode, via Alt-F2 "kdesu kate /etc/fstab" with no quote marks. Now leave your Konsole window with the blkid output showing, and then you copy from the console and paste into kate, and you make sure and delete the quote mark as that is a deal killer. So you will copy:

UUID="a9888695-3e70-426b-af33-5a7bbfd316af

into /etc/fstab, over top of the old UUID for /dev/sda6, and then you will delete that quote mark, and then you will click "save" to keep it. Do that for each partition that is wrong in /etc/fstab, so they all match what blkid says.

Then you can close kate and in Konsole issue

sudo mount -a

and they will be mounted correctly.

8)

[aged hippy]

Re: fsck died with exit status 8

Thank You, very much indeed, dibl.

[dibl]

Re: fsck died with exit status 8

You are quite welcome. For the benefit of future readers, please edit the title on the original post and insert the word "SOLVED" at the front -- thanks!

[Guest]

I would like to thank dibl.

This solved my problem when I were installing Debian on FakeRaid (Raid 1) with a boot partition and a LVM with swap and a ext4 for data on.

Sorry for the bump but I think that my addition may help other users find this topic much easier.

Don't add the boot partition at all to the /etc/fstab as it didn't work for me.

Also FYI Debian users use nano instead of "kdesu kate"