You are not logged in.
Hello everyone!
I am in need of assistance with my fairly new Arch install on my headless server.
I have started with Arch Linux as a learning process with my first home server only a few months ago, so I am still pretty new to Linux in general.
So now my problem:
I noticed that my Plex media server was behaving strangely, and rebooting had previously solves those kinds of problems, when restarting the service didn't help.
So I rebooted the server and was dismayed to notice it wasn't booting. It was stuck in an endless loop of
Starting udev Kernel Device Manager...
Oct 05 22:37:02 Homeserver systemd-udevd[315]: starting version 216
Oct 05 22:38:32 Homeserver systemd[1]: systemd-udevd.service start operation timed out. Terminating.
Oct 05 22:38:32 Homeserver systemd[1]: Failed to start udev Kernel Device Manager.
Oct 05 22:38:32 Homeserver systemd[1]: Unit systemd-udevd.service entered failed state.
Oct 05 22:38:32 Homeserver systemd[1]: systemd-udevd.service has no holdoff time, scheduling restart.
Oct 05 22:38:32 Homeserver systemd[1]: Stopping udev Kernel Device Manager...Before that, there was the following message:
Oct 05 22:03:56 Homeserver systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eno1.device.
Oct 05 22:03:56 Homeserver systemd[1]: Dependency failed for dhcpcd on eno1.I was able to remove that last message by booting with a live installation medium and adjusting the network interface name in the dhcpd configuration.
Now only the endless loop is left.
I must note, that I had just recently done a system update and hadn't noticed any significant errors or anything while updating.
I am at a loss for ideas on how to proceed. I have tried looking at the udev configuration, but so far I haven't found any useful hints about what might be wrong.
I have pasted the output of
journalctl -b -1to a pastebin. Here is the link:
journal
Thanks for any help!
Offline
Run following command in terminal ( Go from repair Arch Linux - during boot time )
sudo sudo mkinitcpio -p linux
After reboot, everything should be okay ( my experience )
Offline