Can't deploy OS on the node with embedded RAID

Bug #1902315 reported by Andrey Grebennikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Expired
Undecided
Unassigned

Bug Description

MAAS 2.8, trying to install the OS onto the Intel server with the embedded RAID.
Because MAAS can't make mirrored EFI partition with software RAID, it was decided to use embedded RAID to create a mirrored device and deploy OS on top of it.

The logical drive is created in the BIOS, however the way it works is that the firmware presents the pre-created software RAID to the OS, along with the physical drives as well.
Problem #1: Once MAAS commissions the node, only physical drives are visible. It is only possible to choose one of them for deploying the OS.
Problem #2: During the deployment the installer finds MD device (that is presented by the firmware) but it doesn't have any instruction from MAAS what to do with it, and the installation fails (deployment log is attached as HW raid1 build.rtf)

Also attaching the sos report from the node that's been commissioned for further analysis of the way software RAID is presented to the OS.

Revision history for this message
Andrey Grebennikov (agrebennikov) wrote :
Revision history for this message
Andrey Grebennikov (agrebennikov) wrote :
Revision history for this message
Alberto Donato (ack) wrote :

Is the hardware raid configured before commissioning the machine?
I'm not quite sure why the OS from the commissioning environment would see the two disks and not the raid while the installed would at deploy time.

Changed in maas:
status: New → Incomplete
Revision history for this message
Andrey Grebennikov (agrebennikov) wrote :

Yes, the raid is configured at the bios level.
The reason for the commissioning to work this way - it only reads info about the block devices and doesn't care about MD ones. Software raid in the bios still exposes the backend block devices to the OS along with the MD one.

Revision history for this message
Alberto Donato (ack) wrote :

Any chance you could test with a more recent maas version? We've changed how we collect commissioning info in 2.9 (and expanded it in 3.0).

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
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.