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
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
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 -
3 matches
Mail list logo