Comment 8 for bug 499483

Am Montag, den 18.01.2010, 02:43 +0000 schrieb Leppie:
> >GRUB can't know how the later booted kernel and udev names the /dev/
> >files for your disks.
> >It can only use UUIDs LABEL and a file on the filesystem which the
> >search command already supports.
>
> then why does the search still use the --fs-uuid option even though
> GRUB_DISABLE_LINUX_UUID is set to true and uncommented?

Because it has LINUX in there and is not named just GRUB_DISABLE_UUID.
It's only for the linux root=UUID kernel parameter. Not for GRUB itself
for what search and set commands are.

> should the "set root=(hdX,Y)" command not take care of the location
> for grub to look for its files?

Hardcoded GRUB devices aren't reliable. You have to
change /boot/grub/device.map to match your BIOS boot order.
And as soon as you change your BIOS boot order or sometimes it's even
enough to just add another disk to your PC and you need to fix
device.map again.

> in some cases the search seems to be looking for different UUID's
> than those passed by the command (set in grub.cfg).

It uses (Well it should, else it's a bug) the UUID of the filesystem
which contains the file the command after search uses.
So if your /boot is a seperate partition search command uses the UUID
of /boot so GRUB can find the Linux kernel and then in the linux command
it uses for root=UUID= the UUID of your / filesystem.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer