deployment-iso

History

Michael Prokop 41029ed891 MT#61264 Mark EFI partition as such only when running in an EFI environment On Debian/trixie we get a failing efi.mount systemd unit: \| root@sp1:~# systemctl --failed \| UNIT LOAD ACTIVE SUB DESCRIPTION \| ● efi.mount loaded failed failed EFI System Partition Automount \| \| Legend: LOAD → Reflects whether the unit definition was properly loaded. \| ACTIVE → The high-level unit activation state, i.e. generalization of SUB. \| SUB → The low-level unit activation state, values depend on unit type. \| \| 1 loaded units listed. \| \| root@sp1:~# systemctl status efi.mount \| × efi.mount - EFI System Partition Automount \| Loaded: loaded (/run/systemd/generator.late/efi.mount; generated) \| Active: failed (Result: exit-code) since Fri 2024-11-15 17:20:59 CET; 28min ago \| Invocation: 62c7b659dfd540e294f4b1f6fcda5e13 \| TriggeredBy: ● efi.automount \| Where: /efi \| What: /dev/disk/by-diskseq/9-part2 \| Docs: man:systemd-gpt-auto-generator(8) \| Mem peak: 1.5M \| CPU: 8ms \| \| Nov 15 17:20:59 sp1 systemd[1]: Mounting efi.mount - EFI System Partition Automount... \| Nov 15 17:20:59 sp1 mount[631]: mount: /efi: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error. \| Nov 15 17:20:59 sp1 mount[631]: dmesg(1) may have more information after failed mount system call. \| Nov 15 17:20:59 sp1 systemd[1]: efi.mount: Mount process exited, code=exited, status=32/n/a \| Nov 15 17:20:59 sp1 systemd[1]: efi.mount: Failed with result 'exit-code'. \| Nov 15 17:20:59 sp1 systemd[1]: Failed to mount efi.mount - EFI System Partition Automount. \| \| root@sp1:~# ls -la /efi \| ls: cannot open directory '/efi': No such device \| \| root@sp1:~# ls -la /dev/disk/by-diskseq/9-part2 \| lrwxrwxrwx 1 root root 10 Nov 15 17:20 /dev/disk/by-diskseq/9-part2 -> ../../sda2 \| \| root@sp1:~# blkid /dev/sda2 \| /dev/sda2: PARTLABEL="EFI System" PARTUUID="fa67b52e-c018-401d-ac71-fad324cad193" The efi.mount systemd unit is automatically generated by systemd-gpt-auto-generator. Quoting from systemd-gpt-auto-generator(8): \| The ESP is mounted to /boot/ if that directory exists and is not used \| for XBOOTLDR, and otherwise to /efi/ This got introduced as of systemd v254, see `6a488fa7cc` for details. Now having systemd v256.7-3 in current Debian/testing AKA trixie, we need to make sure to not present an EFI partition if we actually don't use it. So when we don't run in an EFI environment do not mark the second partition as EFI one. Change-Id: I546c77fce862a41594500a33da1178c5c6182a1a	6 months ago
..
boot	…
scripts	MT#61264 Mark EFI partition as such only when running in an EFI environment	6 months ago

Michael Prokop 41029ed891 MT#61264 Mark EFI partition as such only when running in an EFI environment

On Debian/trixie we get a failing efi.mount systemd unit:

| root@sp1:~# systemctl --failed
|   UNIT      LOAD   ACTIVE SUB    DESCRIPTION
| ● efi.mount loaded failed failed EFI System Partition Automount
|
| Legend: LOAD   → Reflects whether the unit definition was properly loaded.
|         ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
|         SUB    → The low-level unit activation state, values depend on unit type.
|
| 1 loaded units listed.
|
| root@sp1:~# systemctl status efi.mount
| × efi.mount - EFI System Partition Automount
|      Loaded: loaded (/run/systemd/generator.late/efi.mount; generated)
|      Active: failed (Result: exit-code) since Fri 2024-11-15 17:20:59 CET; 28min ago
|  Invocation: 62c7b659dfd540e294f4b1f6fcda5e13
| TriggeredBy: ● efi.automount
|       Where: /efi
|        What: /dev/disk/by-diskseq/9-part2
|        Docs: man:systemd-gpt-auto-generator(8)
|    Mem peak: 1.5M
|         CPU: 8ms
|
| Nov 15 17:20:59 sp1 systemd[1]: Mounting efi.mount - EFI System Partition Automount...
| Nov 15 17:20:59 sp1 mount[631]: mount: /efi: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.
| Nov 15 17:20:59 sp1 mount[631]:        dmesg(1) may have more information after failed mount system call.
| Nov 15 17:20:59 sp1 systemd[1]: efi.mount: Mount process exited, code=exited, status=32/n/a
| Nov 15 17:20:59 sp1 systemd[1]: efi.mount: Failed with result 'exit-code'.
| Nov 15 17:20:59 sp1 systemd[1]: Failed to mount efi.mount - EFI System Partition Automount.
|
| root@sp1:~# ls -la /efi
| ls: cannot open directory '/efi': No such device
|
| root@sp1:~# ls -la /dev/disk/by-diskseq/9-part2
| lrwxrwxrwx 1 root root 10 Nov 15 17:20 /dev/disk/by-diskseq/9-part2 -> ../../sda2
|
| root@sp1:~# blkid /dev/sda2
| /dev/sda2: PARTLABEL="EFI System" PARTUUID="fa67b52e-c018-401d-ac71-fad324cad193"

The efi.mount systemd unit is automatically generated by
systemd-gpt-auto-generator. Quoting from systemd-gpt-auto-generator(8):

| The ESP is mounted to /boot/ if that directory exists and is not used
| for XBOOTLDR, and otherwise to /efi/

This got introduced as of systemd v254, see
6a488fa7cc
for details. Now having systemd v256.7-3 in current Debian/testing AKA
trixie, we need to make sure to not present an EFI partition if we
actually don't use it.

So when we don't run in an EFI environment do not mark the second
partition as EFI one.

Change-Id: I546c77fce862a41594500a33da1178c5c6182a1a

boot

…

scripts MT#61264 Mark EFI partition as such only when running in an EFI environment 6 months ago