Bug#548803: Me too

2009-11-08 Thread Chris Chiappa
Same thing happened to me - couldn't find the filesystem even though
the UUID referenced appaars to be correct.  Booting with
root=/dev/hda1 instead works fine.  I appear to get a correct grub.cfg
if I set
GRUB_DISABLE_LINUX_UUID=true
in /etc/default/grub.cfg

My setup is pretty straight forward - the root fs is ext3 on a PATA disk.

-- 

..ooOO ch...@chiappa.net  | My opinions are my own  OOoo..
..ooOO chris.chia...@oracle.com   | and certainly not those OOoo..
..ooOO http://www.chiappa.net/~chris/ | of my employer  OOoo..



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#548803: Me too

2009-11-08 Thread Felix Zielcke
reassign 530357 grub-pc
forcemerge 530357 548803
thanks
Am Sonntag, den 08.11.2009, 16:44 -0500 schrieb Chris Chiappa:
 Same thing happened to me - couldn't find the filesystem even though
 the UUID referenced appaars to be correct.  Booting with
 root=/dev/hda1 instead works fine.  I appear to get a correct grub.cfg
 if I set
 GRUB_DISABLE_LINUX_UUID=true
 in /etc/default/grub.cfg
 
 My setup is pretty straight forward - the root fs is ext3 on a PATA disk.
 

Do you get from GRUB and not kernel/initrd the message that it can't
find the device with the UUID?
If yes then it would be very strange that disabling root=UUID= usage
fixes this.
If not then it's not the same bug.
If uuid in the root=UUID linux line is the one for your / and initrd
can't find it then it's a bug inside the initrd which is not at all
created by us.

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#548803: Me too

2009-11-08 Thread Chris Chiappa
On Sun, Nov 08, 2009 at 11:57:56PM +0100, Felix Zielcke wrote:
 Do you get from GRUB and not kernel/initrd the message that it can't
 find the device with the UUID?
 If yes then it would be very strange that disabling root=UUID= usage
 fixes this.
 If not then it's not the same bug.
 If uuid in the root=UUID linux line is the one for your / and initrd
 can't find it then it's a bug inside the initrd which is not at all
 created by us.
You're right.  The kernel complained that it gave up waiting for the
root filesystem to appear and dumped me in a shell.  I'll try to
figure out where the right bug report should go.

-- 

..ooOO ch...@chiappa.net  | My opinions are my own  OOoo..
..ooOO chris.chia...@oracle.com   | and certainly not those OOoo..
..ooOO http://www.chiappa.net/~chris/ | of my employer  OOoo..



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org