(Bonus update) I’m back on KDE6 and it’s actually working! I ran Cinnamon for about a day before missing KDE and tried a fresh install of EndeavourOS. It worked fine, Wayland still doesn’t work but I’m only getting minor bugs with x11 compared to when I tried to update from 5.27
(Update) Well finally back on my desktop but sadly not on my original install, Thanks for all the help and advice! Sadly every path just sent me into another brick wall, I’m starting to think my drive itself is physically failing as I couldn’t mount it in chroot and even had trouble reformatting it…I’ll keep an eye on it and not save anything important to it.
I’ve decided I’m just not cut out for vanilla Arch just yet and gone back to Endeavour but this time with Cinnamon (for now) Thanks again!
After upgrading to KDE 6 and experiencing too many bugs for it to be useable for me I went back to a snapshot I made right before upgrading.
Now I’ve spent half my Friday tracking down different systemctl errors and trying to fix corrupted conf files from live USB environments, physically unplugged all but my nvme boot drive.
Rn I’m in a situation where I’m getting
[FAILED] Failed to mount /boot. See ‘systemctl status boot.mount’ for details [DEPEND] Dependency failed for Local File System.
Then it’s asking to give root password or press control-D, which I’ve dealt with before but this time my keyboard just doesn’t work
I tried to just sort it myself reading the Arch Wiki before begging for help on forums but I’m kinda at my wits end, This is a pretty new Arch installed and the first time using btfs on my main drive, I last updated maybe 4 days ago before today. I’ve also successfully restored from timeshift snapshots on this install before without issues.
Any help where to go from here would be great, thanks in advance.
I rolled back using timeshift, which I have used many times before without issue.
I’m not sure it that also rolls back the kernal but I seem to recall it typically does? I can be mistaken.
That fully depends on where your kernels are stored. If they’re in a separate partition, then no; it won’t roll back with the rest of your system.
Yeah /boot is probably separate to root
They were but both located on the same drive
That doesn’t matter. Snapshots only concern the state of any one filesystem; they do not address separate filesystems in any way.
Linux doesn’t really know about drives, it knows about partitions and mount points.
Obviously this is a simplification, but in general it’s close enough. It also could well be your problem - timeshift doesn’t know or care that /boot is on the same physical drive as the rest of your system: if it’s a different partition, it’s separate.