Am Mittwoch, den 02.09.2009, 19:36 +0200 schrieb Albin Tonnerre: > On Wed, Sep 02, 2009 at 07:21:31PM +0200, Felix Zielcke wrote : > > Am Mittwoch, den 02.09.2009, 18:59 +0200 schrieb Albin Tonnerre: > > > Package: grub-pc > > > Version: 1.97~beta1-1 > > > Severity: grave > > > Justification: renders package unusable > > > > > > Hello, > > > After installing grub-pc, the system (using /boot and / on LVM) fails to > > > boot > > > with the following error: > > > > > > Entering rescue mode... > > > error: no such disk > > > > > > This is not particularly related to grub 1.97, as I've been experiencing > > > this > > > for some time now. Lilo is able to boot the system correctly. If there's > > > anything I can do to help you fix this, please let me know. > > > > > > Regards, > > > Albin > > > > > > > > > -- Package-specific info: > > > > > > *********************** BEGIN /proc/mounts > > > /dev/mapper/lvm-system / ext3 rw,relatime,errors=remount-ro,data=ordered > > > 0 0 > > > /dev/mapper/home /home ext3 rw,noatime,errors=remount-ro,data=ordered 0 0 > > > *********************** END /proc/mounts > > > > > > *********************** BEGIN /boot/grub/device.map > > > (hd0) /dev/sda > > > (lvm-system) /dev/mapper/lvm-system > > > *********************** END /boot/grub/device.map > > > > You don't need to have LVs in device.map. device.map doestn't get used > > for LVM. > > That's what grub autogenerated upon install. Thanks for the info, though. I > wasn't aware of that.
grub2 shouldn't do this. I don't know about grub-installer/grub-legacy. > > > *********************** BEGIN /boot/grub/grub.cfg > > > # > > > # DO NOT EDIT THIS FILE > > > # > > > # It is automatically generated by /usr/sbin/grub-mkconfig using templates > > > # from /etc/grub.d and settings from /etc/default/grub > > > # > > > > > > ### BEGIN /etc/grub.d/00_header ### > > > set default=0 > > > insmod ext2 > > > set root=(lvm-system) > > > > Uhm this is weird. There should be a `insmod lvm' too. > > Then the lvm module isn't probable included in core.img > > What do the following commands output? > > grub-probe -t device / > > grub-probe -t abstraction /dev/mapper/lvm-system > > [19:33 ~]% sudo grub-probe -t device / > /dev/mapper/lvm-system > [19:33 ~]% sudo grub-probe -t abstraction /dev/mapper/lvm-system > grub-probe: error: cannot find a device for /dev/mapper/lvm-system. Oh I forgot the -d sudo grub-probe -t abstraction -d /dev/mapper/lvm-system But maybe you're affected by the same problem as in 542435, 544577 and 543795 which was actually caused by a change in dmsetup Check that the files in /dev/mapper are real devices and no symlinks to /dev/dm-X If they're symlinks then run `echo change > /sys/block/dm-X/uevent' and replace X with the real number to which the symlink links to. 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 debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
