You are not logged in.
I just istalled updates (pacman -Syu) on my vanilla arch running on a Schenker Slim 14 and now I can't get it to boot
I use 2 volume groups on 2 different SSDs.
everything system related (rootfs, swap) is within VG 'system' on a 500GB 970 Evo Plus (m.2 NVME) - everything seems fine here
everything within the homedir is in VG 'data' on a 2TB MX500 (2.5" SATA) - it appears it fails to activate. There are multiple timeouts and dependency fails for each LV on this drive
my troble now is that the system does't drop into an emergency shell but keeps trying to mount these LV. I killed the system just now after watching this for roughly 30 minutes
It happend once a couple of weeks ago but there were start jobs running and after they timed out I could activate the LV via lvchange -ay data and got out of the emergency shell with systemctl default.
While I'm typing this I'm creating a live usb drive for troubleshooting. First I'll check the SSD but I doubt there is anything there. Everything was working fine before the reboot.
Any hint is highly appreciated
Offline
As I already expected yesterday the drive and LVs didn't show any sign of trouble.
I was able to boot the system after disabling all mountpoints on VG data in /etc/fstab and did a complete backup of everything relevant. I had no trouble activating and mounting the LVs post boot.
It might be related to https://bbs.archlinux.org/viewtopic.php?id=248788
However I messed with a lot of stuff today and decided for a clean install as a lot of stuff kept going havoc.
If the problem is remaining after a clean install I'll post logs. There was no point in doing so before. There were too many applications causing log entries due to missing config files. The journal was roughly 350Mib
Offline