It looks like my NTFS disk is failing. Not surprised as it’s an old Samsung EVO 840 drive.
When I logged into my PC this morning, I noticed a wall of text (where two lines are still repeating) regarding ntfs-3g
:
Wanting the journal spam to stop, I thought I’d first try umount
the drive, but it was “busy”…
$ sudo umount /data/evo840/
umount: /data/evo840/: target is busy.
Read the umount
man page and thought I’d try the “lazy” option… $ sudo umount -l /data/evo840/
it unmounted the drive (confirmed in Dolphin), but the journal entries persist.
Looked a bit in ntfs-3g
and found there was a ntfsfix
command related to it (needed to remount the drive), and it basically tells be the “Volume is corrupt”…
$ ntfsfix -n /data/evo840/
Mounting volume... Error reading bootsector: Is a directory
FAILED
Attempting to correct errors... Error reading bootsector: Is a directory
FAILED
Failed to startup volume: Is a directory
Error reading bootsector: Is a directory
Volume is corrupt. You should run chkdsk.
No change made
… and the output is the same (sans the last line) if I remove the “-n” option.
So how to I safely stop the ntfs-3g
from doing what it’s doing and stop the journal spam?
- I thought of using gnome-disk to dump the partition table (I won’t miss the drive contents as I have a VDI file I use for Virtualbox), but I suspect the fact “it’s busy” would throw a wrench in that
- I thought of rebooting, but I suspect the fact “it’s busy” would interfere with the reboot cycle/process
- I’ve thought that maybe REISUB might have a good chance of exiting cleanly.
In preparation I’ve edited /etc/fstab
so that the drive no longer mounts at boot.