You are not logged in.
Hello, recently with one of the new home server I'm having some issue at boot. This only happens time to time after a reboot.
May 19 21:11:00 gorille kernel: kauditd_printk_skb: 12 callbacks suppressed
May 19 21:11:00 gorille kernel: audit: type=1130 audit(1621451460.847:23): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd-wait-online comm="systemd" exe="/usr/lib/systemd/systemd>
May 19 21:12:25 gorille systemd[1]: dev-disk-by\x2duuid-adc512e2\x2da22c\x2d4157\x2d9e70\x2dde3aec936ab2.device: Job dev-disk-by\x2duuid-adc512e2\x2da22c\x2d4157\x2d9e70\x2dde3aec936ab2.device/start ti>
May 19 21:12:25 gorille systemd[1]: Timed out waiting for device /dev/disk/by-uuid/adc512e2-a22c-4157-9e70-de3aec936ab2.
May 19 21:12:25 gorille systemd[1]: Dependency failed for /mnt/storage.
May 19 21:12:25 gorille systemd[1]: Dependency failed for Local File Systems.
May 19 21:12:25 gorille systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
May 19 21:12:25 gorille systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
May 19 21:12:25 gorille systemd[1]: mnt-storage.mount: Job mnt-storage.mount/start failed with result 'dependency'.
May 19 21:12:25 gorille systemd[1]: dev-disk-by\x2duuid-adc512e2\x2da22c\x2d4157\x2d9e70\x2dde3aec936ab2.device: Job dev-disk-by\x2duuid-adc512e2\x2da22c\x2d4157\x2d9e70\x2dde3aec936ab2.device/start fa>
May 19 21:12:25 gorille systemd[1]: systemd-ask-password-console.path: Deactivated successfully.
May 19 21:12:25 gorille systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
May 19 21:12:25 gorille systemd[1]: systemd-ask-password-wall.path: Deactivated successfully.
May 19 21:12:25 gorille systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
May 19 21:12:25 gorille systemd[1]: Reached target Timers.
May 19 21:12:25 gorille systemd[1]: Reached target Login Prompts.
May 19 21:12:25 gorille systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
May 19 21:12:25 gorille systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
May 19 21:12:25 gorille systemd[1]: Reached target Sockets.
May 19 21:12:25 gorille systemd[1]: Started Emergency Shell.It looks like the system experience a timeout while trying to mount /mnt/storage as defined in /etc/fstab:
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda3
UUID=cbae49cc-f4a3-484a-ada4-93f155b41852 / ext4 rw,relatime 0 1
# /dev/sda1
UUID=690D-3EE3 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/md126p1
UUID=adc512e2-a22c-4157-9e70-de3aec936ab2 /mnt/storage ext4 rw,relatime 0 3
# /dev/sda2
UUID=260dc0f1-3f00-4230-b39d-2b35fc9d9079 none swap defaults 0 0I can't figure out where is this Timeout coming from ?
I don't want to comment the related line in /etc/fstab and mount it manually after start. Can anyone help ?
Thanks for your help
Last edited by kumasan (2021-05-20 14:25:26)
Offline
More previous context? as this seems to not be a normal partition but something setup as a mapper device/potentially encrypted I'd say chances are you run into early boot entropy issues (... though they should mostly be a thing of the past): https://wiki.archlinux.org/title/Random … ternatives
Other than that if the device is just slow and does eventually show up you could also just set up a systemd automount: https://wiki.archlinux.org/title/Fstab# … th_systemd
Also please use [ code ] instead of [ quote ] when posting outputs.
Last edited by V1del (2021-05-20 10:00:28)
Offline
More previous context? as this seems to not be a normal partition but something setup as a mapper device/potentially encrypted I'd say chances are you run into early boot entropy issues (... though they should mostly be a thing of the past): https://wiki.archlinux.org/title/Random … ternatives
I forgot to mention that the volume behind /mnt/storage is a fake raid (provided by the intel chipset of the motherboard). Nothing encrypted or lack of entropy related
Other than that if the device is just slow and does eventually show up you could also just set up a systemd automount: https://wiki.archlinux.org/title/Fstab# … th_systemd
I'll take a look at it thanks.
Also please use [ code ] instead of [ quote ] when posting outputs.
Corrected.
Offline
I forgot to mention that the volume behind /mnt/storage is a fake raid (provided by the intel chipset of the motherboard)
assuming you do use mdadm , have you added mdadm_udev to mkinitcpio hooks and mdmon to binaries ?
See https://wiki.archlinux.org/title/RAID#C … mkinitcpio for more details
Last edited by Lone_Wolf (2021-05-20 10:49:45)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
Thanks a lot for your help.
The issue seems to have been solved.
I've followed the fix by let systemd munt the device
# /dev/md126p1
UUID=adc512e2-a22c-4157-9e70-de3aec936ab2 /mnt/storage ext4 noauto,x-systemd.automount 0 3After several reboot, this works fine.
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Offline