On Lu, 21 mar 11, 20:28:51, Geronimo wrote: > > > > Look at "/boot/grub/device.map". It sets up a correspondence between > > grub's hdX and devices in "/dev/disk/by-id/..." so it doesn't depend > > on the kernel's device names. > > I tried to change that file, but I suspect, that nobody cares about that > changes. I did that already about 6 weeks ago - and it did not change > anything > then, so I did not try it again. That file should be generated with 'grub-mkdevicemap', as hinted below.
> > Run "grub-mkdevicemap" and "grub-install '(hdX)'" where "(hdX)" > > corresponds to the disk in "/boot/grub/device.map" on which you want > > to install grub. ... > > I don't remember seeing a link (or, preferably, attachment) of your > > boot.cfg and output of "/sbin/blkid | sort". > > Ok, the latter is attached (well - just half of the disks), the former does > not exists any more, cause I purged grub2 Too bad, now we can't investigate what was wrong. Just for the archives, here's an excerpt from a working grub.cfg from a fresh squeeze install: ,---- | menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os { | set gfxpayload=keep | insmod part_msdos | insmod ext2 | set root='(hd0,msdos7)' | search --no-floppy --fs-uuid --set da34b390-81e0-485b-a4f1-fffa7d5a6089 | echo 'Loading Linux 2.6.32-5-amd64 ...' | linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=da34b390-81e0-485b-a4f1-fffa7d5a6089 ro quiet | echo 'Loading initial ramdisk ...' | initrd /boot/initrd.img-2.6.32-5-amd64 | } `---- You might think it's using devices names because of the 'set root=' line, but the next line will actually override that, using the UUID. The 'linux' line is also using UUID to set the 'root' kernel parameter. Hope this explains, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
signature.asc
Description: Digital signature