Shulou(Shulou.com)06/01 Report--

In our data recovery work, we often encounter failures such as "partition prompt formatting" or "file directory structure error or corruption", which is usually caused by bad hard disk or damaged partition parameters.

Usually, we first use third-party recovery tools to safely back up the data and then repair the original equipment.

Chkdsk.exe is the command line interface of the CHKDSK program, which we can use directly from the command prompt program box, which is used to verify the logical integrity of the file system. If CHKDSK finds a logical inconsistency in the file system data, CHKDSK performs an operation that repairs the file system data.

Disk overhaul command (chkdsk) has always been one of our most powerful commands, but sometimes we encounter special situations where we cannot use this command to repair the corruption of partition file directories, such as this example:

Seagate 1TB mobile hard drive partition RAW case, in most cases the cause of the failure is a corrupted file system directory or other logical problems. In the normal process, the data in the partition should be copied first, and the disk maintenance of the failed partition should be done after the data copy is completed. However, there is no guarantee that the disk will be overhauled successfully, or some files may be damaged and the directory may be damaged after overhaul.

After the data copy of the failure disk is completed, it is ordered to overhaul it, and it is always found as follows:

The attempt to replace the computer and uninstall the hard disk was fruitless. Check the partition in winhex and find that there is no $MFTMirr file in the directory browser. Determine that the cause of the failure may still be related to the NTFS system metafile. First locate $MFT and $MFTMirr, and find that the "volume" file record of No. 3 ID is lost in $MFT. Before and after checking, it is found that the loss of the "volume" file record is caused by the offset of the file record, as shown below:

After determining the file recording problem before ID No. 4, write records 0, 1, and 2 back to the normal location, and copy the "volume" file records from the normal partition to the appropriate location of the fault partition:

After saving and exiting, the partition can be opened for normal use to ensure that it is normal and correct. We use the maintenance command again and find that the maintenance is smooth and the user data is complete:

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.