[SOLVED] Corrupted External HD

rod09 · 08-08-2019, 05:10 AM

Hello everyone!
So it seems I borked my external HD's filesystem by pulling the plug on a rush. I just realized that this morning while plugging in the HD in my openSUSE machine and was greeted with a mount failure message:

Code:

$MFTMirr does not match $MFT (record 0).
Failed to mount '/dev/sdb1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

A few years ago I was able to restore a damaged ext4 partition just by rebuilding it with fdisk. I was tempted to do that again with my external HD's NTFS partition but I am not so sure it is a good idea. What do you guys think? How can I restore my external HD's data using my Linux environment?

teckk · 08-08-2019, 08:31 AM

Stick it into a Microsoft windows machine and let "it" fix "it's" proprietary file system.

You can try ntfs tools, don't know where Suse keeps that.
http://manpages.ubuntu.com/manpages/...ntfsfix.8.html

That's a common problem with NTFS drives, if you get in a hurry. Un mount it, then wait 10 seconds before you pull it out.

teckk · 08-08-2019, 08:41 AM

It's part of ntfs-3g
https://www.tuxera.com/community/open-source-ntfs-3g/

rtmistler · 08-08-2019, 08:44 AM

Quote:

run chkdsk /f on Windows then reboot into Windows twice.

In the words of the late Whitney Houston, "I have nothing!"

What teckk said. But I'm curious, was it in a Windows machine when you pulled the power?

Either case, seen many disks get corrupted, and specifically while using Windows. It takes a disk check under Windows action, and usually gets resolved as part of that.

If not, then advise further about your problem.

rod09 · 08-08-2019, 08:48 AM

Quote:

Originally Posted by teckk

Stick it into a Microsoft windows machine and let "it" fix "it's" proprietary file system.

You can try ntfs tools, don't know where Suse keeps that.
http://manpages.ubuntu.com/manpages/...ntfsfix.8.html

That's a common problem with NTFS drives, if you get in a hurry. Un mount it, then wait 10 seconds before you pull it out.

Great tip!
ntfsfix solved it. I just needed to run the following:

Code:

ntfsfix /dev/sdb1

By the way, ntfsfix was already installed in my machine via the ntfs-3g package

Thanks very much

rod09 · 08-08-2019, 08:57 AM

Quote:

Originally Posted by rtmistler

In the words of the late Whitney Houston, "I have nothing!"

What teckk said. But I'm curious, was it in a Windows machine when you pulled the power?

Either case, seen many disks get corrupted, and specifically while using Windows. It takes a disk check under Windows action, and usually gets resolved as part of that.

If not, then advise further about your problem.

No it was actually on my openSUSE machine. I left Windows behind years ago so I don't have a machine around to fix my hard drive. It was really a dumb move to pull the plug like that, but now the problem's solved