PXE image does not support mdraid metadata 1.2

[Andrea Ieri]

I have a host booting in EFI mode with the following layout:

/boot/efi -> fat32 -> md0 -> RAID1 over sda1+sdb1 (GPT)
/boot -> ext4 -> md1 -> RAID1 over sda2+sdb2 (GPT)
/ -> ext4 -> md2 -> RAID1 over sda3+sdb3 (GPT)

The raid uses metadata v1.2

When I PXE boot the host, grub attempts to run:

search --set=root --file /efi/ubuntu/grubx64.efi
chainloader /efi/ubuntu/grubx64.efi

This fails because no (md/X) devices are found.

I think this may be due to the fact that module mdraid1x isn't loaded.
If I try to boot manually from the grub CLI, insmod mdraid1x fails due to the module being unavailable.

[Andres Rodriguez (andreserl)]

I don’t think the issue you are describing is the root cause of this issue. First a few questions:

1. Is this a RAID configuration that MAAS deployed? (E.g software raid) or is this a fake raid device?

2. How is the power configuration of this machine?

3. I think this could actually be a deuicate of https://bugs.launchpad.net/maas/+bug/1792401

[Andrea Ieri (aieri)]

Right, sorry I didn't specify it. Yes, the RAID1 was created from the MAAS UI (it's md software raid, not fake raid).
If it was a fake raid grub would be able to read the partitions directly.

Power configuration is standard IPMI LAN 2.0

[Andres Rodriguez (andreserl)]

Hi All,

I think the issue is a duplicate of [1]. Cna you guys test the patch attached in there and confirm whether this fixes the issue?

https://bugs.launchpad.net/maas/+bug/1792401

[Andrea Ieri (aieri)]

Hi Andres,

I see the fix will be in maas 2.3.6, and that's not out yet, so I can't test too easily. Once that's released, I'll be happy to try deploying this setup again.

[Launchpad Janitor (janitor)]

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