Failure on RAID1 bootloader update

[dimaguy]

I use universalBlue Aurora and I've noticed that I'm getting a noisy startup where bootupd tries to update the bootloader, but is failing with the following logs:

Running as unit: bootupd.service
error: Failed to update EFI: Failed to mount "/dev/nvme0n1p1": Subprocess failed: ExitStatus(unix_wait_status(8192))
mount: /boot/efi: fsconfig() failed: /dev/nvme0n1p1: Can't lookup blockdev.
       dmesg(1) may have more information after failed mount system call.

dmesg doesnt mention anything meaningful

Currently I'm on a Lenovo Thinkpad, it has an OEM Raid1 setup with Intel RST.

My blkid:

/dev/nvme0n1: TYPE="isw_raid_member"
/dev/md126p2: UUID="677b7145-fc97-4fb2-93a9-fff1b4ded0a2" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d7110fce-5560-4c6d-8cca-5ca025ac1edf"
/dev/md126p3: LABEL="fedora_aurora" UUID="9e9f309f-5014-4386-b5c0-f4903e979634" UUID_SUB="df7a423d-974c-455c-9361-4409b051b65c" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="03a655f8-aad8-45b0-97a7-569c85f3ad7c"
/dev/md126p1: UUID="E722-FBB9" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="fe375d77-9242-4944-b2ef-fcc29b4ac2aa"
/dev/nvme1n1: TYPE="isw_raid_member"
/dev/zram0: LABEL="zram0" UUID="6c5d0ff8-386c-4532-92f1-c2b11c694dd3" TYPE="swap"

bootupd version: 0.2.32

bootupd status:

Running as unit: bootupd.service
Component EFI
  Installed: grub2-efi-ia32-1:2.12-40.fc43.x86_64,grub2-efi-x64-1:2.12-40.fc43.x86_64,shim-ia32-15.8-3.x86_64,shim-x64-15.8-3.x86_64
  Update: Available: grub2-1:2.12-40.fc43,shim-15.8-3
Detected: BIOS: unknown
Boot method: EFI

Is there anything I can do to fix this? is this even the right place to report?

[HuijingHei]

Yes, this is the right place for the issue. Could you also help to run lsblk to better understand the partition layout?And better sudo sfdisk -J /dev/md126?

[dimaguy]

❯ sudo lsblk
Place your right index finger on the fingerprint reader
NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
zram0       251:0    0     8G  0 disk  [SWAP]
nvme1n1     259:0    0 953,9G  0 disk  
├─md126       9:126  0 953,9G  0 raid1 
│ ├─md126p1 259:2    0   600M  0 part  /boot/efi
│ ├─md126p2 259:3    0     2G  0 part  /boot
│ └─md126p3 259:4    0 951,3G  0 part  /usr/bin/swtpm
│                                      /var/home
│                                      /var
│                                      /sysroot/ostree/deploy/fedora/var
│                                      /sysroot
│                                      /etc
└─md127       9:127  0     0B  0 md    
nvme0n1     259:1    0 953,9G  0 disk  
├─md126       9:126  0 953,9G  0 raid1 
│ ├─md126p1 259:2    0   600M  0 part  /boot/efi
│ ├─md126p2 259:3    0     2G  0 part  /boot
│ └─md126p3 259:4    0 951,3G  0 part  /usr/bin/swtpm
│                                      /var/home
│                                      /var
│                                      /sysroot/ostree/deploy/fedora/var
│                                      /sysroot
│                                      /etc
└─md127       9:127  0     0B  0 md 

sudo parted -l
Warning: Not all of the space available to /dev/nvme0n1 appears to be used, you
can fix the GPT to use all of the space (an extra 4784 blocks) or continue with
the current setting? 
Fix/Ignore? ^C                                                            
Model: SAMSUNG MZVLC1T0HFLU-00BLL (nvme)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  630MB   629MB   fat32        EFI System Partition  boot, esp
 2      630MB   2778MB  2147MB  ext4                               bls_boot
 3      2778MB  1024GB  1021GB  btrfs


Model: Linux Software RAID Array (md)
Disk /dev/md126: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  630MB   629MB   fat32        EFI System Partition  boot, esp
 2      630MB   2778MB  2147MB  ext4                               bls_boot
 3      2778MB  1024GB  1021GB  btrfs


Warning: Not all of the space available to /dev/nvme1n1 appears to be used, you can fix the GPT to use all of the space (an extra 4784 blocks) or continue with the current setting? 
Fix/Ignore? ^C                                                            
Model: SAMSUNG MZVLC1T0HFLU-00BLL (nvme)
Disk /dev/nvme1n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  630MB   629MB   fat32        EFI System Partition  boot, esp
 2      630MB   2778MB  2147MB  ext4                               bls_boot
 3      2778MB  1024GB  1021GB  btrfs


Model: Unknown (unknown)
Disk /dev/zram0: 8590MB
Sector size (logical/physical): 4096B/4096B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system     Flags
 1      0,00B  8590MB  8590MB  linux-swap(v1)

[HuijingHei]

Thank you @dimaguy for the info.

Guess in this case we should update the bootloader using /dev/md126p1 directly, instead of using the back devices. @travier WDYT?

I tried to setup the same env as RAID1 with 2 disks, but get Failed to find a suitable stage1 device: EFI system Partation cannot be of type mdmember, looks it need the special hardware.