grub-probe error: cannot find a GRUB drive

Bug #602758 reported by Ronald McCollam on 2010-07-07
This bug affects 2 people
Affects Status Importance Assigned to Milestone
grub-installer (Ubuntu)
Colin Watson

Bug Description

Binary package hint: grub

Several systems in the hardware testing lab are unable to install grub. So far the only systems I have seen affected have been HP Proliant systems.

An example:
Today's daily build, ubuntu-server amd64 20100707
HP Proliant ML115

Relevant part of syslog:

Jul 7 14:33:51 debconf: --> PROGRESS INFO grub-installer/progress/step_install_loader
Jul 7 14:33:51 debconf: <-- 0 OK
Jul 7 14:33:51 grub-installer: info: Installing grub on '/dev/disk/by-id/ata-FB160C4081_6RX0VE18'
Jul 7 14:33:51 grub-installer: info: grub-install supports --no-floppy
Jul 7 14:33:51 grub-installer: info: Running chroot /target grub-install --no-floppy --force "/dev/disk/by-id/ata-FB160C4081_6RX0VE18"
Jul 7 14:33:53 grub-installer: /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/disk/by-id/ata-FB160C4081_6RX0VE18. Check your
Jul 7 14:33:53 grub-installer: error: Running 'grub-install --no-floppy --force "/dev/disk/by-id/ata-FB160C4081_6RX0VE18"' failed.
Jul 7 14:33:53 debconf: --> SUBST grub-installer/grub-install-failed BOOTDEV /dev/disk/by-id/ata-FB160C4081_6RX0VE18
Jul 7 14:33:53 debconf: Adding [BOOTDEV] -> [/dev/disk/by-id/ata-FB160C4081_6RX0VE18]
Jul 7 14:33:53 debconf: <-- 0
Jul 7 14:33:53 debconf: --> INPUT critical grub-installer/grub-install-failed
Jul 7 14:33:53 debconf: <-- 0 question will be asked

Similar errors are occurring on several other Proliant systems, with only the disk ID changing. (I can provide output from these as well if it is helpful.)

I will attach the full syslog and partman (in a tgz, as they are quite large uncompressed) as well as the output of lspci -vnvn from a working 10.04 LTS install on the same system.

Ronald McCollam (fader) wrote :
Ronald McCollam (fader) wrote :
Ronald McCollam (fader) wrote :

Incidentally, attempts to install legacy grub or LILO on these systems also fails. (I can collect logs if necessary.) Other Ubuntu releases (10.04 LTS, 8.04 LTS) install correctly so it does not appear to be a hardware issue.

Ameet Paranjape (ameetp) on 2010-07-07
Changed in grub (Ubuntu):
importance: Undecided → High
status: New → Triaged
Steve Langasek (vorlon) on 2010-07-07
affects: grub (Ubuntu) → grub2 (Ubuntu)
Colin Watson (cjwatson) on 2010-07-07
affects: grub2 (Ubuntu) → grub-installer (Ubuntu)
Changed in grub-installer (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
Fabio Marconi (fabiomarconi) wrote :

same problem on 20100707 Alternate amd64
see screenshot attached

Fabio Marconi (fabiomarconi) wrote :

impossible to install by LILO too, cause package lilo is not available

tags: added: iso-testing
Fabio Marconi (fabiomarconi) wrote :

ubuntu Desktop amd64 20100707 not affected

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package grub-installer - 1.49ubuntu12

grub-installer (1.49ubuntu12) maverick; urgency=low

  * Install grub-efi on i386/efi and amd64/efi subarchitectures.
  * Resolve symlinks in default boot device (LP: #602758).
 -- Colin Watson <email address hidden> Thu, 08 Jul 2010 13:03:01 +0100

Changed in grub-installer (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers