Arch Linux

naemd

Member

Registered: 2022-04-12

Posts: 1

Didnt boot correctly after update

Hi,

I had a weird issue after rebooting my server after updating to 5.17.1-
It wouldnt boot correctly and I couldnt SSH in. After rebooting another time it seemed to be working and I noticed no difference.
I have collected the logs however and theres something I noticed.
https://pastebin.com/bBJhes4v

In particular:

Apr 12 21:42:32 ArchboX systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Apr 12 21:42:32 ArchboX systemd[1]: dev-md-0.device: Job dev-md-0.device/start timed out.
Apr 12 21:42:32 ArchboX systemd[1]: Timed out waiting for device /dev/md/0.
Apr 12 21:42:32 ArchboX systemd[1]: Dependency failed for /dev/md/0.
Apr 12 21:42:32 ArchboX systemd[1]: Dependency failed for Swaps.
Apr 12 21:42:32 ArchboX systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
Apr 12 21:42:32 ArchboX systemd[1]: dev-md-0.swap: Job dev-md-0.swap/start failed with result 'dependency'.
Apr 12 21:42:32 ArchboX systemd[1]: dev-md-0.device: Job dev-md-0.device/start failed with result 'timeout'.
Apr 12 21:42:32 ArchboX systemd[1]: dev-md-1.device: Job dev-md-1.device/start timed out.
Apr 12 21:42:32 ArchboX systemd[1]: Timed out waiting for device /dev/md/1.
Apr 12 21:42:32 ArchboX systemd[1]: Dependency failed for /boot.
Apr 12 21:42:32 ArchboX systemd[1]: Dependency failed for Local File Systems.
Apr 12 21:42:32 ArchboX systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Apr 12 21:42:32 ArchboX systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Apr 12 21:42:32 ArchboX systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'.
Apr 12 21:42:32 ArchboX systemd[1]: dev-md-1.device: Job dev-md-1.device/start failed with result 'timeout'.
Apr 12 21:42:32 ArchboX systemd[1]: systemd-ask-password-console.path: Deactivated successfully.
Apr 12 21:42:32 ArchboX systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Apr 12 21:42:32 ArchboX systemd[1]: systemd-ask-password-wall.path: Deactivated successfully.
Apr 12 21:42:32 ArchboX systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.

KVM Console:

And booting for a second time (which worked):

Is there any reason for concern? Or could it be it was just a one time occurence, a hiccup?

loqs

Member

Registered: 2014-03-06

Posts: 18,970

Re: Didnt boot correctly after update

Apr 12 21:42:32 ArchboX kernel: md0: detected capacity change from 0 to 67035136
Apr 12 21:42:32 ArchboX kernel: md2: detected capacity change from 0 to 124922073088
Apr 12 21:42:32 ArchboX kernel: md/raid1:md1: active with 4 out of 4 mirrors
Apr 12 21:42:32 ArchboX kernel: md1: detected capacity change from 0 to 4188160
Apr 12 21:42:32 ArchboX kernel: EXT4-fs (md2): mounted filesystem with ordered data mode. Quota mode: none.

At least one member of md0 was missing so the device was timed out.