When starting a node with multiple non-RAID hard disks, GRUB installation can pause waiting for user input at the console

Bug #1317655 reported by Rod Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Low
Unassigned

Bug Description

When a computer has multiple non-RAID hard disks, a MAAS installation will sometimes (but not always) pause late in the installation phase to ask the user where to install GRUB. (See the attached screen shot.) For a network installation tool like MAAS, this is obviously a serious problem. I'm also attaching /var/log/syslog from the system being installed, at the point when the GRUB installation prompt appeared on the screen.

Revision history for this message
Rod Smith (rodsmith) wrote :
Revision history for this message
Rod Smith (rodsmith) wrote :
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Which installer are you using, fast, or d-i?

Changed in maas:
status: New → Incomplete
Revision history for this message
Rod Smith (rodsmith) wrote :

d-i

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Does this happen with the fast installer? We are considering deprecating d-i anyway.

Revision history for this message
Rod Smith (rodsmith) wrote :

On one system, I had no problems with the fast installer. With another one, the fast installer installs OK, but then tries to boot from the second disk (which on my test had a leftover installation that booted instead of the MAAS-created one). If you think that's a sufficiently different symptom, I can file a new bug report for it.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

That one is possibly related to the bug you reported here https://bugs.launchpad.net/maas/+bug/1307614 but for sure it's separate to the d-i problem.

Changed in maas:
status: Incomplete → Triaged
importance: Undecided → Low
tags: added: d-i packaging
tags: added: provisioning
removed: packaging
Revision history for this message
Rod Smith (rodsmith) wrote :

I doubt if it's related to that bug -- at least, not closely enough to be meaningful. (Both relate to device enumeration, though.) After experimenting a bit to ascertain what was happening, I've opened a new one (bug 1319966).

Changed in maas:
status: Triaged → Invalid
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.