Am Dienstag, den 01.09.2009, 11:43 -0500 schrieb John Goerzen: > Package: grub-pc > Version: 1.97~beta1-1 > Severity: important > > On upgrading this package on a system with working grub-pc already, I > see: > > Setting up grub-pc (1.97~beta1-1) ... > Installation finished. No error reported. > This is the contents of the device map /boot/grub/device.map. > Check if this is correct or not. If any of the lines is incorrect, > fix it and re-run the script `grub-install'. > > (hd0) /dev/sda > (hd1) /dev/sdb > (hd2) /dev/sdd > grub-probe: error: cannot find a device for /. > > dpkg: error processing grub-pc (--configure): > subprocess installed post-installation script returned error exit > status 1 > Errors were encountered while processing: > grub-pc > > root here is /dev/mapper/crypt-root. I am unsure if it is safe to > reboot at this point. Did something with crypt mounts get broken? > > The previous version was 1.96+20090808-1 >
Probable you're also affected by the change of dmsetup 2:1.02.36-1 that made the files in /dev/mapper/* symlinks to /dev/dm-*. That was reverted in 2:1.02.36-2. See 543795, 542425 and 542435. For some people just upgrading the package to -2 and even rebooting doestn't fix it. Check with `ls -l /dev/mapper/' to which /dev/dm-X device your root lv links to and then run `echo change > /sys/block/dm-X/uevent' If that doestn't fix it, `rm /dev/mapper/volume && cp -R /dev/dm-X /dev/mapper/volume' -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
