Drive access error

[Ekinox]

Hello everyone,

First of all, I'm writing here because I didn't know where to open this topic. I'm sorry for that. My hard drive is divided into two parts, and I can't access the second one. When I click on it, I get this error. (The image is attached)

(I haven't used Linux Mint and its forum for a long time. Therefore, I'm sorry if I'm making mistakes that are against the rules or too simple.)

When I enter the code below, I can access the drive. However, I encounter this issue again every time I restart the computer, and I have to enter this code repeatedly. Is there a permanent solution to this problem? Thank you

Code: Select all

 sudo mkdir /media/SHADOWMAN
sudo mount -t ntfs-3g /dev/sda5 /media/SHADOWMAN

[u814e94bab14ee651f4]

Add the following line to your /etc/fstab file. Use the "sudoedit" command to edit that system file safely.

Code: Select all

 /dev/sda5    /media/SHADOWMAN  ntfs-3g   nodev,windows_names,nosuid,noatime,async,big_writes,uid=1000,gid=1000,fmask=0002,dmask=0002  0 0 

No spaces except where I've shown them to be. In the "options field" spaces are not allowed.

Using /dev/sda5 is a bit dangerous. If you add a label to the partition, use gparted to do that, then you can use the LABEL=SHADOWMAN in the fstab instead.

Code: Select all

LABEL=SHADOWMAN       /media/SHADOWMAN      ntfs-3g      nodev,windows_names,nosuid,noatime,async,big_writes,uid=1000,gid=1000,fmask=0002,dmask=0002   0     0 

all on 1 line. That's important.

I've made a bunch of assumptions but those should be true. Doing it this way, the NTFS file system will be mounted at boot, as long as MS-Windows doesn't leave the file system closed. This will mount the file system and make the first userid on the system the owner and allow read-write access.

If you need this storage to be read-write for other userids, that requires using a "group" that both userids share. That's pretty uncommon for home users.

[altair4]

Open a terminal and run:

Code: Select all

echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/disable-ntfs3.conf

Reboot

The file manager defaults to the ntfs3 driver which has issues.

By "blacklisting" the ntfs3 driver the file manager is forced to use ntfs-3g which does not have issues.

[Ekinox]

it works..Right now, I can access the drive

However, there was another error I encountered earlier. When I click on a file inside my drive, I get the following error and cannot access the file contents. What should I do?

[u814e94bab14ee651f4]

You should figure out if the file system is corrupted and try to fix it if it is. In general, file system corruption is best corrected from the OS with native file system support. That is MS-Windows for NTFS/exFAT/FAT32 or Linux for ext4/3/2, jfs, f2fs and 20 others.

So, if that file system is NTFS, boot into MS-Windows and use the chkdsk, scandsk, and other tools in that OS to try and fix it.
If the file system is ext4 or another native-Linux file system, use fsck to try and correct file systems errors. fsck doesn't work for ZFS or BTRFS, so if you have either of those, you'll need to use the tools they provide.

To see which file system each partition has, there are multiple methods. Getting lots of useful information, I find this command the most useful:
lsblk -e 7 -o name,type,fstype,size,FSAVAIL,FSUSE%,label,mountpoint

If corruption of the file system isn't the issue, it is time to worry about a failing HDD/SSD.
Use smartctl to run a short test, wait 5 minutes, then use smartclt to get a test report and look for non-zero error counts. SMART data needs to be allowed in the motherboard BIOS for this to work. There's no known downsides to enabling SMART that I know and it really makes no sense for motherboard firmware NOT to have it enabled by default, but they never do. Anyway, enable S.M.A.R.T. if it isn't already in your BIOS, then run the test, wait, then run the report.