For a few weeks I’ve been unable to mount an internal NTFS Hard drive.
Throughout this post, all installations of manjaro use manjaro-kde-22.1.3-230529-linux61.iso as my starting point.
After a fresh Manjaro install today, the NTFS disk was mountable and I could use it. After getting the OS up to date and rebooting, the drive is no longer mountable. This is actually a reproduction of the error after installing manjaro a second time to a different drive. The NTFS HDD is still mountable in LiveCD, windows 10, and fresh installs. Only after updates does it seem to fail. Chkdsk sees no fault, NTFSFix says only chkdsk can fix it.
I have three ideas for the source:
- It’s a flaw in one of the updates, which is why I am writing here. I don’t write operating systems and couldn’t begin to imagine what part of these updates is causing it to suddenly fail.
- Some other issue during reboot.
- My network admin is firewalling certain parts of my online updates, causing the little bit of code for NTFS to work on my computer to not get to my computer, leaving it nonfunctional. This network suffers from severe packet loss (20% to 80%) during any sustained download and likes to take 1-5 second breaks every few minutes. Let me know if checksums exist for something like that.
This error occured previously after my NVME had been replaced by RMA. I made a fresh Manjaro install to the NVME and the NTFS HDD mounted fine at first. One day I returned, and it mounted no more, presenting the error in the title. I took off my manjaro NVME and booted into Win10. The drive mounted fine in Win10, and
Chkdsk said nothing was wrong. I thought the odds of a second failed NVME drive were incredibly unlikely. I tried a Manjaro LiveCD, and the NTFS HDD mounted fine, which made me suspicious of my NVME once again that hosted my Manjaro install. One day I began some updates, and during the update download, the drive suddenly began to mount again. That was until I rebooted after finishing the updates, and it stopped mounting. I try mounting the drive every day to see if there is really some intermittent cause, and every day it fails. Maybe western digital really sent another bad NVME that was corrupting my Manjaro, it’s been known to happen.
To rule that out, I reinstalled Manjaro to a traditional SSD that I’ve used for years, earlier today, bringing me to the first paragraph, and the issue reproduced after updating and rebooting.
If there is any log or command line suggestions to get information regarding the hardware, please let me know. I made the switch from Win7 to linux only a few months ago and am still unfamiliar with many parts of it and what knowledge readers may want.
Some troubleshooting I took from a guide in a similarly titled support thread in this forum, a guide I can’t link according to forum rules apparently. It’s on itslinuxfoss.
- After writing
mountinto the cmd to “identify the problem filesystem”, the device does not display. It’s not mounted after all.
blkid /dev/sdb2produces nothing, zero lines. The device number is found in the full error by Dolphin:
An error occurred while accessing 'Thrasher', the system responded: The requested operation has failed: Error mounting /dev/sdb2 at /run/media/rainy/Thrasher: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error. KDE Partition Manager also displays that partition address.
nano /etc/fstabproduced only 3 lines, of which I have 4 mounted devices, not including what should be the 5th?: the NTFS drive. Nothing references it here. I had to reopen the console because I don’t know how to exit nano, and the hotkeys written below don’t tell me.
fsck /dev/sdb2said I didn’t have permission to open the location.
sudo fsck /dev/sdb2actually did nothing, returning only one line containing
fsck from util-linux 2.39.3.
And yet, dolphin sees the device. KDE Partition Manager sees the drive, and sees the ntfs-type partition named /dev/sdb2. It’s real, it’s there, it wont mount.
Thanks for reading, I apologize for the wall. I may not find time to read the thread again until after work tomorrow (18h), but I greatly appreciate any suggestions or acknowlegdement. If there’s no hope for a solution, I’d like to know too. I may try some other linux distributions to see if they fare better, however the NTFS compatibility I hear is a very core component close to linux’s kernel, which would probably be the same on other distros.