I'm using a 1 TB external HDD from Western Digital, Element series. Formatted as NTFS.
I was able to mount the drive and use it as normal in Karmic.
However, while creating folders within the drive recently, the drive unmounted itself silently. So after waiting for 2 mins, I unplugged the USB and replug it.
I have a VBOX windows XP running in background, not sure if the virtualized windows did anything to it...
And I got this error message and some instructions for windows system:
I can't even mount to check it.
Error mounting: mount exited with exit code 13: $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.
Any one knows any software approach to handle this situation?
I really hope it's not a hardware fault, or I'll have to open up the casing, and prepare for the worst...
Ok the HDD works fine with a Windows OS machine.
I'm just guessing a work around: Does anyone knows a way to reset the $MFT or MFTMirr records please?
Ok solved it using ntfsprogs package
sudo apt-get install ntfsprogs
Should fix immediately without reboot.
sudo ntfsfix /dev/sdb1
Replace the device path with your own error report's device path.
Certain files that were being moved around before the silent unmounting event, now cannot be moved or deleted, but they can be copied and accessed.
Probably need a system restart...
Unable to trash file: Input/output error
Error removing file: No such file or directory
Edit4: There's still some inconsistency errors. My findings are the same with coffeecat: you need to plug it into the windows operating system to run checks for a proper fix. There are also some data corruption, though the exact number of files affected is unknown. Woe be me for NTFS...