On 08/10/10 16:19, Goh Lip wrote:
Great! But upon receiving this message, I rebooted and did this same
syntax with "root=LABEL=2010_1_64_root ro" (of course, substituting with
my labelname). Boots fine! Strange, isn't it? -(normally, I boot with
uuid).
I hope it is not because you have used the same labelname for your
partitions (without realizing it) or had 'reused' the same labelname and
the grub-device map was looking at the old partition.
No - most definitely not!
At least, Barry, you've got this sorted out and I am glad.
Regards and take care. - Goh Lip
Weird!
Remember this? :-
menuentry 'PCLOS Live' {
linux (hd0,1)/isolinux/vmlinuz vga=788 livecd=livecd fromusb
root=/dev/sda1 acpi=on fstab=rw,noauto
initrd (hd0,1)/isolinux/initrd.gz
}
(Excuse wrapping) well, in my quest to get rid of sdxx, (hdx,y) and
UUIDs, I tried this:-
menuentry 'PCLOS Live test' {
search --no-floppy --label --set maingrub
linux /isolinux/vmlinuz vga=788 livecd=livecd fromusb
root=label=maingrub acpi=on fstab=rw,noauto
initrd /isolinux/initrd.gz
}
...and it works! go figure?
I wonder if grub version has a bearing on this? I am using 1.97 beta4
is that the latest? - and which are you using.
Another odd thing :-
this works also
menuentry 'Ubuntu 10.04' {
search --no-floppy --label --set ubuntu
chainloader +1
}
So why does Ubuntu's grub2 chainload when my 1.97b4 version won't?
Now I understand why most distros are cautious about moving to grub2 ;-/
Cheers - Barry
_______________________________________________
Help-grub mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-grub
