On Sun 30 Mar 2025 at 17:35:18 (+0300), J wrote:
> Every time i restart the PC i have an error message while rebooting
> process: "[FAILED] failed unmounting *disk-mount-point*..."
>
> It didn't bother me really, because this message usually just immediately
> disappeared. But last time the *compu
>
> I would investigate why my ext4 disks were not being unmounted cleanly
> on shutdown if it were happening here. I suppose my suspicions would
> first fall on any network connections.
Yes, i want to investigate it too, but i don't know where to start. SMART
of the disks is OK, btw.
I have exp
Thank you for your help!
systemctl help local-fs.target
> systemctl cat local-fs.target
>
> I hope, it gives an answer to my question. For more details see
> loginctl(1). Actually I was shooting in dark.
>
I didn't understand much from this, frankly speaking. But...
In your logs I se
On 02/04/2025 21:31, J wrote:
I expect that this mount is a part of local-fs.target, so qbittorrent
and other processes started from user session should be stopped
already.
Unfortunately i don't know what the local-fs.target is. Quick search
shows that it is probably a part of syst
> If an application is terminated by SIGKILL
>
There is *SIGTERM*
* deb systemd-shutdown[1]: Sending SIGTERM to remaining processes...*
And it happens after
*Stopped target local-fs.target - Local File Systems.*
OK. Thanks!
when it is writing data then you can
> easily get corrupted files.
>
These apps don't write data. They only read, does it matter?
On 03/04/2025 22:05, J wrote:
And i want to ask again: can these problems lead to information loss?
It depends on details you (likely) may find in logs.
If an application is terminated by SIGKILL (from your description I
suspect that it happens sometimes) when it is writing data then you can
Chronologically it is
Apr 01 14:19:20 deb systemd-logind[741]: System is rebooting.
Apr 01 14:19:20 deb systemd-logind[741]: The system will reboot now!
Apr 01 14:19:20 deb umount[3537]: umount:
/mnt/8cd66b97-bde6-4475-b875-8f3928a8b14d: target is busy.
Apr 01 14:19:20 deb systemd[1]: Unmounting
> I expect that this mount is a part of local-fs.target, so qbittorrent
> and other processes started from user session should be stopped already.
>
Unfortunately i don't know what the local-fs.target is. Quick search shows
that it is probably a part of systemd, which (local-fs.target) is, i guess
On 01/04/2025 18:31, J wrote:
Apr 01 14:19:20 deb systemd[1]: Failed unmounting
mnt-8cd66b97\x2dbde6\x2d4475\x2db875\x2d8f3928a8b14d.mount - /
mnt/8cd66b97-bde6-4475-b875-8f3928a8b14d.
Apr 01 14:19:20 deb systemd[1]:
mnt-8cd66b97\x2dbde6\x2d4475\x2db875\x2d8f3928a8b14d.mount:
>
> Apr 01 14:19:20 deb systemd[1]: Failed unmounting
> mnt-8cd66b97\x2dbde6\x2d4475\x2db875\x2d8f3928a8b14d.mount -
> /mnt/8cd66b97-bde6-4475-b875-8f3928a8b14d.
> Apr 01 14:19:20 deb systemd[1]:
> mnt-8cd66b97\x2dbde6\x2d4475\x2db875\x2d8f3928a8b14d.mount: Mount process
> exited, code=exited, stat
On 31/03/2025 20:38, J wrote:
Do timestamps in the output match the moment when you experienced the
issue? I would expect "-b -1" rather than "-b1", however the latter
still may be valid.
I see no errors in logs.
Do you execute journalctl as root? 90 seconds timeouts and following
>
> Do timestamps in the output match the moment when you experienced the
> issue? I would expect "-b -1" rather than "-b1", however the latter
> still may be valid.
>
I see no errors in logs.
qBitTorrent may be the culprit, i see this mention of QB, but i don't know
if it is connected
Mar 31 16
On 30/03/2025 21:52, J wrote:
Also, is there a way to see these messages on black screen during reboot
in the system logs somehow?
i can't find it in
journalctl -b1 -r
Do timestamps in the output match the moment when you experienced the
issue? I would expect "-b -1" rather than "-b1", howe
Also, is there a way to see these messages on black screen during reboot in
the system logs somehow?
i can't find it in
*journalctl -b1 -r*
вс, 30 мар. 2025 г. в 17:35, J :
> Hello!
>
> Every time i restart the PC i have an error message while rebooting
> process: "[FAILED] failed unmounting *
Hello!
Every time i restart the PC i have an error message while rebooting
process: "[FAILED] failed unmounting *disk-mount-point*..."
It didn't bother me really, because this message usually just immediately
disappeared. But last time the *computer could get stuck* on this for a
minute or two.
16 matches
Mail list logo
