logo       

Re: uuid changes- not updated in grub2: msg#00645

kubuntu-users

Subject: Re: uuid changes- not updated in grub2

Bruce Marshall wrote:

>
> Grub2 has problems with uuid's. I recently installed the grub2 pkg on
> jaunty
> and it changed the:
>
> uuid <long string for uuid)
>
> in grub1's menu.lst to:
>
> root <same long string for uuid>
>
> in both the menu.lst and in the grub.cfg files.
>
> This left my machine unbootable.
>
> I have reported this bug which was a dupe of a similar bug. Just a warning
> to those who might want to try grub2 but still keep grub1 working.
>

Jonas, the grub2 setup mechanism appears different in Hardy and Karmic.
I do not have Jaunty to know how it works. But have you done

'sudo update-from-grub-legacy'

It will do no harm if you do these before update-from-legacy

sudo update-grub
sudo grub-mkconfig


Jonas, my grub.cfg appears like this

in Karmic
menuentry "Ubuntu, Linux 2.6.31-4-generic" {
set root=(hd0,5)
search --no-floppy --fs-uuid --set 79c013db-b497-4cba-a693-02317cf22c13
linux /boot/vmlinuz-2.6.31-4-generic
root=UUID=79c013db-b497-4cba-a693-02317cf22c13 ro quiet splash
initrd /boot/initrd.img-2.6.31-4-generic
}

and in Hardy
menuentry "Ubuntu, linux 2.6.24-24-generic" {
linux (hd0,8)/boot/vmlinuz-2.6.24-24-generic
root=UUID=606840d0-3e10-4e6b-9aba-c445d082832b ro quiet splash
initrd (hd0,8)/boot/initrd.img-2.6.24-24-generic
}

Both works.


My '1st grub' grub.cfg is a simple
menuentry "Kde4 " {
configfile (hd0,5)/boot/grub/grub.cfg
}

menuentry "Cos " {
set root=(hd0,2)
chainloader +1
}


Note: configfile to grub2 boots and
chainload to grub legacy and windows boots

Grub2 naming convention is now (hd0,x) for sdax
unlike grub legacy where (hd0,x) is sda(x+1)


Regards,
Goh Lip


--
kubuntu-users mailing list
kubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

Google Custom Search

News | Mail Home | sitemap | FAQ | advertise