Ephemeral boot error: alloc magic is broken at 0x94eceac0: 94e05880

Bug #1716784 reported by David Britton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Unassigned

Bug Description

Xenail, MAAS: 2.2.2-6099-g8751f91-0ubuntu1~16.04.1 (stable ppa)

I get the Following error on boot of my systems into the commissioning image:

Booting under MAAS direction...
error: File not found.
alloc magic is broken at 0x94eceac0: 94e05880
Aborted. Press any key to exit. error: you need to load the kernel first.

Tags: xenial
Revision history for this message
David Britton (dpb) wrote :
Revision history for this message
David Britton (dpb) wrote :
Revision history for this message
Andres Rodriguez (andreserl) wrote :

From our irc discussion:

18:27 < dpb> but it's booted just fine as recently as 2 days ago

A new grub version was published on 2017-07-28 in 2.02~beta2-36ubuntu3.12. This seems like it could be a regression in grub that 2.02~beta2-36ubuntu3.13 (currently in proposed) could probably fix.

Changed in maas:
status: New → Incomplete
tags: added: xenial
Revision history for this message
David Britton (dpb) wrote :

I'm still getting this. I tried updating the NUC firmware where this repeats, no joy.

Maas version: MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1). My images are all "synced" as of today.

Anything else I can try?

Changed in maas:
status: Incomplete → New
Revision history for this message
David Britton (dpb) wrote :

I found out a trick:

https://askubuntu.com/questions/760228/booting-under-maas-direction-error-file-not-found

This led me to think there was an error with the kernel selected for the ephemeral boot, so, I went into settings, 16.04 was selected, but the kernel was 'no minimum kernel'. I changed that to 16.04-hwe. I then was able to enlist. After that, I switched it back to 'no minimum kernel', and it still enlists fine.

I suspect some kind of migration is amiss, and it was trying to tell the node to use a kernel that was no longer there, or not referenced in the right way.

Anyway, appears working now with that workaround.

Scott Moser (smoser)
no longer affects: grub2 (Ubuntu)
Changed in maas:
importance: Undecided → High
milestone: none → 2.4.0alpha1
status: New → Triaged
Changed in maas:
milestone: 2.4.0alpha1 → 2.4.0alpha2
Changed in maas:
milestone: 2.4.0alpha2 → 2.4.0beta1
Changed in maas:
milestone: 2.4.0beta1 → 2.4.0beta2
Changed in maas:
milestone: 2.4.0beta2 → 2.4.0beta3
Changed in maas:
milestone: 2.4.0beta3 → 2.4.0beta4
Changed in maas:
milestone: 2.4.0beta4 → 2.4.x
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

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.