Skillfully use DOS command to repair u disk File error

We usually do not use the computer when the DOS command. The general user at most understand a few simple DOS commands, such as the most frequent is to use ping command to detect network situation, today small edit to teach you how to use the chkdsk command on U disk File system error repair.

First of all, what does the Chkdsk command do? Does it have anything to do with our USB drive?

The chkdsk command is a key command for repairing file system errors in DOS. So, the U disk File system errors will cause harm to our data security? Do we need to fix it?

Yes, it is necessary for us to fix the file system error because it is likely to cause considerable harm to our data security.

When the file system is a serious error, or a common error accumulation to a certain extent, the U disk part of the file will not be able to open or copy. Even when we copy data from the computer to the U disk, it will also inexplicably appear the situation of copy interruption (because of file system errors caused by such problems occur on the premise that U disk space is large enough, and there is no damage in the activity of the virus). or simply the entire U disk must be formatted to use again, U disk inside the original data annihilated!!

Of course, it is best to use the quality of the USB disk, they are both a file system error is relatively easy to repair. The chkdsk command is described below:

The Chkdsk command is a dedicated command for repairing media that Windows can recognize, such as U disk, hard disk, memory card, and so on. This command is an abbreviation of Chkdsk+disk.

OK, nonsense I won't say more, let me introduce how to use CHKDSK to maintain our U disk

Operation Steps

Start running (you can also press the start key +r key combination to call out the Run menu) CMD carriage return (if the Windows7 user, you can also press the start directly in the blank column input PowerShell, Windows7 The latest command execution tool PowerShell to execute CHKDSK command)

When you open a DOS or PowerShell window, execute the following command:

Enter CHKDSK (u disk letter):

For example, check the K disk to enter:

CHKDSK k:

This is a read-only query that fixes a problem where some index entries are missing.

Special emphasis: If you ask "whether to convert lost links to files," Select No (N), and then press ENTER. Windows does this just to make it easy to see the "lost" file, but once it's been converted to a file without an extension, we won't be able to use it, so there's no point in fixing it.

If this is the case, you need to use the command at the bottom of the advanced point.

If there is a larger problem, you need to enter:

CHKDSK (U disk letter):/F

For example: Fix k disk is chkdsk k:/f

At this point you need to forcibly remove all open handles in the U disk (first need to turn off all of the U Disk Open program), and then Windows exclusive U disk for file system errors. The repair capability is greatly improved at this time.

After you confirm that all open programs have been turned off, if you are prompted to force the removal of the volume, enter y, and then press ENTER

The repair time required for this method will be longer than the read-only time, but how much longer it will depend on the severity of the U Disk File system error.

If you are prompted for the volume is in use, do you want to check the volume at the next reboot and select N

Under normal circumstances, use once:/F command to repair all U disk errors. Then run chkdsk again: command to display "Windows checked file system and make sure there is no problem", then we can safely use the U disk.

Note: If you want to let the program automatically remove all the open handle of U disk, then enter CHKDSK (U disk letter):/x can. Windows will automatically remove all open USB stick handles and then completely seal the repair on the USB drive. But I do not advise you to use it this way. For example, we are using a similar 360 software butler download tools to the U disk to download files, when the file has not been downloaded to complete the. peer-to-peer format. However, this operation will cause these files to be corrupted!

If there is a problem with the U disk, there may be some of the file cluster has been lost, need to be retrieved, then we need the following command:

CHKDSK (U disk letter):/F/R

For example: Fix k disk is chkdsk k:/f/r

At this time not only need to remove all the open U disk handle, but also to the entire U disk for high intensity scanning. This is the most powerful repair, but the longest time, but also may lead to a U disk temperature is too high, it is recommended that you do not use this command. If you must use, please be sure to do a U disk cooling measures.

The above method can be used to repair 97% of u disk problem.

If the above is not, there may be a U disk autorun virus, you need to repair it (recommended that you use Super Patrol U disk immune device to solve this problem, because the implementation of the following command has a certain risk)

attrib (u disk letter): "Auturun.inf"-a-s-r-h

Del (U disk letter): "Auturun.inf"/f/s/q

The above method can solve 99% u disk problem, if not, please find Data recovery company (charge)

The above method is also suitable for hard disk

OK, fix u file system error DOS command introduction finished, then file system error is how to produce it?

Windows XP operating system I believe everyone has used it? XP operating system of a major flaw, coupled with the bad habits of everyone, it is easy to allow u disk to produce such a file system error:

When we insert a U disk on the XP system's computer, the computer will connect the U disk first. Then immediately disconnect the U disk connection, and then restore the U disk connection. If we open it when the computer just recognizes the U disk, it is possible that the corresponding file system error is caused by "abnormal eject".

Solution: on XP, insert U disk, after the computer identified a U disk, please wait about 5 seconds to open U disk.

There is a more common situation: we intend to eject the U disk normally, but Windows prompts "device xx is in use, cannot eject". Then we forcibly pull out u disk, this may also cause U Disk File system error.

Solution: If you do not prompt to eject the U disk, and we can determine that all open files in the U disk has been closed, then please confirm that there is no copy of the file in the U disk to pull out the U disk.

There is also a situation most easily overlooked by everyone: when Windows prompts "XX device has been safely ejected" immediately unplug the U disk, but also very easy to produce file system errors!

Solution: In the tip "XX equipment has been safely ejected" please do not pull out the U disk, wait 2-3 seconds before pulling out u disk.

The above method can let everyone use DOS command to repair u disk File system. In addition, we also need to understand, sometimes when we copy files, the computer and U disk connection suddenly interrupted, this will cause a U disk File system failure.