Bug#542425: error: cannot find a device for /.
Am Sonntag, den 30.08.2009, 19:02 +0200 schrieb Albin Stjerna: The output’s a bit over my head, but a point of interest seems to be: + set /usr/sbin/grub-mkdevicemap dummy + test -f /usr/sbin/grub-mkdevicemap + : + set /usr/sbin/grub-probe dummy + test -f /usr/sbin/grub-probe + : + mkdir -p /boot/grub + test -e /boot/grub/device.map + : ++ /usr/sbin/grub-probe --target=device / grub-probe: error: cannot find a device for /. Apparently, for some reason it’s running grub-probe on /, which, of course, isn’t registered with GRUB. The only partition it’s supposed to know about is my (unencrypted, plain) boot partition (/dev/hda1). Now, what I’m wondering is why GRUB has forgotten this: I haven’t touched any of GRUB’s settings! Oh right, I forgot that we use grub-probe even to find out the right device for the kernel root= parameter. Someone who has an encrypted LVM / had the same problem and just reported #544420 This was also caused by a symlink instead of the device. So please check with `ls -l /dev/mapper/' if your / LVM is a symlink or device. If it's a symlink then try to run `echo change /sys/block/dm-X/uevent' and replace X with the right number the symlink points to. If that doestn't fix it then I think `rm /dev/mapper/volume cp -R /dev/dm-R /dev/mapper/volume' should do it. -- 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
Bug#542425: error: cannot find a device for /.
At Mon, 31 Aug 2009 16:28:42 +0200, Felix Zielcke wrote: Am Sonntag, den 30.08.2009, 19:02 +0200 schrieb Albin Stjerna: The output’s a bit over my head, but a point of interest seems to be: + set /usr/sbin/grub-mkdevicemap dummy + test -f /usr/sbin/grub-mkdevicemap + : + set /usr/sbin/grub-probe dummy + test -f /usr/sbin/grub-probe + : + mkdir -p /boot/grub + test -e /boot/grub/device.map + : ++ /usr/sbin/grub-probe --target=device / grub-probe: error: cannot find a device for /. Apparently, for some reason it’s running grub-probe on /, which, of course, isn’t registered with GRUB. The only partition it’s supposed to know about is my (unencrypted, plain) boot partition (/dev/hda1). Now, what I’m wondering is why GRUB has forgotten this: I haven’t touched any of GRUB’s settings! Oh right, I forgot that we use grub-probe even to find out the right device for the kernel root= parameter. Someone who has an encrypted LVM / had the same problem and just reported #544420 This was also caused by a symlink instead of the device. So please check with `ls -l /dev/mapper/' if your / LVM is a symlink or device. If it's a symlink then try to run `echo change /sys/block/dm-X/uevent' and replace X with the right number the symlink points to. If that doestn't fix it then I think `rm /dev/mapper/volume cp -R /dev/dm-R /dev/mapper/volume' should do it. Thanks, but something, I have no idea what, seems to have fixed it. grub-probe now detects / to /dev/mapper/nyx-root as expected, and the setup of grub-pc seems to run fine (I haven’t tried a reboot yet, though). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542425: error: cannot find a device for /.
At Fri, 28 Aug 2009 12:57:53 +0200, Felix Zielcke wrote: If you'd have that problem then there should be /dev/dm-0 or something like that instead of the /dev/mapper name. Anyway your / is encrypted and grub2 doestn't support that yet. My / is encrypted, but GRUB 2 is loading some initramfs I think, which in turn decrypts it. It’s all auto-configured, so I’m not really sure, but it’s using LUKS. Well make sure that /boot/grub/unicode.pf2 exists, if not then copy it from /usr/share/grub It’s there. Else run `sh -x grub-mkconfig', maybe that tells why it wants to access / If not then you have to add `x' to the `#!/bin/sh -e' line in every /etc/grub.d/ file and run again grub-mkconfig. The output’s a bit over my head, but a point of interest seems to be: + set /usr/sbin/grub-mkdevicemap dummy + test -f /usr/sbin/grub-mkdevicemap + : + set /usr/sbin/grub-probe dummy + test -f /usr/sbin/grub-probe + : + mkdir -p /boot/grub + test -e /boot/grub/device.map + : ++ /usr/sbin/grub-probe --target=device / grub-probe: error: cannot find a device for /. Apparently, for some reason it’s running grub-probe on /, which, of course, isn’t registered with GRUB. The only partition it’s supposed to know about is my (unencrypted, plain) boot partition (/dev/hda1). Now, what I’m wondering is why GRUB has forgotten this: I haven’t touched any of GRUB’s settings! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542425: error: cannot find a device for /.
Package: grub-pc
Version: 1.96+20090826-3
Severity: normal
I'm having roughly the same problem as the earlier submitter. I'm using the
standard Encrypted LVM setup, and I have upgraded both LVM and GRUB as
adviced earlier, with no success. Though, I haven't rebooted yet, fearing the
system would be unbootable.
Output:
Setting up grub-pc (1.96+20090826-3) ...
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/hda
(hd1) /dev/hdc
grub-probe: error: cannot find a device for /.
dpkg: error processing grub-pc (--configure):
subprocess installed post-installation script returned error exit status 1
my /proc/mounts:
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev tmpfs rw,relatime,size=10240k,mode=755 0 0
/dev/mapper/nyx-root / ext3
rw,noatime,nodiratime,errors=remount-ro,data=ordered 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
/dev/hda1 /boot ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/mapper/storage /var/storage ext3
rw,noatime,nodiratime,errors=continue,data=ordered 0 0
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/nyx-root / ext3
rw,noatime,nodiratime,errors=remount-ro,data=ordered 0 0
/dev/hda1 /boot ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/mapper/storage /var/storage ext3
rw,noatime,nodiratime,errors=continue,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/hda
(hd1) /dev/hdc
*** 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
set timeout=5
set root=(hd0,1)
search --no-floppy --fs-uuid --set 563eca43-4812-4743-80d1-5e62d512c18b
if loadfont /grub/ascii.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
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set root=(hd0,1)
search --no-floppy --fs-uuid --set 563eca43-4812-4743-80d1-5e62d512c18b
insmod png
if background_image /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/10_linux ###
menuentry Debian GNU/Linux, Linux 2.6.30-1-686 {
set root=(hd0,1)
search --no-floppy --fs-uuid --set 563eca43-4812-4743-80d1-5e62d512c18b
linux /vmlinuz-2.6.30-1-686 root=/dev/mapper/nyx-root ro quiet
initrd /initrd.img-2.6.30-1-686
}
menuentry Debian GNU/Linux, Linux 2.6.30-1-686 (recovery mode) {
set root=(hd0,1)
search --no-floppy --fs-uuid --set 563eca43-4812-4743-80d1-5e62d512c18b
linux /vmlinuz-2.6.30-1-686 root=/dev/mapper/nyx-root ro single
initrd /initrd.img-2.6.30-1-686
}
### 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: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0]1.5.27 Debian configuration management sy
ii grub-common 1.96+20090826-3 GRand Unified Bootloader, version
ii libc62.9-25 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/linux_cmdline:
* grub2/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
grub-pc/kopt_extracted: false
* grub-pc/install_devices: /dev/hda
Bug#542425: error: cannot find a device for /.
Am Freitag, den 28.08.2009, 11:47 +0200 schrieb Albin Stjerna: Package: grub-pc Version: 1.96+20090826-3 Severity: normal I'm having roughly the same problem as the earlier submitter. I'm using the standard Encrypted LVM setup, and I have upgraded both LVM and GRUB as adviced earlier, with no success. Though, I haven't rebooted yet, fearing the system would be unbootable. Output: Setting up grub-pc (1.96+20090826-3) ... 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/hda (hd1) /dev/hdc grub-probe: error: cannot find a device for /. dpkg: error processing grub-pc (--configure): subprocess installed post-installation script returned error exit status 1 my /proc/mounts: /dev/mapper/nyx-root / ext3 rw,noatime,nodiratime,errors=remount-ro,data=ordered 0 0 If you'd have that problem then there should be /dev/dm-0 or something like that instead of the /dev/mapper name. Anyway your / is encrypted and grub2 doestn't support that yet. In a previous upload upstream changed the default font from ascii.pf2 to unicode.pf2 and I forgot to change the grub-pc.postinst so that the unicode font gets copied to /boot But you're using a fixed version. Well make sure that /boot/grub/unicode.pf2 exists, if not then copy it from /usr/share/grub Else run `sh -x grub-mkconfig', maybe that tells why it wants to access / If not then you have to add `x' to the `#!/bin/sh -e' line in every /etc/grub.d/ file and run again grub-mkconfig. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
