FS#29928 - Grub install failure, testing ISO

Attached to Project: Release Engineering
Opened by Greg Sutcliffe (gwmngilfen) - Thursday, 17 May 2012, 11:24 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 05 August 2012, 15:00 GMT
Task Type Bug Report
Category AIF
Status Closed
Assigned To Dieter Plaetinck (Dieter_be)
Architecture All
Severity Critical
Priority Normal
Reported Version testbuild (specify!)
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Using archlinux-2012.05.17_04-00-01-netinstall-dual.iso, QEMU-KVM x86_64 machine, IDE Disk on /dev/sda, automated install.

At the end of the install, grub-install will fail:

/dev/mapper/../dm-0 does not have any corresponding BIOS drive.

It looks like the grub stage files aren't being copied into /mnt/boot/grub, which might be related. This can be worked around as follows:

chroot /mnt /bin/bash
grub-install --recheck /dev/sda

I'm not yet sure why the installer environment behaves differently to chroot. On a Virtio Disk (/dev/vda) then this workaround doesn't function, and you cannot boot the system.
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 05 August 2012, 15:00 GMT
Reason for closing:  Won't fix
Additional comments about closing:  No longer relevant.
Comment by Thomas Hebb (tchebb) - Monday, 21 May 2012, 02:08 GMT
This appears to have been introduced in this commit: https://github.com/Dieterbe/aif/commit/07aacb72d27e12521025ec346b978a079d4ee05e

I've written a patch which fixes it: https://mailman.archlinux.org/pipermail/arch-releng/2012-May/002552.html
Comment by Tim Dysinger (dysinger) - Wednesday, 13 June 2012, 01:00 GMT
I've just seen this also
Comment by Robert Lewis (niriven) - Saturday, 07 July 2012, 21:16 GMT
Chroot did not work for me, but this did:

grub-install --recheck --root-directory=/mnt /dev/sda

Loading...