You are not logged in.
Hello,
I saw there are many posts talking about this kind of problem, but I didn't manage to find something working for me, so I come here to ask for help
The problem:
Sometimes, (once every 7 boots or so), my server fails to boot and is stuck in recovery mode ("input password or press ctrl+D"). It's on Archlinux, with an asrock N100DC-ITX motherboard). The BTRFS raid 1 is composed of 2 SSDs (Samsung 870)
Jun 08 14:43:37 Lyvi systemd[1]: dev-disk-by\x2duuid-e93aa4d0\x2d76ad\x2d41ab\x2d9795\x2d7e93b847d8dc.device: Job dev-disk-by\x2duuid-e93aa4d0\x2d76ad\x2d41ab\x2d9795\x2d7e93b847d8dc.device/start timed out.
Jun 08 14:43:37 Lyvi systemd[1]: Timed out waiting for device /dev/disk/by-uuid/e93aa4d0-76ad-41ab-9795-7e93b847d8dc.
Jun 08 14:43:37 Lyvi systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/e93aa4d0-76ad-41ab-9795-7e93b847d8dc.
Jun 08 14:43:37 Lyvi systemd[1]: Dependency failed for /light.
Jun 08 14:43:37 Lyvi systemd[1]: Dependency failed for Local File Systems.Following some recommendations, I set a longer timeout in fstab to give more time to the raid to mount :
UUID=e93aa4d0-76ad-41ab-9795-7e93b847d8dc /light btrfs rw,relatime,x-systemd.mount-timeout=15min 0 2But unfortunately, it doesn't work, the timeout still happen after 90seconds.
Last edited by ealrann (2024-06-08 15:17:24)
Offline
90 seconds timeout is systemd timeout; you can change it in /etc/systemd/system.conf, but it shouldn't need so long timeout. Something is wrong.
Post full output of command: 'sudo journalctl -b-1' from failed boot.
Offline
Thanks for your help
Here's the full log: https://pastebin.com/aAQxqiLd
The mount started at 14:42:xx and failed at 14:43:37 . Then I took control of the pc at 15:49 to test if I can mount it manually (it worked).
Last edited by ealrann (2024-06-09 20:56:00)
Offline
You can change systemd timeout from 90 seconds to, for example, 30 seconds in file I mentioned earlier (3 places in that file), so if service is failing, than fail faster.
I don't see clear reason of problem in your log, but maybe this:
Jun 08 14:42:09 Lyvi kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
Jun 08 14:42:09 Lyvi kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Jun 08 14:42:11 Lyvi kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])Offline