After a file system crash I reinstalled jaunty. I did not change the
partitions. I only formatted the root partition with ext4 again. The bug
disappeared, Ubuntu boots now without any problems. So I am closing the
bug report.
** Changed in: grub (Ubuntu)
Status: New => Invalid
--
grub doe
I tried to boot with "root=/dev/disk/by-uuid/71f444b7-d4a5-42de-82dd-
ac58416c1de9" option, but it causes the same kernel panic. Enclosed
please find the dmesg output.
I have two disks. The first disk contains my main Ubuntu system. The
second (sdb) contains Windows XP (sdb1), Windows Vista (sdb2)
Hi Benjamin,
I attempted to reproduce you problem with a two disc configuration and
Windows installed on the 2nd disc, but I have not be able to reproduce
this (yet).
Can you change the boot option to:
"root=/dev/disk/by-uuid/71f444b7-d4a5-42de-82dd-ac58416c1de9"
And retry. If we get the same V
Here you are. Setting status back to New.
** Attachment added: "tune2fs -l /dev/sdb3"
http://launchpadlibrarian.net/21694496/tune2fs-l_sdb3
** Changed in: grub (Ubuntu)
Status: Incomplete => New
--
grub does not resolve ext4 uuid
https://bugs.launchpad.net/bugs/320860
You received thi
We might just need to update the copy of libvolumeid in grub. Could you
post the output of 'sudo tune2fs -l /dev/sdb3', please?
** Changed in: grub (Ubuntu)
Status: New => Incomplete
--
grub does not resolve ext4 uuid
https://bugs.launchpad.net/bugs/320860
You received this bug notificati
** Attachment added: "fdisk-l"
http://launchpadlibrarian.net/21597141/fdisk-l
--
grub does not resolve ext4 uuid
https://bugs.launchpad.net/bugs/320860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
** Attachment added: "menu.lst"
http://launchpadlibrarian.net/21597136/menu.lst
--
grub does not resolve ext4 uuid
https://bugs.launchpad.net/bugs/320860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
