grub-probe error: cannot find a GRUB drive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub-installer (Ubuntu) |
Fix Released
|
High
|
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/
Jul 7 14:33:51 debconf: <-- 0 OK
Jul 7 14:33:51 grub-installer: info: Installing grub on '/dev/disk/
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/
Jul 7 14:33:53 grub-installer: /usr/sbin/
Jul 7 14:33:53 grub-installer: error: Running 'grub-install --no-floppy --force "/dev/disk/
Jul 7 14:33:53 debconf: --> SUBST grub-installer/
Jul 7 14:33:53 debconf: Adding [BOOTDEV] -> [/dev/disk/
Jul 7 14:33:53 debconf: <-- 0
Jul 7 14:33:53 debconf: --> INPUT critical grub-installer/
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.
Changed in grub (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
affects: | grub (Ubuntu) → grub2 (Ubuntu) |
affects: | grub2 (Ubuntu) → grub-installer (Ubuntu) |
Changed in grub-installer (Ubuntu): | |
assignee: | nobody → Colin Watson (cjwatson) |
tags: | added: iso-testing |
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.