Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Friday, June 17, 2011

$MFTMirr does not match $MFT (record 0)

Source
 BY 

Sometimes, when you are executing a file transfer between your computer hard drive and an external drive and your computer shutdown for some reason (in my case, no battery/ac power) it’s pretty common to get some errors on external drives that uses NTFS as they file system.

The most common message is:

Error mounting: mount exited with exit code 13: $MFTMirr does not match $MFT (record 0).

Failed to mount ‘/dev/sdb3′: 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.
One workaround for this issue is to do as the message says, boot on Windows and try to use the 
awesome
 NTFS tool that Windows offer. But a perfect solution for a Linux users is to use the ntfsprogs utility.
ntfsprogs is a suite of NTFS utilities based around a shared library. The tools are available for free and come with full source code.
  • mkntfs: Create an NTFS volume on a partition
  • ntfscat: Print a file on the standard output
  • ntfsclone: Efficiently backup/restore a volume at the sector level
  • ntfscluster: Given a cluster, or sector, find the file
  • ntfsfix: Forces Windows to check NTFS at boot time
  • ntfsinfo: Dump a file’s attributes, completely
  • ntfslabel: Display or set a volume’s label
  • ntfslib: Move all the common code into a shared library
  • ntfsls: List directory contents
  • ntfsresize: Resize an NTFS volume
  • ntfsundelete: Find files that have been deleted and recover them
  • ntfswipe: Write zeros over the unused parts of the disk
  • ntfsdefrag: Defragment files, directories and the MFT
  • ntfsck: Perform consistancy checks on a volume
  • nttools: Command-line tools to view/change an offline NTFS volume, e.g. ntfscp, ntfsgrep, ntfstouch, ntfsrm, ntfsrmdir, ntfsmkdir
  • ntfsdiskedit: Walk the tree of NTFS ondisk structures (and alter them)
Be careful with these utilities, they might damage the filesystem, or your hard disk !
With ntfsprogs installed (sudo apt-get install ntfsprogs) you should execute the following commands in a terminal:
sudo ntfsfix /dev/partitionName
After this command you should expect the following output:
~$ sudo ntfsfix /dev/sdb3
Mounting volume... FAILEDAttempting to correct errors...Processing $MFT and $MFTMirr...Reading $MFT... OKReading $MFTMirr... OKComparing $MFTMirr to $MFT... FAILEDCorrecting differences in $MFTMirr record 0...OKProcessing of $MFT and $MFTMirr completed successfully.Setting required flags on partition... OKGoing to empty the journal ($LogFile)... OKNTFS volume version is 3.1.NTFS partition /dev/sdb3 was processed successfully.
After this step you should be able to access your external drive partition as usual, mount or use nautilus to access your files.
Source:  http://gnuwin32.sourceforge.net/packages/ntfsprogs.htm


How to recover files off a crashed hard drive


One universal true about computers is this: the hard drive will fail. It is not a matter of if, but a matter of when. In an ideal world, every computer user would make regular, full backups of their system. Unfortunately, that isn’t the case, and far too often computer users find themselves with a crashed hard drive.
If your hard drive has crashed and you’re unable to boot into the system to retrieve your files, you’ll have to take a different, more involved approach. This tutorial will show you how to recover files off of a crashed hard drive.
These instructions assume that the hard drive is crashed but not physically damaged. You can use these instruction with both Mac OS X and Windows. You will need a second computer with Internet access and a DVD burner, a blank CD, and the crashed system should have an optical drive.
Step 1
Download a Linux distro that offers a LiveCD, or that can be run from a CD or pen drive. Small-file size options are Puppy Linux and Damn Small Linux. However, I recommend downloading Ubuntu, simply because mounting a drive is effortless with it and does not require the Terminal.
Step 2
Burn the downloaded ISO file to a blank CD using Nero or any other burning software.
Step 3
Insert the CD into your crashed system and restart the computer. At BIOS, enter setup by pressing the designated key for your system – for most computers, it’s F12 or ESC.
Once in BIOS, select Boot Sequence and highlight CD/DVD Drive. Press the ‘U’ button to move the option above the internal hard drive, then save and exit BIOS.
The computer will restart and the Ubuntu logo will be displayed along with a menu of options. Choose ‘Try Ubuntu….’ This will start Ubuntu, running it from your CD drive. Don’t worry, it won’t affect your hard drive in any way.
Step 4
After Ubuntu has loaded, look in the upper left corner. Choose Places. Towards the bottom of the menu, you will see a picture of a hard drive – it will say something like ’0.0GB Drive’, displaying the capacity of your internal hard drive. Click to mount.
Step 5
Plug in your external hard drive or flash drive. Navigate to Places and choose the new drive you just plugged in to mount it.
Step 6
The internal hard drive and external media are now mounted. Look on the desktop for the hard drives. Click them to open.
In the windows that appear, you can choose Documents and Settings and copy the data files to your external drive, or you can simply copy the entire internal drive to the external drive and sort it out later.
Step 7
Once finished, shut the machine down and remove the CD when instructed.
You can now reload your system as normal.
http://www.ubuntu-es.org/?q=node/124721

1 comment:

Robert C said...

My external Drive was not working function. This helped me fix my problem.

Thanks

Rob