error: cannot find a GRUB drive for . Check your device.map.

Bug #1069856 reported by Vitaliy Kulikov on 2012-10-22
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Undecided
Unassigned

Bug Description

i have STRIPE in bios (fake RAID0). was working fine on 12.04.
but, during upgrade to 12.10 ... here is output.

$ sudo update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.5.0-17-generic
Found initrd image: /boot/initrd.img-3.5.0-17-generic
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
Found linux image: /boot/vmlinuz-3.2.0-33-generic
Found initrd image: /boot/initrd.img-3.2.0-33-generic
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
Found linux image: /boot/vmlinuz-3.2.0-32-generic
Found initrd image: /boot/initrd.img-3.2.0-32-generic
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
Found linux image: /boot/vmlinuz-3.2.0-31-generic
Found initrd image: /boot/initrd.img-3.2.0-31-generic
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
Found memtest86+ image: /boot/memtest86+.bin
grub-probe: error: cannot find a GRUB drive for /dev/mapper/isw_cijbaaefjb_Volume0p1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/mapper/isw_cijbaaefjb_Volume0p2. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/mapper/isw_cijbaaefjb_Volume1p1. Check your device.map.
done

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: grub-pc 2.00-7ubuntu11
Uname: Linux 3.0.24-std251-amd64 x86_64
NonfreeKernelModules: raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear usb_storage nouveau ttm drm_kms_helper drm xhci_hcd r8169 mii i2c_algo_bit i2c_core mxm_wmi video wmi
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
Date: Mon Oct 22 17:50:33 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: grub2
UpgradeStatus: Upgraded to quantal on 2012-10-22 (0 days ago)

Vitaliy Kulikov (slonua) wrote :
Vitaliy Kulikov (slonua) wrote :

here is more info:

$ blkid
/dev/sdb: TYPE="isw_raid_member"
/dev/sdc: TYPE="isw_raid_member"
/dev/sdd1: LABEL="USB DISK" UUID="1B77-5EA6" TYPE="vfat"
/dev/mapper/isw_cijbaaefjb_Volume0p1: LABEL="System Reserved" UUID="20647F8B647F6288" TYPE="ntfs"
/dev/mapper/isw_cijbaaefjb_Volume0p2: UUID="D216832016830527" TYPE="ntfs"
/dev/mapper/isw_cijbaaefjb_Volume1p1: LABEL="sys" UUID="b369150b-f49e-4e96-9520-6165f24829dd" TYPE="ext4"

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
Reeyarn (reeyarn) wrote :

I was upgrading from 12.04 to 12.10,

Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up grub-pc (2.00-7ubuntu11) ...
Installation finished. No error reported.
Generating grub.cfg ...
cat: /video.lst: No such file or directory
/usr/sbin/grub-probe: error: failed to get canonical path of .
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.
dpkg: error processing grub-pc (--configure):
 subprocess installed post-installation script returned error exit status 1

Phillip Susi (psusi) wrote :

Can you please run sudo grub-probe -d /dev/mapper/isw_cijbaaefjb_Volume0 -t drive? Also do you have a /boot/grub/device.map file?

Changed in grub2 (Ubuntu):
status: Confirmed → Incomplete
Reeyarn (reeyarn) wrote :

/boot/grub$ sudo cat device.map
[sudo] password for u910a6:
(hd0) /dev/disk/by-id/ata-HITACHI_HTS723232A7A364_E3834563JK71MN

sudo grub-probe -d /dev/disk/by-id/ata-HITACHI_HTS723232A7A364_E3834563JK71MN -t drive
(hd0)

sudo update-grub
Generating grub.cfg ...
/usr/sbin/grub-probe: error: failed to get canonical path of .
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.

So I first cat device.map, then run grub-probe successfully, but fail at update-grub.

Reeyarn (reeyarn) wrote :

I run the following two commands. It purged and reinstalled grub and it solved my problem.

sudo apt-get purge grub grub-pc grub-common
sudo apt-get install grub-common grub-pc

Phillip Susi (psusi) wrote :

Glad you fixed it.

Changed in grub2 (Ubuntu):
status: Incomplete → Invalid
Andreas Heinig (andreas-heinig) wrote :

For me the suggested command sequence (purge + install) don't fix the problem.

#> update-grub
Generating grub.cfg ...
cat: /video.lst: No such file or directory
/usr/sbin/grub-probe: error: failed to get canonical path of .
/usr/sbin/grub-probe: error: cannot find a GRUB drive for . Check your device.map.

I have a software raid as boot partition.

#> blkid
/dev/sda1: UUID="45aa82a9-5fc2-6eae-8795-1fcf28759b4f" UUID_SUB="ac14b6d9-8c9c-478d-79d8-39b942b29b48" LABEL="ubuntu:0" TYPE="linux_raid_member"
/dev/sda2: UUID="235bd0a9-005a-c373-6d65-97a6c29d2e13" UUID_SUB="81f0c4d9-5d46-f47b-2a72-71f5382a78ac" LABEL="ubuntu:1" TYPE="linux_raid_member"
/dev/sdb1: UUID="45aa82a9-5fc2-6eae-8795-1fcf28759b4f" UUID_SUB="820d518d-0cce-692a-e01c-62e8b85fc696" LABEL="ubuntu:0" TYPE="linux_raid_member"
/dev/sdb2: UUID="235bd0a9-005a-c373-6d65-97a6c29d2e13" UUID_SUB="6fc7a785-c04c-bd9d-97f0-6b77922a2e51" LABEL="ubuntu:1" TYPE="linux_raid_member"
/dev/sdc1: UUID="45aa82a9-5fc2-6eae-8795-1fcf28759b4f" UUID_SUB="ac00f434-005a-fc22-4d48-c115e4bd6273" LABEL="ubuntu:0" TYPE="linux_raid_member"
/dev/sdc2: UUID="235bd0a9-005a-c373-6d65-97a6c29d2e13" UUID_SUB="c17bc39d-c898-e12e-cace-de0a71ad4603" LABEL="ubuntu:1" TYPE="linux_raid_member"
/dev/md0: LABEL="TUSH_BOOT" UUID="a2c9766f-4a3c-41d5-8eaf-f55518653820" TYPE="ext2"
/dev/md1: UUID="6YlTj9-9lt3-rJOR-x8j3-jXSe-aDpW-rEWBwq" TYPE="LVM2_member"
[...]

Changed in grub2 (Ubuntu):
status: Invalid → Incomplete
Phillip Susi (psusi) wrote :

Do you have a /boot/grub/device.map file? Can yuo post the output of the df command?

I tried both: With and without a device.map

Btw.: in hte configuration dialog, I choose to install grub on sda. (->hd0)

Here is the device.map:
#> cat /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-Hitachi_HDS721075KLA330_GTE200P8G1E7HE
(hd1) /dev/disk/by-id/ata-ST3750330NS_9QK1YCFE
(hd2) /dev/disk/by-id/ata-SAMSUNG_HD753LJ_S13UJ1MQ30648

And the df output:
#> df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/LVM--MD1-kubuntu--root 48057224 39004160 6611848 86% /
udev 6120900 12 6120888 1% /dev
tmpfs 2453352 904 2452448 1% /run
none 5120 0 5120 0% /run/lock
none 6133376 7484 6125892 1% /run/shm
none 102400 0 102400 0% /run/user
/dev/md0 467302 138767 303604 32% /boot
/dev/mapper/LVM--MD1-rtems--nfs 1032088 377356 602304 39% /mnt/rtemsnfs
/dev/mapper/LVM--MD1-tftpboot 1032088 52020 927640 6% /mnt/tftpboot
/dev/mapper/root-home 1030072 80228 897520 9% /root
/dev/mapper/heandr 516059576 43260800 446584480 9% /home/heandr
/dev/mapper/LVM--MD1-project 619273992 256980120 330836592 44% /home/heandr/Projects

Phillip Susi (psusi) wrote :

Can you run sudo grub-probe -t device -d /dev/mapper/LVM--MD1-kubuntu--root and post the output?

Had the same issue, resolved by:

rm /etc/grub.d/00_header.backup

Problem solved for me!

The tipp of Kirill was perfect. The updated created the file /etc/grub.d/00_header.myversion which leads to the problem.

Launchpad Janitor (janitor) wrote :

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]

Changed in grub2 (Ubuntu):
status: Incomplete → Expired
Tv (tv42) wrote :

I still see this (or very similar errors) on 13.10, with / on btrfs (multidevice sda3 & sdb3) and /boot on devicemapper raid1 (sda2 and sdb2). Since my symptoms look cosmetical only, I haven't tried deleting anything in /etc/grub.d.

tv@zulu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.10
Release: 13.10
Codename: saucy

tv@zulu:~$ sudo update-grub
Generating grub.cfg ...
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sdb3
/dev/sda3. Check your device.map.
Found linux image: /boot/vmlinuz-3.11.0-12-generic
Found initrd image: /boot/initrd.img-3.11.0-12-generic
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sdb3
/dev/sda3. Check your device.map.
Found memtest86+ image: /memtest86+.bin
done

tv@zulu:~$ grep /dev/sd /proc/mounts
/dev/sdb3 / btrfs rw,relatime,space_cache 0 0
/dev/sdb3 /home btrfs rw,relatime,space_cache 0 0

tv@zulu:~$ grep /boot /proc/mounts
/dev/md0 /boot ext4 rw,relatime,data=ordered 0 0

tv@zulu:~$ sudo mdadm --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Mon Oct 28 10:01:06 2013
     Raid Level : raid1
     Array Size : 976320 (953.60 MiB 999.75 MB)
  Used Dev Size : 976320 (953.60 MiB 999.75 MB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Tue Dec 24 15:34:00 2013
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           Name : zulu:0 (local to host zulu)
           UUID : c65746ce:08f53527:8494833c:c4723a0d
         Events : 19

    Number Major Minor RaidDevice State
       0 8 18 0 active sync /dev/sdb2
       1 8 2 1 active sync /dev/sda2

Recently encountered this, and I turned up this page while searching for solutions, and I hate to turn this into a "forum" post but I wanted to leave this here for anyone else beating their head against the wall over this.

On my afflicted system one of the partitions that was part of my btrfs raid 1 array did not have a type. fdisk, changed the type to Linux and grub was happy.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers