External HDD fails to mount

Two days before this thread auto-locked. You were asked to start a new thread, now that the booting issue has been fixed. You did not.

So…

There is risk.

How does it work when you use the sudo mount sudo mount -t ntfs /dev/sdc1 /mnt/ ?

You can always try mounting it with /etc/fstab if you think you can try that.

You can try adding this to the bottom of your /etc/fstab. This may work, without changing the permissions on the drive.

UUID=6C713AF620551318  /liam-games      ntfs   user,nofail,rw,data=ordered      0  2	# /dev/sdc1

I am so sorry, I honestly feel horrible for this; I truly do. I can see you’re upset about this, are you sure you want to proceed when I’ve wasted your time so much already?

I was told by @LeeTalbert to make a new thread or join the one I had linked. I made a new thread, and it was here: OM ROME won’t boot after recent update. In that thread, I was helped and the issue with the kernel was solved by selecting an older kernel version to boot with until it worked again. Since that problem was solved for the time being, and I was told that a fix was being worked on for a future update, I thought it would be safe and reasonable to end that thread there.

It’s a command that I mentioned in my very early message, when I said:

It only puts a band-aid on the problem by allowing me to forcibly mount the hard drive, but I do not have all permissions. I can only read the data, I cannot write anything to the drive.

Ok, I’ll give that a shot and let you know. If I shared with you the existing contents of fstab as well, would that be of any use to you?

1 Like

Yes, please post the existing contents of /etc/fstab

By the way. It’s not the waste of time. It is the fact that I slept 4 weeks and don’t remember all of it. The thread is now 125 replies and I have to read the whole thing to bring myself back up to speed.

1 Like

Okay, well before we proceed any further and you possibly end up re-reading the whole thread - Why don’t we start fresh to make things easier. If you think it’s a good idea, I will completely re-install OpenMandriva fresh. That way, we don’t have to keep track of all the little changes I’ve been doing to the system throughout this thread that I did two months ago. I already know that the issue still persists when I re-install it. I could start a new thread, and I will re-read through this whole thread myself to find as much information as I believe is relevant and necessary. That will put the load on myself and not waste your time and possibly anyone else if they decide to also read through this thing to help me, too. What do you think?

1 Like

Just post the fstab for now

Alright, here is the fstab file:
fstab.txt (720 Bytes)

Lets try it with this.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=75FA-030B                            /boot/efi      vfat    defaults,noatime,umask=0077 0 2
/dev/mapper/luks-51d94b0e-5ed9-49f4-bed3-80d33398eb9b /              ext4    defaults,noatime,discard 0 1
/dev/mapper/luks-874d153d-6239-4889-8bd3-4f6aecce8e22 swap           swap    defaults   0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
#
# /dev/sdc1 USB
UUID=6C713AF620551318  /liam-games      ntfs   user,nofail,rw,data=ordered      0  2

You will need to reboot.

user means if you boot first and then plug in the drive, you can mount it without sudo, as in just click on the drive in Dolphin.

nofail means that if the drive is not plugged in, the PC will still boot without it.

rw should make the drive read/write. Hopefully. :grinning:

1 Like

Alright. I pasted those lines into the fstab file exactly and rebooted. After rebooting, I attempted to mount the hard drive by clicking it through Dolphin. I’m still getting the original error:

“An error occurred while accessing ‘Liam’s Gameplay’, the system responded: The requested operation has failed: Error mounting /dev/sdc1 at /media/mandriva/Liam_s Gameplay: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error”

I took a look at the fstab file and it now has these contents:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=75FA-030B                            /boot/efi      vfat    defaults,noatime,umask=0077 0 2
/dev/mapper/luks-51d94b0e-5ed9-49f4-bed3-80d33398eb9b /              ext4    defaults,noatime,discard 0 1
/dev/mapper/luks-874d153d-6239-4889-8bd3-4f6aecce8e22 swap           swap    defaults   0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

It did not save the changes. Paste the above in again, but you have to sudo.

Right, I forgot I need to sudo. It appeared to have saved. I’ll give it another shot.

Alright, I pasted it in again, saved and rebooted. The fstab file definitely has the changes saved now. The exact same error message persists.

I can’t remember if this has been done, so try it please.

sudo dnf install ntfs-3g ntfs-3g-system-compression ntfsprogs lib64ntfs-3g

I don’t believe it’s been done yet, but I think the output is saying those packages are already installed. For some reason it’s having trouble downloading metadata for the repo ‘repository’. I know we were doing a bit of messing around with repo files. This is the output:

[mandriva@openmandriva-x8664 ~]$ sudo dnf install ntfs-3g ntfs-3g-system-compression ntfsprogs lib64ntfs-3g
[sudo] password for mandriva: 
LibreWolf Software Repository                                          462  B/s | 833  B     00:01    
Error: Failed to download metadata for repo 'repository': repomd.xml GPG signature verification error: Error during parsing OpenPGP packets: Corrupt PGP packet
Ignoring repositories: repository
Last metadata expiration check: 1:47:59 ago on Thu 15 May 2025 22:48:07.
Package ntfs-3g-2022.10.3-1.znver1 is already installed.
Package ntfs-3g-system-compression-1.0-3.znver1 is already installed.
Package ntfsprogs-2022.10.3-1.znver1 is already installed.
Package lib64ntfs-3g-2022.10.3-1.znver1 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[mandriva@openmandriva-x8664 ~]$

I’m not sure what the “corrupt PGP packet” is about or if it’s relevant. I don’t know what a PGP packet is.

That is an error for the security keys for the LibreWolf repo. You can ignore that. All of the programs are installed.

This leaves nothing but to chown the ntfs partition on the drive. Think about the risks before doing it.

I don’t know your situation. Where you live, income, etc., so I have no idea how hard it would be to get another drive and just copy your game files over to it.

Gathering info for now. Sorry, but there is so much to go through.

Try replacing what you put in /etc/fstab with this.

UUID=6C713AF620551318 /liam-games ntfs-3g user,nofail,rw,uid=1001,gid=1006,data=ordered,umask=000 0 2

EDITED for the user ID

I don’t really know what kind of risks there actually are. The worst I imagine could happen is that I get locked out of the drive entirely somehow and permanently can’t use it or access the data anymore. I don’t know though if that’s the kind of risk I should expect or not. I’m in Australia. Financially it would be a bother to get a new hard drive if I were to screw it up somehow, but it wouldn’t be the end of the world. What’s most important to me is not losing the data itself. The data is essentially hundreds of hours of gaming memories, and the whole purpose of buying the drive in the first place was to hold the ever-expanding library of videos on it. I haven’t been able to make a proper backup for that data yet.

The HDD having the issue is a 2TB drive, and is named “Liam’s Gameplay”. Currently about 800GB is in use. I can’t back it all up on my main storage drive “Linux Storage”, because that one only has 592GB free. I do, however, have an extra 2TB internal drive in the house that I’m not currently using that has plenty of space on it, so I could back up to that.

I thought I remembered that I couldn’t take anything off of the “Liam’s Gameplay” drive due to the permission limitations, but I just tested it. It appears that I can copy/paste all the data to another drive, thank God. It just won’t let me cut/paste. So before I try to chown the ntfs partition, I will try to backup the data to my other HDD in the house first.

I’ll give it a try.