4

I'm on Jammy.

I have a new external 6TB disk that I need to share between Windows and Ubuntu for games, but for some reason, it's seemingly impossible to mount, using fstab at least. When allowed to mount automatically, it seems to work, but it's not in the location I want it. When trying to mount using fstab, however, it seems to have some kind of problem with the filesystem.

If filesystem is set to auto, cat /proc/mounts says the filesystem type is fuseblk, which is the same as my other NTFS disks have always shown, but in this case, trying to access it says 'This location is not a folder.' Setting the filesystem to ntfs-3g results in the same. Setting it to ntfs3 mounts it, but of course I don't have access permission to anything on the drive.

When removed from fstab and allowed to mount using defaults, the filesystem is displayed as ntfs3, but for some reason, I have full access to the disk.

EDIT: More information I was asked for:

This is a desktop.

This is the base fstab entry. Everything is totally off the shelf basic, save for the options I added to no change or type entry I changed as detailed above.

/dev/disk/by-id/usb-Seagate_Expansion_HDD_00000000NT17G2ZN-0:0-part2 /mnt/Expansion auto nosuid,nodev,nofail,x-gvfs-show 0 0

In syslogs, I just found these messages:

  • It is recommened to use chkdsk.
    • I've done that with the /r flag from within my Window environment. Took over seven hours and returned no problems. Crystal Disk Info shows no problems as well. GSmartControl doesn't read S.M.A.R.T. info from the majority of the disks I've had (which I know support it), so that's no help.
  • volume is dirty and "force" flag is not set!
    • I ran ntfsfix on the volume to no change. I also have made sure to turn off fast startup in Windows specifically to prevent this. Like I said, I have no such issues with my other disks, including my Windows system partition.

So... none of that seems to make sense. I also tried the force option to no change, save for both of those messages no longer appearing in logs.

0 Answers0