Why should I mount both /boot and /efi

sergik82 · 2023-10-04 16:47:02

A couple months ago I faced with this issue, my laptop can't start properly if /boot and /efi wasn't mounted... and still can't realize for what it needs

twelveeighty · 2023-10-04 19:11:07

What does "can't start properly" mean? Please post actual error messages. Which of the three typical EFI scenarios did you configure?

sergik82 · 2023-10-05 07:07:38

twelveeighty wrote:

What does "can't start properly" mean? Please post actual error messages. Which of the three typical EFI scenarios did you configure?

I guess... It would better if I show sys log when /efi not mounted
http://0x0.st/HWVu.txt

seth · 2023-10-05 07:29:36

Oct 05 11:27:57 invisible systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 05 11:27:57 invisible systemd[1]: Set up automount EFI System Partition Automount.
Oct 05 11:27:58 invisible systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 05 11:27:58 invisible systemd[1]: efi.automount: Got automount request for /efi, triggered by 527 (bootctl)
Oct 05 11:29:28 invisible systemd[1]: Dependency failed for EFI System Partition Automount.
Oct 05 11:29:28 invisible systemd[1]: efi.mount: Job efi.mount/start failed with result 'dependency'.
Oct 05 11:29:28 invisible bootctl[527]: Unable to write 'LoaderSystemToken' EFI variable, ignoring: Input/output error
Oct 05 11:29:29 invisible systemd[1]: TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 05 11:29:29 invisible systemd[1]: TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 05 11:29:34 invisible containerd[631]: time="2023-10-05T11:29:34.174986793+05:00" level=info msg="Start cri plugin with config {PluginConfig:{ContainerdConfig:{Snapshotter:overlayfs DefaultRuntimeName:runc DefaultRuntime:{Type: Path: Engine: PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[] PrivilegedWithoutHostDevices:false PrivilegedWithoutHostDevicesAllDevicesAllowed:false BaseRuntimeSpec: NetworkPluginConfDir: NetworkPluginMaxConfNum:0 Snapshotter: SandboxMode:} UntrustedWorkloadRuntime:{Type: Path: Engine: PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[] PrivilegedWithoutHostDevices:false PrivilegedWithoutHostDevicesAllDevicesAllowed:false BaseRuntimeSpec: NetworkPluginConfDir: NetworkPluginMaxConfNum:0 Snapshotter: SandboxMode:} Runtimes:map[runc:{Type:io.containerd.runc.v2 Path: Engine: PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[BinaryName: CriuImagePath: CriuPath: CriuWorkPath: IoGid:0 IoUid:0 NoNewKeyring:false NoPivotRoot:false Root: ShimCgroup: SystemdCgroup:false] PrivilegedWithoutHostDevices:false PrivilegedWithoutHostDevicesAllDevicesAllowed:false BaseRuntimeSpec: NetworkPluginConfDir: NetworkPluginMaxConfNum:0 Snapshotter: SandboxMode:podsandbox}] NoPivot:false DisableSnapshotAnnotations:true DiscardUnpackedLayers:false IgnoreBlockIONotEnabledErrors:false IgnoreRdtNotEnabledErrors:false} CniConfig:{NetworkPluginBinDir:/opt/cni/bin NetworkPluginConfDir:/etc/cni/net.d NetworkPluginMaxConfNum:1 NetworkPluginSetupSerially:false NetworkPluginConfTemplate: IPPreference:} Registry:{ConfigPath: Mirrors:map[] Configs:map[] Auths:map[] Headers:map[]} ImageDecryption:{KeyModel:node} DisableTCPService:true StreamServerAddress:127.0.0.1 StreamServerPort:0 StreamIdleTimeout:4h0m0s EnableSelinux:false SelinuxCategoryRange:1024 SandboxImage:registry.k8s.io/pause:3.8 StatsCollectPeriod:10 SystemdCgroup:false EnableTLSStreaming:false X509KeyPairStreaming:{TLSCertFile: TLSKeyFile:} MaxContainerLogLineSize:16384 DisableCgroup:false DisableApparmor:false RestrictOOMScoreAdj:false MaxConcurrentDownloads:3 DisableProcMount:false UnsetSeccompProfile: TolerateMissingHugetlbController:true DisableHugetlbController:true DeviceOwnershipFromSecurityContext:false IgnoreImageDefinedVolumes:false NetNSMountsUnderStateDir:false EnableUnprivilegedPorts:false EnableUnprivilegedICMP:false EnableCDI:false CDISpecDirs:[/etc/cdi /var/run/cdi] ImagePullProgressTimeout:1m0s DrainExecSyncIOTimeout:0s} ContainerdRootDir:/var/lib/containerd ContainerdEndpoint:/run/containerd/containerd.sock RootDir:/var/lib/containerd/io.containerd.grpc.v1.cri StateDir:/run/containerd/io.containerd.grpc.v1.cri}"
Oct 05 11:29:34 invisible systemd[1]: efi.automount: Got automount request for /efi, triggered by 562 (systemd-logind)
Oct 05 11:31:05 invisible systemd[1]: Dependency failed for EFI System Partition Automount.
Oct 05 11:31:05 invisible systemd[1]: efi.mount: Job efi.mount/start failed with result 'dependency'.
Oct 05 11:31:07 invisible systemd[1]: efi.automount: Got automount request for /efi, triggered by 562 (systemd-logind)
Oct 05 11:32:37 invisible systemd[1]: Dependency failed for EFI System Partition Automount.
Oct 05 11:32:37 invisible systemd[1]: efi.mount: Job efi.mount/start failed with result 'dependency'.
Oct 05 11:32:37 invisible systemd[1]: efi.automount: Got automount request for /efi, triggered by 562 (systemd-logind)
Oct 05 11:34:07 invisible systemd[1]: Dependency failed for EFI System Partition Automount.
Oct 05 11:34:07 invisible systemd[1]: efi.mount: Job efi.mount/start failed with result 'dependency'.
Oct 05 11:34:08 invisible systemd[1]: efi.automount: Got automount request for /efi, triggered by 562 (systemd-logind)

Oct 05 11:29:28 invisible systemd[1]: dev-disk-by\x2ddiskseq-6\x2dpart1.device: Job dev-disk-by\x2ddiskseq-6\x2dpart1.device/start timed out.
Oct 05 11:29:28 invisible systemd[1]: Timed out waiting for device /dev/disk/by-diskseq/6-part1.
Oct 05 11:29:28 invisible systemd[1]: Dependency failed for File System Check on /dev/disk/by-diskseq/6-part1.
Oct 05 11:29:28 invisible systemd[1]: Dependency failed for EFI System Partition Automount.
Oct 05 11:29:28 invisible systemd[1]: efi.mount: Job efi.mount/start failed with result 'dependency'.
Oct 05 11:29:28 invisible systemd[1]: systemd-fsck@dev-disk-by\x2ddiskseq-6\x2dpart1.service: Job systemd-fsck@dev-disk-by\x2ddiskseq-6\x2dpart1.service/start failed with result 'dependency'.
Oct 05 11:29:28 invisible systemd[1]: dev-disk-by\x2ddiskseq-6\x2dpart1.device: Job dev-disk-by\x2ddiskseq-6\x2dpart1.device/start failed with result 'timeout'.
Oct 05 11:29:28 invisible bootctl[527]: ! Mount point '/boot' which backs the random seed file is world accessible, which is a security hole! !
Oct 05 11:29:28 invisible bootctl[527]: ! Random seed file '/boot/loader/random-seed' is world accessible, which is a security hole! !
Oct 05 11:29:28 invisible bootctl[527]: Random seed file /boot/loader/random-seed successfully refreshed (32 bytes).
Oct 05 11:29:28 invisible bootctl[527]: Unable to write 'LoaderSystemToken' EFI variable, ignoring: Input/output error
Oct 05 11:29:29 invisible systemd[1]: Finished Update Boot Loader Random Seed.

It looks like there's a bogus automount entry in your fstab and bootctl doesn't like the permissions on your /boot - but the system boots fine?

sergik82 · 2023-10-05 14:52:57

thats my fstab... wthat's wrong with it?

 cat /etc/fstab 
# /dev/md126p2
UUID=406fddcb-6753-4c8a-932d-0be516155b6e	/         	f2fs      	rw,relatime,lazytime,background_gc=on,discard,no_heap,inline_xattr,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,discard_unit=block,memory=normal	0 1

# /dev/md126p1
UUID=88A0-8FE6      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 1
UUID=88A0-8FE6      	/efi     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 1

# /dev/sdc1
UUID=0f26927f-5657-4602-aec8-fab88920fedf	/home     	ext4      	rw,noatime,commit=60,barrier=0	0 2

/swapfile 		none 					swap 		defaults 	0 0

if I comment /efi volume I've got system stuck durind the boot proccess

seth · 2023-10-05 15:27:47

Oct 05 11:29:40 invisible systemd[1]: Reached target Multi-User System.
Oct 05 11:29:40 invisible systemd[1]: Reached target Graphical Interface.

You don't get "stuck", but bootctl waits for the /efi automount, likely https://bbs.archlinux.org/viewtopic.php … 8#p2006888

sergik82 · 2023-10-05 18:48:19

seth wrote:

Oct 05 11:29:40 invisible systemd[1]: Reached target Multi-User System.
Oct 05 11:29:40 invisible systemd[1]: Reached target Graphical Interface.
You don't get "stuck", but bootctl waits for the /efi automount, likely https://bbs.archlinux.org/viewtopic.php … 8#p2006888

systemctl list-units --type=automount
  UNIT                              LOAD   ACTIVE SUB     DESCRIPTION                                                  
  proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point

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. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

is it mean that, I should disable proc-sys-fs-binfmt_misc.automount than I'll able to get rid /efi volume from fstab?

seth · 2023-10-05 18:52:43

No.
Why are you trying to remove /efi from the fstab?
bootctl clearly doesn't like its absensence.

Though now I'm not sure where the dev-disk-by\x2ddiskseq-6\x2dpart1.device even comes from (but I've no experience w/ systemd-boot either)

sergik82 · 2023-10-05 19:00:45

seth wrote:

No.
Why are you trying to remove /efi from the fstab?

but it worked without /efi in the fstab file few months ago... for what it needs now?

seth · 2023-10-05 19:07:52

seth wrote:

bootctl clearly doesn't like its absensence

seth wrote:

I've no experience w/ systemd-boot

There was https://github.com/systemd/systemd/issues/28585 but that's supposed to be fixed.
When did your problems start *exactly* what what are the corresponding updates in your pacman log.

sergik82 · 2023-10-05 19:20:13

seth wrote:

one more question

efibootmgr   
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0002,0003,0004,0005,0006,0007,0008,0009,000A,000B,000C,000D,000E,000F,0010,0011,0012,0013,0014,0015,0016,0017,0018,0019,001A,001B,001C,001D,001E,001F,0020,0021,0022,0023,0024,0025,0026,0027,0028,0029,002A,002B,002C,002D,002E,002F,0030,0031,0032,0033,0034,0035,0036,0037,0038,0055,0045,0046,0049,003A,004E,0065,0074,0077,006F,0072,006B,0020,0044,0065,0076,0069,0063,0065,0000,0065,0000,0039,003C,003D,003B,003E,003F
Boot0001* UEFI OS	HD(1,GPT,61131728-a9bf-7c43-b939-0a6d3a1ee8ab,0x800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot0002* UEFI: IP4 Qualcomm Atheros PCIe Network Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(d8cb8a7f5468,0)/IPv4(0.0.0.00.0.0.0,0,0)0000424f
Boot0003* UEFI: IP6 Qualcomm Atheros PCIe Network Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(d8cb8a7f5468,0)/IPv6([::]:<->[::]:,0,0)0000424f
Boot0004* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0005* UEFI:Removable Device	BBS(130,,0x0)
Boot0006* UEFI:Network Device	BBS(131,,0x0)
Boot0007* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0008* UEFI:Removable Device	BBS(130,,0x0)
Boot0009* UEFI:Network Device	BBS(131,,0x0)
Boot000A* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot000B* UEFI:Removable Device	BBS(130,,0x0)
Boot000C* UEFI:Network Device	BBS(131,,0x0)
Boot000D* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot000E* UEFI:Removable Device	BBS(130,,0x0)
Boot000F* UEFI:Network Device	BBS(131,,0x0)
Boot0010* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0011* UEFI:Removable Device	BBS(130,,0x0)
Boot0012* UEFI:Network Device	BBS(131,,0x0)
Boot0013* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0014* UEFI:Removable Device	BBS(130,,0x0)
Boot0015* UEFI:Network Device	BBS(131,,0x0)
Boot0016* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0017* UEFI:Removable Device	BBS(130,,0x0)
Boot0018* UEFI:Network Device	BBS(131,,0x0)
Boot0019* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot001A* UEFI:Removable Device	BBS(130,,0x0)
Boot001B* UEFI:Network Device	BBS(131,,0x0)
Boot001C* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot001D* UEFI:Removable Device	BBS(130,,0x0)
Boot001E* UEFI:Network Device	BBS(131,,0x0)
Boot001F* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0020* UEFI:Removable Device	BBS(130,,0x0)
Boot0021* UEFI:Network Device	BBS(131,,0x0)
Boot0022* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0023* UEFI:Removable Device	BBS(130,,0x0)
Boot0024* UEFI:Network Device	BBS(131,,0x0)
Boot0025* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0026* UEFI:Removable Device	BBS(130,,0x0)
Boot0027* UEFI:Network Device	BBS(131,,0x0)
Boot0028* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0029* UEFI:Removable Device	BBS(130,,0x0)
Boot002A* UEFI:Network Device	BBS(131,,0x0)
Boot002B* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot002C* UEFI:Removable Device	BBS(130,,0x0)
Boot002D* UEFI:Network Device	BBS(131,,0x0)
Boot002E* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot002F* UEFI:Removable Device	BBS(130,,0x0)
Boot0030* UEFI:Network Device	BBS(131,,0x0)
Boot0031* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0032* UEFI:Removable Device	BBS(130,,0x0)
Boot0033* UEFI:Network Device	BBS(131,,0x0)
Boot0034* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0035* UEFI:Removable Device	BBS(130,,0x0)
Boot0036* UEFI:Network Device	BBS(131,,0x0)
Boot0037* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0038* UEFI:Removable Device	BBS(130,,0x0)
Boot0039* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot003B* UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot003C* UEFI:Removable Device	BBS(130,,0x0)
Boot003D* UEFI:Network Device	BBS(131,,0x0)
Boot003E* UEFI:Removable Device	BBS(130,,0x0)
Boot003F* UEFI:Network Device	BBS(131,,0x0)

after each reboot my boot records are multiplying... how can I change it?

seth · 2023-10-05 19:32:24

https://man.archlinux.org/man/efibootmgr.8#D

Idk, but I'd guess this is related to whatever is causing the failed automout attempts

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

sergik82 · 2023-10-05 19:43:48

seth wrote:

https://man.archlinux.org/man/efibootmgr.8#D
Idk, but I'd guess this is related to whatever is causing the failed automout attempts
Please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
bluetooth.service                        | bluetooth.target.wants
bumblebeed.service                       | graphical.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
docker.service                           | multi-user.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
haveged.service                          | sysinit.target.wants
lm_sensors.service                       | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

seth · 2023-10-05 19:54:11

You apparently have PA and pipewire active and likely want to use pipewire-pulse, but that's unrelated and otherwise this looks unsuspicious…

seth wrote:

When did your problems start *exactly* what what are the corresponding updates in your pacman log.

systemctl status 'dev-disk-by\x2ddiskseq-6\x2dpart1.device'
systemctl show 'dev-disk-by\x2ddiskseq-6\x2dpart1.device'

Arch Linux

#1 2023-10-04 16:47:02

Why should I mount both /boot and /efi

#2 2023-10-04 19:11:07

Re: Why should I mount both /boot and /efi

#3 2023-10-05 07:07:38

Re: Why should I mount both /boot and /efi

#4 2023-10-05 07:29:36

Re: Why should I mount both /boot and /efi

#5 2023-10-05 14:52:57

Re: Why should I mount both /boot and /efi

#6 2023-10-05 15:27:47

Re: Why should I mount both /boot and /efi

#7 2023-10-05 18:48:19

Re: Why should I mount both /boot and /efi

#8 2023-10-05 18:52:43

Re: Why should I mount both /boot and /efi

#9 2023-10-05 19:00:45

Re: Why should I mount both /boot and /efi

#10 2023-10-05 19:07:52

Re: Why should I mount both /boot and /efi

#11 2023-10-05 19:20:13

Re: Why should I mount both /boot and /efi

#12 2023-10-05 19:32:24

Re: Why should I mount both /boot and /efi

#13 2023-10-05 19:43:48

Re: Why should I mount both /boot and /efi

#14 2023-10-05 19:54:11

Re: Why should I mount both /boot and /efi

Board footer