Error mounting [path], wrong fs type, bad option, bad superblock on [path], missing codepage or helper program

There was a power outage at my place while I was on my computer.

After I restarted my computer, a drive of mine, which is NTFS, would not mount.

I would get this error when trying to access it:
error mounting /dev/sda1, wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error

Can anyone help me try to recover my drive?

Some of the things I tried were:

sudo blkid /dev/sda1

Response:

BLOCK_SIZE=“512” UUID=“[idhere]” TYPE=“ntfs” PARTUUID=“[partuiid here]”

sudo fsck /dev/sda1

Response:

fsck from util-linux 2.40.2

I do have ntfs-3g installed and I re-installed it.

I used gparted to see if I could repair it.
Response:

Check and repair file system (ntfs) on /dev/sda1 00:00:00 ( ERROR )

calibrate /dev/sda1 00:00:00 ( SUCCESS )

path: /dev/sda1 (partition)
start: 2048
end: 976773119
size 976771072 (465.76 GiB)
check file system on /dev/sda1 for errors and (if possible) fix them 00:00:00 ( ERROR )

ntfsresize -i -f -v ‘/dev/sda1’ 00:00:00 ( ERROR )

ntfsresize v2022.10.3 (libntfs-3g)
$MFTMirr does not match $MFT (record 3).
ERROR(5): Opening ‘/dev/sda1’ as NTFS failed: Input/output error
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
and will be made to NTFS by this software until it gets repaired.

I noticed the part where is says run chkdsk /f on Windows. But, I’m not on Windows. So, what can I do?

I do have a Windows computer. But, I would find that painfully tedious :slight_smile: to move my drive to that computer. If possible, I’d like to be able to resolve it on my Manjaro installation computer.

Thanks, any help would be appreciated.

It’s apparently an NTFS file system on that partition.

Can be used by Linux - but upon failure or problems with it can only be properly dealt with by … Windows and it’s native tools.

Boot a Windows or a minimal Windows environment and use it to assess and fix the file system - which can’t be done using Linux tools only.

that is maybe unfortunate - but the only way to deal with the issue properly.

use a different file system on the device (not ntfs) to avoid this

2 Likes

Ok, I was afraid that was going to be the response.

Anyways, I forgot, I have an external drive holder. So, I can use that and then try and fix it.

Thanks!

I ran chkdsk /F on the drive and it didn’t work initially. But, after 3 tries, it worked. One thing I noticed is that you need to make sure it unmounts from Windows properly. It didn’t at first and so I shut down the computer.

Then, I loaded it again on Windows 11 and it seemed to work properly as I could unmount it successfully, but, it still wouldn’t mount on my Linux computer.

I tried it a third time on Windows 11 and then it discovered something was wrong when I just inserted the drive. Not sure why it didn’t detect the first or second time. I accepted it’s scan and repair. And then when I tried it on my Linux computer, the drive was readable again.

Mind you, all this time, the drive was readable on Windows 11.

I`ts nice and all for you
but you are describing and expecting a, perhaps fairly normal … file system related thing

… What seems to be the problem?

The messages could not really capture it.

I see.

I’m moving my files now to a ext4 formatted drive.

1 Like

In case you ever wish more information; and if you have the time:

Regards.

1 Like

Thanks!

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.