You are not logged in.
I was copying some large files between two NTFS formatted drives which I left running overnight. In the morning the computer did not want to wake and activate the monitors, so I had to do a hard reset. When I rebooted the system and attempted to mount drive sdc1 (the drive that was receiving the copied files) in Gnome Files/Nautilus it gave me a pop-up window with this error:
Unable to access location
Error mounting /dev/sdc1 at /run/media/p101user/2023 Media1: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error
However, if I go to the terminal and enter these commands, then the drive will mount:
sudo mkdir /run/media/p101user/"2023 Media"
sudo mount /dev/sdc1 /run/media/p101user/"2023 Media"
When I mount it through the terminal then I can access it in Gnome Files/Nautilus without issue. But, if I unmount the driver, either with the 'umount' command in the terminal, graphically through Files/Nautilus, or reboot the computer then the error appears again in Files/Nautilus.
I ran sudo dmesg and found this:
[ 37.645279] ntfs3: sdc1: It is recommened to use chkdsk.
[ 37.700089] ntfs3: sdc1: volume is dirty and "force" flag is not set!
As far as I can tell chkdsk is a windows function. I did boot into windows and it did run some kind of disk repair on startup. However that did not fix my mounting problem in Arch.
I also found fsck on the Arch wiki.
Running:
sudo fsck /dev/sdc1
...only produces this result:
fsck from util-linux 2.39.2
...and the Arch wiki seems to indicate that running
sudo fsck -a
to attempt to automatically repair a disk is only for drives formatted as ext2/ext3/ext4 or FAT, not NTFS.
Is there any way to fix this so that I can mount the drive through Gnome Files/Nautilus?
Last edited by P101 (2023-09-22 16:57:19)
Offline
While access to NTFS is now mature in Linux, some extra features and dealing with damage are not implemented. It’s more to give the ability to access your Windows data from Linux than use as a standalone filesystem under Linux.
If only possible, put these drives in a machine with Windows and run the native chkdsk. This is the best possible option.
An alternative is using ntfsfix. However, read the warning in the manual. This is a way to force your way in, not repair damage. So if there is any corruption, ntfsfix will make it mountable, but the damage will remain and may propagate.
Sometimes I seem a bit harsh — don’t get offended too easily!
Offline
Same thing here (but on kde dolphin), issue started 3 days ago after an arch update.
Offline
Offline