Bug#542435: grub-probe: error: cannot find a device for /. (LVM2)

Felix Zielcke fzielcke at z-51.de
Wed Aug 19 19:12:33 UTC 2009


Am Mittwoch, den 19.08.2009, 21:01 +0200 schrieb Stefan
Lippers-Hollmann:

> === NOT working, with dmsetup udev rules ===
> 
> $ ls -al /dev/mapper/ /dev/sputnik/
> /dev/mapper/:
> insgesamt 0
> drwxr-xr-x  2 root root    140 19. Aug 20:56 .
> drwxr-xr-x 17 root root   2860 19. Aug 20:57 ..
> crw-rw----  1 root root 10, 60 19. Aug 2009  control
> lrwxrwxrwx  1 root root      7 19. Aug 2009  sputnik-debian64 -> ../dm-0
> lrwxrwxrwx  1 root root      7 19. Aug 20:56 sputnik-home -> ../dm-3
> lrwxrwxrwx  1 root root      7 19. Aug 20:56 sputnik-swap -> ../dm-2
> lrwxrwxrwx  1 root root      7 19. Aug 20:56 sputnik-var -> ../dm-1
> 

This just can't work with the way how grub-probe currently works.
stat() is used to map the filesystem paths to devices.
So in that case it uses the /dev/dm-* ones instead of the /dev/mapper/*
But grub-probe generates the (vg-lv) grub device from the file name and
then looks for all LVM headers if there is such a volumegroup and
logical volume.

It would be easier to fix in lvm2 package but because this is an
upstream change of it we need to adress this in grub-probe.
But I fail to get an idea how to fix this.






More information about the Pkg-grub-devel mailing list