OK, I clarified the problem. With either the UUID of the / filesystem or
the /boot filesystem in the /boot/grub/grub.cfg search line:
ie either:
search --fs-uuid --set bfdeb6d6-0b77-4beb-a63d-bdc3e455b8ea
or:
search --fs-uuid --set 96c96a61-8615-4715-86d0-09cb8c62638c
I get:
error: no such device bfdeb6d6-0b77-4beb-a63d-bdc3e455b8ea
or:
error: no such device 96c96a61-8615-4715-86d0-09cb8c62638c
By removing the "search --fs-uuid --set ...." line entirely I can boot
successfully.
Thanks for your help!
Felix Zielcke wrote, on 26/05/09 15:05:
Am Dienstag, den 26.05.2009, 11:51 +0930 schrieb Arthur Marsh:
Hi, I had incorrectly said
"search line uses / uuid instead of /boot uuid"
when in fact the search line used the /boot uuid instead of /
So where's the bug?
The root variable inside grub was ever already for the filesystem where
the files are loaded from so it should be your /boot and not your /
so the search --set is totally correct because it just sets the root
variable to it and as long as grub can load your kernel everything
should be fine.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
