So, last Night I accidentaly switched of my PC during shutdown. Was a bad mistake, a stupid one.
It boots now in a frozen Plasma DEsktop. I can switch over to another terminal session and checked the last errormessages via sudo journalctl -b -1 -e and fount this:
Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")
What else can I do now to get my system up and running again?
Well, situation changed a bit: Switched back to my frozen gui, now I see bootscrren again, with last entry “reached graphical user interface” and stopped there… strange!
I could boot into another snapshot, but I try to fix it with your help, almighty forum!
Okay, now I don’t get it anymore. I was working (on my windows corporate thingy) and switched back to my private endevouros workstation and was greeted by a working, responsive, totally fine Plasma…
Okay, it was marked as solution too early. I must have gotten a hit on my filesystem.
My nfs mounts are not working anymore, here is a copy of the fstab entry (just one, lines are similar for different mounts) :
truenas:/mnt/Datapool_on_TrueNAS/Movies /Movies_on_TrueNAS nfs x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=1min 0 0
Dolphin freezes, when I try to open certain paths (nfs mounts, but also true for additional drives mounted), and mounting per cli does not work either:
sudo mount -t nfs truenas:/mnt/Datapool_on_TrueNAS/Movies /Movies_on_TrueNAS/
Waiting for a response (after giving it my superuser password) since some time…
got an response:
mount.nfs: No such device for (null) on /Movies_on_TrueNAS/
strange…
Edit: Can I somehow “unsolution” a solution?
More information:
Dolphin is bringing this error:
dolphin
kf.coreaddons: "Could not load plugin from /usr/lib/qt6/plugins/kf6/thumbcreator/appimagethumbnail.so: Cannot load library /usr/lib/qt6/plugins/kf6/thumbcreator/appimagethumbnail.so: libappimage.so.1.0: cannot open shared object file: No such file or directory"
I wonder if it caused corruption on your nfs shares. It may be worth running fsck on your server to check.
Highly unlikely. The NFS shares are ZFS-Raids.
I agree that it’s unlikely then. What does journalctl show for nfs?
It has shown multiple errors.
I took another approach: Commented out the NFS shares, rebootet → works fine.
Went to daughters PC, got same error → woha.
Was pissed about that and took the brutal approach: Cancelled one running scrub job and one running zfs send job on my truenas and rebootet it.
Vopila, everythings fine. This is VERY strange…
Time to get rid of truenas, it is more and more annoying… zfs chezmoi looks promising.