Bug#544731: error: no such disk renders system unbootable
On Wed, 02 Sep 2009 20:50 +0200, Albin Tonnerre wrote : On Wed, Sep 02, 2009 at 08:26:25PM +0200, Felix Zielcke wrote : Am Mittwoch, den 02.09.2009, 20:23 +0200 schrieb Albin Tonnerre: [20:20 ~]% sudo grub-probe -t abstraction -d /dev/mapper/lvm-system lvm 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 They are real devices :( Regards, Run `bash -x grub-install --modules=minicmd /dev/sda' the grub-mkimage line should include lvm. and then check on reboot with `lsmod' if lvm is really loaded. `ls' should show the LVs Argh. After running apt-get install --reinstall grub-pc, lvm is now listed in /boot/grub/grub.cfg, and grub2 is able to boot the system correctly. Please don't close the bug, though - this has happened to me several times in the past, and running grub-install after a couple grub-pc updates resulted in the same kind of error. I absolutely have no clue as to what just happened there. Alright, so this started happening again. I'm using the latest version from unstable, 1.97-1. Did and apt-get remove --purge grub-common grub-pc, then removed everything in /boot/grub, and reinstalled. [20:15 @laptop ~]% cat /boot/grub/device.map (hd0) /dev/sda [20:15 @laptop ~]% sudo grub-probe -t device / /dev/mapper/lvm-system [20:16 @laptop ~]% sudo grub-probe -t abstraction -d /dev/mapper/lvm-system grub-probe: error: no mapping exists for `lvm-system' After adding '(lvm-system) /dev/mapper/lvm-system' to /boot/grub/devices.map: [20:17 @laptop ~]% sudo grub-probe -t abstraction -d /dev/mapper/lvm-system nothing Of course, the generated grub.cfg file doesn't contain any 'insmod lvm' directive. As previously, the files in /dev/mapper/ are real block devices and not symlinks. If there's anything I can do to help debug this issue, please let me know. Regards, -- Albin Tonnerre signature.asc Description: Digital signature
Bug#544731: error: no such disk renders system unbootable
retitle 544731 missing insmod lvm in grub.cfg (error: no such disk) tags 544731 + unreproducible thanks Maybe the more specific title will make this easier to find once the bug comes back. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#544731: error: no such disk renders system unbootable
Processing commands for cont...@bugs.debian.org: retitle 544731 missing insmod lvm in grub.cfg (error: no such disk) Bug #544731 [grub-pc] error: no such disk renders system unbootable Changed Bug title to 'missing insmod lvm in grub.cfg (error: no such disk)' from 'error: no such disk renders system unbootable' tags 544731 + unreproducible Bug #544731 [grub-pc] missing insmod lvm in grub.cfg (error: no such disk) Added tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544731: error: no such disk renders system unbootable
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
*** 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)
search --no-floppy --fs-uuid --set e2d78b0a-2ed3-4369-adcc-c9be72ca5431
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod ext2
set root=(lvm-system)
search --no-floppy --fs-uuid --set e2d78b0a-2ed3-4369-adcc-c9be72ca5431
insmod png
if background_image /boot/grub/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/09_default ###
### END /etc/grub.d/09_default ###
### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, Linux 2.6.30-1-amd64 {
insmod ext2
set root=(lvm-system)
search --no-floppy --fs-uuid --set e2d78b0a-2ed3-4369-adcc-c9be72ca5431
linux /boot/vmlinuz-2.6.30-1-amd64 root=/dev/mapper/lvm-system ro
quiet
initrd /boot/initrd.img-2.6.30-1-amd64
}
menuentry Debian GNU/Linux, Linux 2.6.30-1-amd64 (recovery mode) {
insmod ext2
set root=(lvm-system)
search --no-floppy --fs-uuid --set e2d78b0a-2ed3-4369-adcc-c9be72ca5431
linux /boot/vmlinuz-2.6.30-1-amd64 root=/dev/mapper/lvm-system ro
single
initrd /boot/initrd.img-2.6.30-1-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii grub-common 1.97~beta1-1 GRand Unified Bootloader, version
ii libc6 2.9-26 GNU C Library: Shared libraries
ii ucf 3.0021 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 5.0.5 common files for the Debian Deskto
ii genisoimage 9:1.1.9-1 Creates ISO-9660 CD-ROM filesystem
-- debconf information:
grub-pc/kopt_extracted: false
grub2/kfreebsd_cmdline:
* grub-pc/install_devices: /dev/sda
grub-pc/postrm_purge_boot_grub: false
grub-pc/linux_cmdline: fillme
* grub2/linux_cmdline:
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default: quiet
grub-pc/chainload_from_menu.lst: true
--
Albin Tonnerre
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544731: error: no such disk renders system unbootable
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. *** 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 -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544731: error: no such disk renders system unbootable
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. *** 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. Regards, -- Albin Tonnerre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544731: error: no such disk renders system unbootable
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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544731: error: no such disk renders system unbootable
Am Mittwoch, den 02.09.2009, 20:23 +0200 schrieb Albin Tonnerre: [20:20 ~]% sudo grub-probe -t abstraction -d /dev/mapper/lvm-system lvm 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 They are real devices :( Regards, Run `bash -x grub-install --modules=minicmd /dev/sda' the grub-mkimage line should include lvm. and then check on reboot with `lsmod' if lvm is really loaded. `ls' should show the LVs -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544731: error: no such disk renders system unbootable
On Wed, Sep 02, 2009 at 08:26:25PM +0200, Felix Zielcke wrote : Am Mittwoch, den 02.09.2009, 20:23 +0200 schrieb Albin Tonnerre: [20:20 ~]% sudo grub-probe -t abstraction -d /dev/mapper/lvm-system lvm 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 They are real devices :( Regards, Run `bash -x grub-install --modules=minicmd /dev/sda' the grub-mkimage line should include lvm. and then check on reboot with `lsmod' if lvm is really loaded. `ls' should show the LVs Argh. After running apt-get install --reinstall grub-pc, lvm is now listed in /boot/grub/grub.cfg, and grub2 is able to boot the system correctly. Please don't close the bug, though - this has happened to me several times in the past, and running grub-install after a couple grub-pc updates resulted in the same kind of error. I absolutely have no clue as to what just happened there. Regards, -- Albin Tonnerre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
