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.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Invalid
--
[Feisty]Bug with kernel 2.6.20 on
here is my fstab file attached.
Daniel.
** Attachment added: fstab file
http://launchpadlibrarian.net/8289292/fstab
--
[Feisty]Bug with kernel 2.6.20 on AMD 64 : no way to boot
https://bugs.launchpad.net/bugs/107965
You received this bug notification because you are a member of Ubuntu
Bugs,
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 :
[EMAIL PROTECTED]:/home/dmoyne# blkid
/dev/sda1: UUID=bdba10ce-bfc4-41fb-bb39-25deca8024fd SEC_TYPE=ext2
TYPE=ext3
/dev/hda1:
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
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!
--
[Feisty]Bug with kernel 2.6.20 on AMD 64 : no way to boot
https://bugs.launchpad.net/bugs/107965
You received this
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
--
[Feisty]Bug with kernel
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.
--
[Feisty]Bug with kernel 2.6.20 on AMD 64 : no way to boot
