You are not logged in.
I did a full system update a few days ago and after that I couldn't boot anymore. The problem seems to be systemd. I downgraded the following update:
[2018-07-14 15:15] [ALPM] upgraded systemd-sysvcompat (238.133-4 -> 239.0-2)
[2018-07-14 15:15] [ALPM] upgraded libsystemd (238.133-4 -> 239.0-2)
[2018-07-14 15:15] [ALPM] upgraded systemd (238.133-4 -> 239.0-2)
[2018-07-14 15:15] [ALPM] upgraded linux (4.17.2-1 -> 4.17.5-1)
[2018-07-14 15:15] [ALPM] upgraded linux-headers (4.17.2-1 -> 4.17.5-1)After the downgrade of the above packages everything worked fine again. I had to downgrade linux (and also downgraded linux-headers because I didn't know if keeping them on different versions is a problem) because systemd couldn't handle the newer linux version (I also downgraded libsystemd and systemd-sysvcompat just to be sure).
The problems I had were:
virtualbox-host no longer worked (there is a system hook that is normally started with systemd but it no longer worked)
network didn't work anymore (systemd couldn't establish a connection with dhcpcd)
NTFS filesystems couldn't be mounted anymore
After starting xserver the mouse and keyboard didn't work
Basically the entire system is unusable. I'm just skipping updating these packages for now. Just wanted to report it, maybe it is a unknown problem. If you need any further information please tell me.
Last edited by kiritsuku (2018-07-23 16:04:59)
Offline
Sounds like you didn't actually boot the new kernel. Do you have a /boot partition that wasn't mounted?
Offline
I do have a boot partition but it should be mounted because that is how it is configured in /etc/fstab. I didn't change any configuration. It looks like this:
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=a84aca82-6e3f-499a-b6fc-307dbc991760 /boot ext2 defaults 0 1 #sda1
UUID=aa4f31d9-a730-447b-b48b-53ae6e31b5df swap swap defaults 0 0 #sda2
UUID=262c5209-d942-4446-b66e-972ddefc8e70 / ext4 defaults 0 1 #sda3
UUID=60c81450-ab1a-4215-b351-f8f6e73538bd /home ext4 defaults 0 1 #sda4
UUID=8236FBF636FBE955 /media/win ntfs-3g rw,auto,uid=1000,gid=100 0 0 #sdb2Last edited by kiritsuku (2018-07-23 14:44:24)
Offline
And is the bootloader actually using the /boot partition?
To check if this is the issue, update, reboot, then check uname -r.
Last edited by Scimmia (2018-07-23 14:45:49)
Offline
Ok, that is interesting. I just updated the above packages and now everything works fine. I don't know what went wrong the first time I installed the packages.
Offline