[Feisty]Bug with kernel 2.6.20 on AMD 64 : no way to boot

[Daniel Moyne]

Binary package hint: e2fsck-static

systematic failure of boot procedure after some good sessions ; termination on this error message :fsck died with exit status 12
difficult to know what is wrong ; tried to replace all UUID with /dev/device but no progress

[Daniel Moyne (dmoyne)]

I changed the UUID label in Grub in line :
kernel /boot/vmlinuz-2.6.20-15-generic root=/UUID=....
by :
kernel /boot/vmlinuz-2.6.20-15-generic root=/dev/sda1 ro quiet splash
and now it works.

So apparently there are some confusion with UUID labelling

[Daniel Moyne (dmoyne)]

Some more comments on evious message :
- The error message might be fsck died with exit status 8
- The correction in menu.lst for the relevant kernel line is to be re-done after each kernel update with the package manager.

[Theodore Ts'o (tytso)]

Can you send me the output of the "blkid" command (run as root), please?

This sounds like it may very well be a duplicate of bug #110138, but I'd like to confirm that. Thanks!

[Daniel Moyne (dmoyne)]

with kernel 2.6.20-16-generic this bug does not show up any more however this is the result of command blkid in my present setup :
root@azun:/home/dmoyne# blkid
/dev/sda1: UUID="bdba10ce-bfc4-41fb-bb39-25deca8024fd" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda1: UUID="579af963-1c96-4b98-b722-d83fc57a9ed5" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda5: UUID="48ffa9a3-d07a-467b-8984-84b804e9e5dc" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdb1: LABEL="/" UUID="9c4e237e-e9bb-491f-9c3f-f8226dd0dfe8" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdb6: UUID="b8790cc4-fef8-11d6-977e-97616905797f" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda2: UUID="9b99944d-3365-4bf5-a567-a025bb6be69c" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda3: UUID="15550516-805e-40dd-8431-db177c26c42c" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdb5: UUID="97d08cf4-fef8-11d6-914e-a02ea66c9c07" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda3: UUID="68d0b785-2bf5-4c82-87c9-469d46a5592f" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda5: LABEL="/home" UUID="02b87c1e-fb23-4b6e-953d-7cdf819a9fa9" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda6: LABEL="/usr/local" UUID="30c4529e-ca82-4a00-87d0-0808901d935c" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda7: TYPE="swap" UUID="a296c745-3387-46b1-be48-c30b6dd7d3ec"

I am surprised about the result as /dev/sda1 should have LABEL="/" as described in fstab ; /dev/hdb1 is "/" on a parallel monuted distro not this one.
Regards.

[Theodore Ts'o (tytso)]

The other distro happened to use the label "/". If you have parallel mounted distribution, using mount-points for labels can be very confusing.

In any case, if simply going to another kernel solved the problem, then this clearly isn't an e2fsck-static bug.

I am confused about how changing the kernel would cause fsck to bomb out, and changing the kernel boot option shouldn't make a difference either.

Can you send me your /etc/fstab file?

In any case, unless you can replicate it, and I'd suggest that perhaps this bug report should be closed out.

[Daniel Moyne (dmoyne)]

here is my "fstab" file attached.
Daniel.

[Theodore Ts'o (tytso)]

Oh, I see the problem. You're not using an initrd. If you want to use root=UUID.... you need to be using an initrd which can do the uuid lookup. The kernel won't do a uuid lookup for you.