boot.mount slowing down boot process

alba4k · Yesterday 17:17:36

I recently reinstalled arch on my laptop to use LUKS encryption.

However, I am noticing slower boot times and the problem appears to be boot.mount, according to systemd-analyze.

systemd-analyze

Startup finished in 6.904s (firmware) + 1.248s (loader) + 1.509s (kernel) + 2.754s (initrd) + 13.436s (userspace) = 25.854s
graphical.target reached after 13.436s in userspace.

systemd-analyze critical-chain

graphical.target @13.436s
└─multi-user.target @13.436s
  └─getty.target @13.436s
    └─getty@tty1.service @13.436s
      └─systemd-user-sessions.service @13.420s +14ms
        └─network.target @13.419s
          └─NetworkManager.service @13.073s +345ms
            └─network-pre.target @13.073s
              └─firewalld.service @12.806s +265ms
                └─polkit.service @12.851s +248ms
                  └─basic.target @12.805s
                    └─systemd-pcrphase-sysinit.service @12.775s +30ms
                      └─sysinit.target @12.771s
                        └─systemd-update-utmp.service @12.749s +21ms
                          └─systemd-tmpfiles-setup.service @12.656s +91ms
                            └─local-fs.target @12.647s
                              └─boot.mount @1.179s +11.467s
                                └─systemd-fsck@dev-disk-by\x2duuid-890D\x2dA1A5.service @363ms +35ms
                                  └─dev-disk-by\x2duuid-890D\x2dA1A5.device

systemd-analyze blame

11.467s boot.mount
 2.973s dev-ttyS3.device
 2.973s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
 2.972s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
 2.972s dev-ttyS2.device
 2.972s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
 2.972s dev-ttyS0.device
 2.969s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
 2.969s dev-ttyS1.device
 2.963s sys-devices-platform-STM0125:00-tpmrm-tpmrm0.device
 2.963s dev-tpmrm0.device
 2.954s sys-module-fuse.device
 2.953s sys-module-configfs.device
 2.931s dev-disk-by\x2dpartuuid-f03a4990\x2d4e38\x2d4c6e\x2da888\x2d0ba156e41f3b.device
 2.931s sys-devices-pci0000:00-0000:00:06.0-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
 2.931s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_512GB_______S6H3NX2T530900_1\x2dpart1.device
 2.931s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
 2.931s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-f03a4990\x2d4e38\x2d4c6e\x2da888\x2d0ba156e41f3b.device
 2.931s dev-nvme0n1p1.device
 2.931s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_512GB_______S6H3NX2T530900\x2dpart1.device
 2.931s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-890D\x2dA1A5.device
 2.931s dev-disk-by\x2did-nvme\x2deui.36483332545309000025385800000001\x2dpart1.device
 2.931s dev-disk-by\x2ddiskseq-1\x2dpart1.device
 2.931s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
[...]

This happens even when removing it from /etc/fstab.

I currently have a boot partition and a an encrypted btrfs partition containing @ and @home subvolumes

lsblk -f

nvme0n1
├─nvme0n1p1 vfat        FAT32       890D-A1A5                             492.9M    10% /boot
└─nvme0n1p2 crypto_LUKS 2           65122208-30dd-4061-b3d3-be44937ebbf4
  └─luks    btrfs                   b79991df-414d-46ee-92d2-4ced5190283f  446.9G     6% /home
                                                                                        /

Let me know if there's anything else I could add.

Last edited by alba4k (Yesterday 17:20:49)

cryptearth · Yesterday 17:40:11

as you clearly not followed it - start over here: https://wiki.archlinux.org/title/Installation_guide
we can't support whatevery really bad instructions you followed (likely some random guide, a yt video, or worst: some ai)

a few points:
- why remove /boot from fstab? - your very next topic will be "system not booting after kernell update" - caused by: /boot not mounted during update
- syslx64.efi? unless you really try to use syslinux that's a rather strange name
- btrfs in a luks container is only useful for snapshots and has a high impact on scrubbing

Last edited by cryptearth (Yesterday 17:44:50)

alba4k · Yesterday 18:05:46

as you clearly not followed it

I did, what would make you think I didn't?

why remove /boot from fstab?

I did not. I did that temporarily to check whether that would fix the issue. It didn't. I know it needs to be there

syslx64.efi?

Where did you even read that. Regardless, I'm booting from a UKI

btrfs in a luks container is only useful for snapshots and has a high impact on scrubbing

unrelated

-thc · Today 05:44:54

Have you taken a look at the journal? If you want us to ta look too:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

alba4k · Today 11:58:38

Here you go: https://0x0.st/8O7S.txt

Couldn't find anything directly related to boot.mount, though

qu@rk · Today 12:32:14

At 13:07:14 mounting /boot starts, then there's

systemd[1]: Listening on Disk Image Download Service Socket.

and it takes about 11 seconds until

systemd[1]: Mounted /boot.

Maybe some VM stuff?

-thc · Today 12:53:25

Well - this looks a bit odd.

One thing to note is that the dirty bit of your boot partition is set and fsck removes it. That sounds like a mishap on shutdown or reboot. That doesn't take very long - it's just odd.

The 11 second time jump in the log looks like it's cause is the boot partition mount but it's probably a coincidence.

Can you provide another log with disabled mount of the boot partition?

Arch Linux

#1 Yesterday 17:17:36

boot.mount slowing down boot process

#2 Yesterday 17:40:11

Re: boot.mount slowing down boot process

#3 Yesterday 18:05:46

Re: boot.mount slowing down boot process

#4 Today 05:44:54

Re: boot.mount slowing down boot process

#5 Today 11:58:38

Re: boot.mount slowing down boot process

#6 Today 12:32:14

Re: boot.mount slowing down boot process

#7 Today 12:53:25

Re: boot.mount slowing down boot process

Board footer