Am Sonntag, den 11.10.2009, 17:08 +0200 schrieb Armin Berres: > On Sun, 11 Oct 09 16:57, Felix Zielcke wrote: > > Probable some grub-probe call fails. > > If it's grub-probe please run it without the 2>/dev/null part which > > supresses the error messages. > > And also check that your device.map has all needed devices listed. > > Good guess. Here we go: > > # grub-probe --device-map=/boot/grub/device.map -t device / > grub-probe: error: cannot find a device for /. > > # cat /boot/grub/device.map > (hd0) /dev/sda
Thanks, now I only need to know which line in update-grub causes this. There is already one grub-probe call handled differently then just sending errors to /dev/null but seems like this is also needed for another one. The reason is that grub-probe also prints out errors which are only relevant for grub2 and this confused people. As I said one line above the part you quoted from me: `sh -x update-grub' > Looks sane, doesn't it? I have /boot on a little ext3 partition and the > rest is on LVM. > > # mount > /dev/dm-0 on / type ext3 (rw,errors=remount-ro) *sigh* I'm now too lazy to search the bug reports we got for grub2 because of this, but the problem is a change in dmsetup which was reverted in the next upload. And so only affects sid users. Solution is to run `update-initramfs -c -t -k all' and if you don't want to reboot then also run `echo change > /sys/block/dm-0/uevent' -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
