Seems like lately after a reboot my system will throw an error message when trying to mount the 6TB storage drive that’s formatted NTFS…
I use the Gnome disk utility to “repair” the drive, and all well…until next reboot.
Any clue as to what’s causing this?
Are you dual-booting? If so be sure to disable “fast startup” in Windows
No, it’s a Seagate IronWolf 6TB NAS Hard Drive 7200 RPM.
Dual booting with Debian, all the Windows garbage(TPM, Secure Boot,Fast Boot) is disabled in the BIOS.
I can’t remember for sure, but I think the only time I saw this error was with my newest SSD, and it eventually led to some corrupted files.
I don’t know much about NAS devices, though, so the above may be irrelevant.
On another note: I noticed that it says “/run/media…”. Is it permanently mounted (physically, I mean)?
Yes, It is an internal storage drive. I typically put the OS on an SSD drive, with an HDD for data.
What about software? Is it also permanently mounted via software? It probably should be, since it’s internal.
Usually, drives permanently mounted via software are at
/mnt/driveLabel rather than
@dalto Would doing this make a difference in your opinion?
I would argue that it would be a good idea and is a best practice.
However, I don’t think letting it be automounted should cause filesystem corruption. Seems more like it isn’t being unmounted properly.
If it was me, I would probably not use ntfs on a linux-only setup.
No, not that.
I meant if the error message may disappear if he automounts it.
I would suspect that you may need to use something like Hirens boot CD to do a disk check for the ntfs. Linux has a hard time with this file type when left in a dirty state. (unclean mount) I’ve seen other suggest using a native ntfs file check system does reset the unclean state better. I cannot confirm since I haven’t used ntfs since like 2010.
As I said, I can’t remember for sure, but yeah, I remember having some issues when I used to automount an NTFS partition when dual-booting and I remember that running a native W1nd0z3 disk check would fix it.
“chkdsk”, I think?
Don’t remember if it was this particular error, but Linux would sometimes have trouble with both the storage NTFS partition and the actual M$ system partition.
I should take the time to switch over to Ext4, I only have 1.2TB on this 6TB drive, so I could shrink the drive, create an Ext4 partition, then copy my data to it. Then resize back up, although some space might end up wasted.
I agree it will be good to change the filesystem if you don’t need to access the drive with Windows.
In the meanwhile, you could try
ntfsfix to see if it restores the ability to mount the drive.
sudo ntfsfix -d /dev/sdb1
I am going to go ahead and change from NTFS to EXT4, but it’s interesting that the mount problem has not occurred on the last couple reboots. As a matter of fact, the drive just goes ahead and mounts without asking for user password. ?
Rather that resize partitions & format and copy files etc I went ahead and just formatted the 6TB disc after backing up the data to a 5TB disc that I forgot I had. Life is simple again.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.