XFS over LVM on a custom storage layout,can't boot MAAS with a UEFI Node

For additional information; It works just fine using EXT4 FS.

You must recommission a machine if you change it to UEFI. Did you run re-commissioning and then configure the disks?

Nope, it was always a UEFI node. The issue seems to be the kernel not loading XFS FS Module or not even taking account for.

Gael,

Can you provide the following info:

1. The MAAS install log (you can grab that from the UI, or you can use the following command):

maas <user> node-results read system_id=<your_system> result_type=1 | grep "\"data\"" | cut -d"\"" -f4 | base64 --decode

2. The config sent to the machine when you set the FS to XFS:

maas <user> machine get-curtin-config <system_id>

Hi Andres, sorry for the late answer, here are the requested informations:

Curtin config extract:

storage:
  config:
  - grub_device: true
    id: sda
    model: PERC 6/i
    name: sda
    ptable: gpt
    serial: 6d4ae520a1236f001dc35c8f049b092a
    type: disk
    wipe: superblock
  - device: sda
    id: sda-part1
    name: sda-part1
    number: 1
    offset: 4194304B
    size: 96468992B
    type: partition
    uuid: 88a0df20-c224-4637-ad93-1d932e065a77
    wipe: superblock
  - device: sda
    id: sda-part2
    name: sda-part2
    number: 2
    size: 499122176B
    type: partition
    uuid: 1df4c42e-a94c-41d9-887f-9f2139425029
    wipe: superblock
  - device: sda
    id: sda-part3
    name: sda-part3
    number: 3
    size: 145559126016B
    type: partition
    uuid: 14870e21-4ef7-4058-baf1-8ae1148bb1b0
    wipe: superblock
  - devices:
    - sda-part3
    id: vg0
    name: vg0
    type: lvm_volgroup
    uuid: 1cae2f4d-ea47-45df-9d33-d1b77f23ee3f
  - id: vg0-lv0
    name: lv0
    size: 145554931712B
    type: lvm_partition
    volgroup: vg0
  - fstype: vfat
    id: sda-part1_format
    label: ''
    type: format
    uuid: 0bea118f-558e-4235-8547-644c76078066
    volume: sda-part1
  - fstype: xfs
    id: sda-part2_format
    label: ''
    type: format
    uuid: a45a16b8-018c-4a24-b9d8-aee19ca4566e
    volume: sda-part2
  - fstype: xfs
    id: vg0-lv0_format
    label: ''
    type: format
    uuid: 48691520-0025-4e6c-a7c0-50bb0ac30713
    volume: vg0-lv0
  - device: vg0-lv0_format
    id: vg0-lv0_mount
    options: ''
    path: /
    type: mount
  - device: sda-part2_format
    id: sda-part2_mount
    options: ''
    path: /boot
    type: mount
  - device: sda-part1_format
    id: sda-part1_mount
    options: ''
    path: /boot/efi
    type: mount
  version: 1

And here is the deploy result:

curtin: Installation started. (0.1.0~bzr532-0ubuntu1~16.04.1)
third party drivers not installed or necessary.
Creating new GPT entries.
The operation has completed successfully.
  Logical volume "lv0" created.
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Get:5 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7532 kB]
Get:6 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB]
Get:7 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [656 kB]
Get:8 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages [8064 B]
Get:9 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [544 kB]
Get:10 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [16.2 kB]
Get:11 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages [4860 B]
Get:12 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages [5896 B]
Get:13 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages [384 kB]
Get:14 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [179 kB]
Get:15 http://archive.ubunt...

Thank you for the configuration. I can reproduce the issue and confirm that if you use ext4 for the root filesystem, the deployment works.

I've dup'ed this against the grub2 bug which is where the fix is needed.

Hi ryan, thanks a lot for the following and answer.
Do we have an expected time of resolve for this patch? Seems to be pretty critical.

If you need an immediate fix, change the fstype on your /boot partition to
ext4.

There's no eta on when grub2 will figure out how to install /boot
filesystem modules into /boot/efi/EFI/ubuntu/<target>/

On Wed, Nov 15, 2017 at 1:54 PM, Gaël THEROND <email address hidden>
wrote:

> *** This bug is a duplicate of bug 1652822 ***
> https://bugs.launchpad.net/bugs/1652822
>
> Hi ryan, thanks a lot for the following and answer.
> Do we have an expected time of resolve for this patch? Seems to be pretty
> critical.
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1731490
>
> Title:
> XFS over LVM on a custom storage layout,can't boot MAAS with a UEFI
> Node
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1731490/+subscriptions
>