"grub2-probe: error: cannot find a GRUB drive…" What causes this, and why?
grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub.cfg ... Found theme: /boot/grub2/themes/system/theme.txt /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/vda2 /dev/vdb2. Check your device.map. Found linux image: /boot/vmlinuz-3.9.0-0.rc4.git0.1.fc20.i686.PAE Found initrd image: /boot/initramfs-3.9.0-0.rc4.git0.1.fc20.i686.PAE.img Found linux image: /boot/vmlinuz-0-rescue-e567d261136e65c44daec4be883d00f5 Found initrd image: /boot/initramfs-0-rescue-e567d261136e65c44daec4be883d00f5.img /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/vda2 /dev/vdb2. Check your device.map. done
/boot/grub2/device.map: # this device map was generated by anaconda (hd0) /dev/vda (hd1) /dev/vdb (hd2) /dev/vda (hd3) /dev/vdb
/proc/mounts: /dev/vda2 / btrfs rw,seclabel,relatime,compress=lzo,space_cache 0 0 /dev/vda2 /home btrfs rw,seclabel,relatime,compress=lzo,space_cache 0 0 /dev/vda2 /boot btrfs rw,seclabel,relatime,compress=lzo,space_cache 0 0
btrfs filesystem show Label: 'fedora' uuid: d5773e24-f14f-4d85-8fd3-b2b5457b4708 Total devices 2 FS bytes used 3.61GB devid 2 size 18.03GB used 5.78GB path /dev/vdb2 devid 1 size 18.03GB used 5.79GB path /dev/vda2
Btrfs v0.20-rc1
btrfs filesystem df / Data, RAID1: total=5.00GB, used=3.35GB System, RAID1: total=32.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, RAID1: total=768.00MB, used=262.83MB
Thanks, poma
On 02.04.2013 17:53, poma wrote:
"grub2-probe: error: cannot find a GRUB drive…" What causes this, and why?
grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub.cfg ... Found theme: /boot/grub2/themes/system/theme.txt /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/vda2 /dev/vdb2. Check your device.map. Found linux image: /boot/vmlinuz-3.9.0-0.rc4.git0.1.fc20.i686.PAE Found initrd image: /boot/initramfs-3.9.0-0.rc4.git0.1.fc20.i686.PAE.img Found linux image: /boot/vmlinuz-0-rescue-e567d261136e65c44daec4be883d00f5 Found initrd image: /boot/initramfs-0-rescue-e567d261136e65c44daec4be883d00f5.img /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/vda2 /dev/vdb2. Check your device.map. done
/boot/grub2/device.map: # this device map was generated by anaconda (hd0) /dev/vda (hd1) /dev/vdb (hd2) /dev/vda (hd3) /dev/vdb
/proc/mounts: /dev/vda2 / btrfs rw,seclabel,relatime,compress=lzo,space_cache 0 0 /dev/vda2 /home btrfs rw,seclabel,relatime,compress=lzo,space_cache 0 0 /dev/vda2 /boot btrfs rw,seclabel,relatime,compress=lzo,space_cache 0 0
btrfs filesystem show Label: 'fedora' uuid: d5773e24-f14f-4d85-8fd3-b2b5457b4708 Total devices 2 FS bytes used 3.61GB devid 2 size 18.03GB used 5.78GB path /dev/vdb2 devid 1 size 18.03GB used 5.79GB path /dev/vda2
Btrfs v0.20-rc1
btrfs filesystem df / Data, RAID1: total=5.00GB, used=3.35GB System, RAID1: total=32.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, RAID1: total=768.00MB, used=262.83MB
grub2-mkconfig -o /dev/null Generating grub.cfg ... Found theme: /boot/grub2/themes/system/theme.txt /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/vda /dev/vdb. Check your device.map. Found linux image: /boot/vmlinuz-3.9.0-0.rc5.git0.2.fc20.i686.PAE Found initrd image: /boot/initramfs-3.9.0-0.rc5.git0.2.fc20.i686.PAE.img Found linux image: /boot/vmlinuz-0-rescue-e567d261136e65c44daec4be883d00f5 Found initrd image: /boot/initramfs-0-rescue-e567d261136e65c44daec4be883d00f5.img /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/vda /dev/vdb. Check your device.map. done
/boot/grub2/device.map: # this device map was generated by anaconda (hd0) /dev/vda (hd1) /dev/vdb (hd2) /dev/vdc (hd3) /dev/vdd
/proc/mounts: /dev/vda / btrfs rw,relatime,space_cache 0 0
btrfs filesystem show Label: none uuid: 78448190-f468-4747-8adf-0d1188bd2b6b Total devices 2 FS bytes used 2.06GB devid 2 size 10.00GB used 3.01GB path /dev/vdb devid 1 size 10.00GB used 3.03GB path /dev/vda
Btrfs v0.20-rc1
btrfs filesystem df / Data, RAID0: total=4.00GB, used=1.94GB Data: total=8.00MB, used=0.00 System, RAID1: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, RAID1: total=1.00GB, used=124.13MB Metadata: total=8.00MB, used=0.00
So far, "grub2-probe: error: cannot find a GRUB drive…" has nothing to do with subvolumes - in this configuration, there are none. Stay tuned. :)
poma
On Wed, 03 Apr 2013 09:54:34 +0200 poma pomidorabelisima@gmail.com wrote:
So far, "grub2-probe: error: cannot find a GRUB drive…" has nothing to do with subvolumes - in this configuration, there are none. Stay tuned. :)
poma
Maybe re-run "grub2-install /dev/vda"
On 03.04.2013 09:57, Frank Murphy wrote:
On Wed, 03 Apr 2013 09:54:34 +0200 poma pomidorabelisima@gmail.com wrote:
So far, "grub2-probe: error: cannot find a GRUB drive…" has nothing to do with subvolumes - in this configuration, there are none. Stay tuned. :)
poma
Maybe re-run "grub2-install /dev/vda"
The installation itself is not affected in this case, and has no influence on the creation of the configuration file. ;) /usr/sbin/grub2-install /dev/vda Installation finished. No error reported. /usr/sbin/grub2-install /dev/vdb Installation finished. No error reported.
In fact with a very simple Gene's patch[1] the issue(rhbz#890955) was solved.[2]
/usr/sbin/grub2-mkconfig -o /dev/null Generating grub.cfg ... Found theme: /boot/grub2/themes/system/theme.txt Found linux image: /boot/vmlinuz-3.9.0-0.rc5.git0.2.fc20.i686.PAE Found initrd image: /boot/initramfs-3.9.0-0.rc5.git0.2.fc20.i686.PAE.img Found linux image: /boot/vmlinuz-0-rescue-e567d261136e65c44daec4be883d00f5 Found initrd image: /boot/initramfs-0-rescue-e567d261136e65c44daec4be883d00f5.img done
On the other side of the River Styx, the last referent grub revision(4770) didn't solve this issue.[3]
/usr/local/sbin/grub-mkconfig -o /dev/null Generating grub.cfg ... /usr/local/sbin/grub-probe: error: cannot find a GRUB drive for /dev/vda /dev/vdb. Check your device.map. Found linux image: /boot/vmlinuz-3.9.0-0.rc5.git0.2.fc20.i686.PAE Found initrd image: /boot/initramfs-3.9.0-0.rc5.git0.2.fc20.i686.PAE.img Found linux image: /boot/vmlinuz-0-rescue-e567d261136e65c44daec4be883d00f5 Found initrd image: /boot/initramfs-0-rescue-e567d261136e65c44daec4be883d00f5.img /usr/local/sbin/grub-probe: error: cannot find a GRUB drive for /dev/vda /dev/vdb. Check your device.map. done
bzr branch http://bzr.savannah.gnu.org/r/grub/trunk/grub bzr log -m multi-device -p util/grub-mkconfig_lib.in ------------------------------------------------------------ revno: 4770 […] message: * util/grub-mkconfig_lib.in (prepare_grub_to_access_device): Fix handling of multi-device filesystems. diff: === modified file 'util/grub-mkconfig_lib.in' --- util/grub-mkconfig_lib.in 2012-12-28 06:57:17 +0000 +++ util/grub-mkconfig_lib.in 2013-03-24 12:11:19 +0000 @@ -115,9 +115,7 @@
prepare_grub_to_access_device () { - device="$1" - - partmap="`"${grub_probe}" --device "${device}" --target=partmap`" + partmap="`"${grub_probe}" --device "$@" --target=partmap`" for module in ${partmap} ; do case "${module}" in netbsd | openbsd) […]
downstream 1 : 0 upstream :)
poma
[1] https://bugzilla.redhat.com/attachment.cgi?id=676998 [2] https://bugzilla.redhat.com/attachment.cgi?id=676998&action=diff [3] http://bzr.savannah.gnu.org/lh/grub/trunk/grub/revision/4770#util/grub-mkcon...
-
Frank Murphy -
poma