Am Sonntag, den 30.08.2009, 19:02 +0200 schrieb Albin Stjerna:
> The output’s a bit over my head, but a point of interest seems to be:
> + set /usr/sbin/grub-mkdevicemap dummy
> + test -f /usr/sbin/grub-mkdevicemap
> + :
> + set /usr/sbin/grub-probe dummy
> + test -f /usr/sbin/grub-probe
> + :
> + mkdir -p /boot/grub
> + test -e /boot/grub/device.map
> + :
> ++ /usr/sbin/grub-probe --target=device /
> grub-probe: error: cannot find a device for /.
> Apparently, for some reason it’s running grub-probe on /, which, of course,
> isn’t registered with GRUB. The only partition it’s supposed to know about is
> (unencrypted, plain) boot partition (/dev/hda1). Now, what I’m wondering is
> GRUB has forgotten this: I haven’t touched any of GRUB’s settings!
Oh right, I forgot that we use grub-probe even to find out the right
device for the kernel root= parameter.
Someone who has an encrypted LVM / had the same problem and just
This was also caused by a symlink instead of the device.
So please check with `ls -l /dev/mapper/' if your / LVM is a symlink or
If it's a symlink then try to run `echo change > /sys/block/dm-X/uevent'
and replace X with the right number the symlink points to.
If that doestn't fix it then I think `rm /dev/mapper/volume && cp -R /dev/dm-R
should do it.
Proud Debian Maintainer
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org