grub2 installation fails on 14.04 kickstart installation

Bug #1302529 reported by bekks
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
New
Undecided
Unassigned
kickseed (Ubuntu)
New
Undecided
Unassigned

Bug Description

== Regression details ==
Discovered in version: 14.04
Last known good version: 12.04

Hi!

I got hit by a bug that grub2 could not be installed when using 14.04 - while the exact same kickstart file works perfectly when using 12.04 for kickstarting.

The exact error (after the installer fails, and before pressing enter to continue) in tty4 is: "disk hd0 not found".

I'm attaching a screenshot of the error, when the automated installer fails.

The kickstart file snippet regarding bootloader installation after partitioning is this:

-----<snip>-----
zerombr yes
bootloader --location=mbr
clearpart --initlabel --drives=sda
part /boot --fstype=ext4 --size=256 --asprimary
part swap --size=512 --asprimary
part / --fstype=ext4 --size=1 --grow --asprimary
-----<snap>-----

I am running the installation using the 14.04 server beta2 cd, and adding "toram ks=http://mylocalwebserverip/ubuntutest.ks" to the kernel options prior booting, the result stays the same without "toram".

Best regards,
bekks

Revision history for this message
bekks (bekks) wrote :
bekks (bekks)
tags: added: grub regression-release
bekks (bekks)
description: updated
bekks (bekks)
description: updated
Revision history for this message
bekks (bekks) wrote :

Added the output of:

grub-install --verbose --force "(hd0)"

from within a chroot created with "chroot /target /bin/bash" right after the installer failed.

Revision history for this message
bekks (bekks) wrote :

Added the output of:

grub-install --verbose --force /dev/sda

from within a chroot created with "chroot /target /bin/bash" right after the installer failed.

This works fine, and exits with $? being 0.

Revision history for this message
Colin Watson (cjwatson) wrote :

This looks identical to bug 1292628, which should be fixed in more recent daily builds; the fix missed beta2 by a day or two, though.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.