Deployment fails when UEFI partition is on a separate disk to the root partition

Bug #1842094 reported by Dan MacDonald
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned
curtin
Triaged
Medium
Unassigned

Bug Description

I am running MAAS 2.4.2 under Ubuntu 18.04.

I want to deploy 18.04 using ZFS for the root disk onto a Dell PowerEdge R630 that has 2x500GB SAS drives in RAID 0 and a 500GB NVME SSD attached to a PCIe M.2 adapter. Unfortunately, the R630 cannot boot directly off of the NVME SSD and MAAS doesn't allow using zfsroot partitions in BIOS mode so if I want this to work I would have to have the UEFI boot partition installed on the SAS drives and zfsroot on the SSD. I have attempted this several times and commissioning works fine plus the installation succeeds but ultimately the deployment fails because I end up at the GRUB prompt and it doesn't boot into the OS post deployment so deployment times out and fails.

I have got this hardware configuration to work successfully with MAAS by using BIOS mode boot, creating a small /boot partition on the SAS drive and using ext4 for the root partition on the NVME SSD but really I want to use ZFS. There is nothing in GRUB or ZFS that depends on UEFI so I would like to see this restriction/requirement removed.

Is deploying with /boot/efi (in UEFI boot mode) on a separate disk to the root partition not supported? If that is the case, MAAS should prevent deployment from starting.

Revision history for this message
Blake Rouse (blake-rouse) wrote :

Please provide the following information documented here: https://discourse.maas.io/t/getting-curtin-debug-logs/169

Changed in maas:
status: New → Incomplete
Revision history for this message
Dan MacDonald (allcoms) wrote :

Hi Blake

I tried to follow the instructions you provided a link to but the following command did not work for me (after installing jq, which wasn't installed previously):

maas dan node-results read system_id=atp33e name=/tmp/curtin-logs.tar | jq -r .[0].data | base64 -d > curtin-logs.tar

So the command I ran instead was:

maas dan node-results read system_id=atp33e > maas-zfs-uefi-curtin-logs.txt

Hopefully the attached logs are still of use?

Revision history for this message
Dan MacDonald (allcoms) wrote :
Revision history for this message
Dan MacDonald (allcoms) wrote :
Revision history for this message
Dan MacDonald (allcoms) wrote :
Changed in maas:
status: Incomplete → New
Changed in maas:
status: New → Invalid
Revision history for this message
Ryan Harper (raharper) wrote :

Thanks for filing the bug. The logs are helpful. I'll recreate the failure with the provided storage config and see if that helps sort out what's missing.

Changed in curtin:
importance: Undecided → Medium
status: New → Triaged
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.