Mint-Arch migration led to unmountable drive
Just installed CachyOS and the drive I used alongside system drive for media\archive storage can't get mounted anymore. It's internal HDD and uses NTFS, I created it on Windows 10 years ago and used all this time from under Mint (no dualboot, only Mint). I did a regular reboot before OS switch and didn't even mount it this time.
While trying to access said drive, dolphin prints that:
An error occurred while accessing 'drive', the system responded: The requested operation has failed: Error mounting /dev/sda1 at /run/media/user/drive: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error
Where can I start my fixing journey? Where I can look for precise reason it fails?
All components are 5-10 years old if it matters. The other HDD that I formatted under Mint works just fine. It's probably a CachyOS vs NTFS problem.
[new]
I succeed at force-mounting it via ntfs 3g, but it seems it really was a problem with a bad block or something originating from windows. Checks were passed with 0 errors, so I assume it's a little funni M$ gave me with a divorce letter.
Instead of finding a way to force-mount it every time, I tried checking it via WinPE, and it helped remove the cause of errors.
I'm yet to understand what is really behind that, filesystem differences and how OSs work with them, so if you have good articles, please share these.
What was your mount command? You might have to do something like
mount -t ntfs3 /dev/sda1 /whereveryouwannamountthethingor edit your fstab entry, something like/dev/sda1 /whereveryouwannamountthething ntfs3 defaults 0 0Here's the Arch wiki page for NTFS, the Arch wiki is usually where I'd start for fixing stuff, their documentation is fantastic.
If adding entries to your using fstab you should probably use UUID's instead of device names.
To get the UUID type
sudo blkid | grep /dev/sdb2where /dev/sdb2 is replaced with your partition name. This should give you the UUID for your partition.Then you can make an entry into your fstab that looks like this.
The reason you want to use UUID's is because the device name /dev/sda, /dev/sdb etc... can change but the UUID of your partition stays the same.
Thank you. I resolved the issue thanks to our brainstorming. Upd in OP.
(Sorry for a copy-paste answer, it's not about you, it's that my anxiety doesn't handle personal adresses well rn)
You're good, glad we could help!
You are most likely only missing ntfs support, which seems to not be installed by default: https://unix.stackexchange.com/questions/363583/cant-mount-ntfs-on-arch-linux
I'm not familiar with cachy-os but since its based on arch, the following should work:
Not sure if cachy-os will auto mount. But after installing the
ntfs-3gpackage, make sure you reboot.If it still doesn't work you can try to manually mount it or edit you're fstab so it it auto-mounted and assigned to the same device label.
The linked post is 8 years old. AfaIk, by now ntfs is in the regular Linux kernel (
ntfs3) and thentfs-3gFUSE driver in principle isn't necessary anymore. Yet, one may giventfs-3ga try if thentfs3kernel module doesn't work.OP may also try running
ntfsfixto repair the partition.TBH I was only interested in the install instructions (program name) for arch/pacman. Havent used an ntfs fs in ages but there is still a package for ntfs-3g in debian. He obviously lacks ntfs support atm
No,
ntfs-3gis not strictly necessary for NTFS support, (mount -t ntfsshould already work). It just offers more options and features than the standardntfs3which is already built into the Linux kernel. Yet,ntfs-3gperforms better under some circumstances (mount -t ntfs-3g). It also providesntfsfixand other neat tools.Thank you. I resolved the issue thanks to our brainstorming. Upd in OP.
(Sorry for a copy-paste answer, it's not about you, it's that my anxiety doesn't handle personal adresses well rn)
NTFS doesn't like to not cleanly getting shit down. I remember I needed to boot windows again and then shutdown, in order to access my NTFS volume from Linux, because last time windows didnt shutdown cleanly. Glad you got it fixed
see if you can get it to manually mount with ntfs-3g. If you can, set an auto mount after.
Manually it should look something like
sudo mkdir /mnt/drivename
sudo mount ntfs-3g /dev/sda1 /mnt/drivename
Thank you. I resolved the issue thanks to our brainstorming. Upd in OP.
(Sorry for a copy-paste answer, it's not about you, it's that my anxiety doesn't handle personal adresses well rn)
Please check the output of
fdiskon whether the filesystem is recognised correctly.Thank you. I resolved the issue thanks to our brainstorming. Upd in OP.
(Sorry for a copy-paste answer, it's not about you, it's that my anxiety doesn't handle personal adresses well rn)
Great 👍🏻