During our weekly testing in the certification servers, in one of the servers, the installation failed when installing grub2 in one of the servers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debian-installer (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: debian-installer
During our weekly testing, one of the installations run out of memory and failed during the grub-installer phase:
Feb 9 16:15:01 debconf: Adding [BOOTDEV] -> [/dev/sda]
Feb 9 16:15:01 debconf: <-- 0
Feb 9 16:15:01 debconf: --> PROGRESS INFO grub-installer/
Feb 9 16:15:01 debconf: <-- 0 OK
Feb 9 16:15:01 grub-installer: info: Installing grub on '/dev/sda'
Feb 9 16:15:01 grub-installer: info: grub-install supports --no-floppy
Feb 9 16:15:01 grub-installer: info: Running chroot /target grub-install --no-floppy --force "/dev/sda"
Feb 9 16:15:04 grub-installer: /usr/sbin/
Feb 9 16:15:04 grub-installer: /usr/sbin/
Feb 9 16:15:04 grub-installer: error: Running 'grub-install --no-floppy --force "/dev/sda"' failed.
Feb 9 16:15:04 debconf: --> SUBST grub-installer/
Feb 9 16:15:04 debconf: Adding [BOOTDEV] -> [/dev/sda]
Feb 9 16:15:04 debconf: <-- 0
Feb 9 16:15:04 debconf: --> INPUT critical grub-installer/
Feb 9 16:15:04 debconf: <-- 0 question will be asked
Feb 9 16:15:04 debconf: --> GO
Changed in debian-installer (Ubuntu): | |
status: | New → Incomplete |
Feb 9 16:09:18 kernel: [ 0.000000] 1159MB HIGHMEM available.
Feb 9 16:09:18 kernel: [ 0.000000] 887MB LOWMEM available.
No obvious justification for running out of memory here, then. Can you
run this after the failure?
for x in dev proc sys; do mount --bind /$x /target/$x; done install. out 2>&1
chroot /target grub-install --no-floppy --force --debug /dev/sda >/tmp/grub-
for x in dev proc sys; do umount /target/$x; done
Then post /tmp/grub- install. out here. Thanks.