You are not logged in.
Hello friends.
During the last months there is an issue that drives me crazy. If I try to sync the filesystem, or to halt/sleep my computer (which I suspect again it is a sync issue), the system is unable to sync at all. This happened randomly after an update, with no change to the hardware at all. I noticed it that it took forever to shutdown (but did shutdown eventually after many timeouts). It got more serious when I wanted to "sync" to be sure a USB stick I was using was properly written.
I tried to unmount all external filesystems, but this didn't help. It wasn't one of them.
Here is the full journalctl output.
Also I took a screenshot of the shutdown procedure, where it clearly says that it is unable to sync.
I have tried all the tricks I know how to approach this, with no luck.
Any ideas?
Last edited by teras (2024-09-03 16:25:44)
Offline
Please post the full journal output for a boot with the issue. As the journal output you posted does not contain the start of the boot it misses information such as kernel version, loaded kernel modules, types of file-system in use, kernel OOPS.
Offline
Offline
Please replace the oversized images in your OP w/ links.
Sep 02 23:27:03 aura kernel: Missing ENDBR: kallsyms_lookup_name+0x4/0xd0
That's the OOT binder-linux module
You also have NM and networkd enabled, disable the latter.
Then there's
Sep 02 23:27:02 aura systemd[1]: Mounting /Volumes/Windows...
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Finally try to disable APST, https://wiki.archlinux.org/title/Solid_ … leshooting
Next to the nvme there're tow ATA drives, but they "seem" to unmount cleanly.
Offline
Now it's this spooky moment that a problem disappears by itself.
First of all, it was not the Windows partition thing, since this is what I do on any new installation. Having said that, I did log in to Windows, performed some housekeeping there, installed latest updates there and (had to) reboot a couple of times.
The only other thing I did was to minimize the time watchdog waits for timeout, from 90" to 10".
Now, I am again able to "sync" (hooray!) and properly halt and shutdown. Of course I'll try in the long run to fix the issues that @seth pointed out and thank you so much.
I'll mark this topic as solved.
Offline
The only other thing I did was to minimize the time watchdog waits for timeout, from 90" to 10".
That would shorten the dealy - have you previously waited for 90s to see whether the system halts eventually?
What if you set the timeout to 60s? 25s?
Offline
No, I don't think it has to do with timeout. Now I am able to sync, suspend and shutdown almost instantly.
Before, sync was impossible, suspend didn't really work (only the monitors were turned off) and shut down did shut down eventually, after a long period of timeout.
The system did halt, but it took forever.
Now that I am thinking, I don't even believe fiddling with windows was the solution, since I tried to comment out all mount points except root partition, and rebooted and even this didn't work.
I am still curious what fixed the problem -- maybe in the meantime arch updated something and fixed it? I don't know.
Offline