By dint of using your USB key, writing data to it, erasing it, plugging it in and unplugging it, it is quite possible that problems will arise one day.
The 1st possible problem is an error in the file system of your USB key.
Which can prevent you from accessing certain files, preventing you from modifying them, preventing you from writing data to certain places on your USB drive, or even running out of free space for no apparent reason.
To try to solve this problem, simply repair the file system by following our tutorial: Check and repair the file system on Windows.
Note: you will have to right-click "Properties" on your USB key visible in the file explorer and follow what is explained in the tutorial cited above.
The 2nd possible problem is an error outside of the main partition of your USB key, or even damaged blocks on the memory chip of your USB key.
To find out and try to fix the problem (if possible in your case), follow the steps below.
HD Tune is a free software allowing in particular to test the sectors of your USB key.
To do this, download and install this software, then plug in your USB key.
Once your USB drive is plugged into your computer, launch HD Tune and select your USB key from the list available at the top of the window.
In our case, it is a 64 GB SanDisk USB key.
Then, go to the "Error Scan" tab and click the "Start" button.
Warning : this process may take some time depending on the capacity (size) of your USB key, as well as its performance.
Wait while your USB key is tested.
After the test is completed, you will see whether any data blocks are damaged on your USB or not.
As shown in the legend to the right:
As you can see, in our case, the 1st data block of our USB key is damaged.
Which is problematic given that this is where the list of files (MFT for Master File Table) is located, as well as a copy of it (copy of the MFT) and system-specific information of files used.
In other words, if the 1st block is too damaged, it is possible that the data is no longer accessible. Unless you try to recover them using data recovery software, such as File Scavenger or Recuva, for example.
To attempt a quick file system repair from the Windows GUI, right-click "Properties" on your visible USB key in File Explorer.
Then, in the "Tools" tab, click on the "Check" button.
Depending on the version of Windows you are on, the options offered may vary.
However, the operation remains the same.
In Windows 7, check the 2 available boxes and click on "Start".
In Windows 8 and 8.1, click "Analyze drive".
In Windows 10, click "Analyze and repair drive".
Windows analyzes the file system of your USB key and tries to repair the errors found if necessary.
However, the test performed from the Windows graphical interface is not complete.
Windows will only perform the first 3 steps which are quite quick.
As you can see, in our case, Windows did not detect an error in the file system.
However, there are, as you will see in the rest of this tutorial.
To scan and repair the file system in depth the file system of your USB key, you will need to use the command line utility "chkdsk" present since Windows 7.
To do this, open a command prompt (cmd.exe).
In this command prompt, simply type the command below replacing "X" with the letter assigned to your USB key (visible in the file explorer).
In our case, our USB key has the letter "e".
Batch
chkdsk e: /f /r
As you can see, the "chkdsk" utility will perform several operations:
These steps can take time and especially steps 4 and 5.
This is the reason why only the 3 steps are performed when you run the file system scan from the Windows GUI.
As you can see, in our case, stage 5 of this "chkdsk" utility allowed us to detect errors in the master file table (MFT). Which was predictable given that it is the 1st block of our USB key that is damaged.
This is also logical given that this hidden file $MFT is necessarily very used to know the files present on your USB key, and this in any folder of it.
Unfortunately, in our case, the "chkdsk" utility was unable to repair this MFT.
Nevertheless, the problem is software and can therefore be fixed by starting from scratch.
This still allows you not to buy an USB key in this case.
Plain Text
Fixed errors in the Master File Table (MFT) mirror. Abandonment of CHKDSK. An unspecified error occurred (6e74667363686b2e 1798).
In the "DiskPart" command line utility present in Windows, there is a "recover" command which allowed us to solve our problem.
To do this, in your command prompt, type the command below to launch "DiskPart".
Batch
diskpart
Next, list the disks present on your computer.
Batch
list disk
Plain Text
Disk ### Status Size Free Dyn Gpt --------- ------------- ------- ------- --- --- Disk 0 Online 60 GB 1024 KB * Disk 1 Online 57 GB 0 B
Select the disk corresponding to your USB key.
In our case: disk 1.
Note: you can also refer to the numbers indicated in the Windows disk management available in the Windows "Computer Management" console.
Batch
select disk 1
Plain Text
Disk 1 is now the selected disk.
Type the command below.
Batch
recover
Plain Text
The RECOVER command completed successfully.
Quit DiskPart.
Batch
exit
Launch again the analysis and the repair of the file system of your USB key thanks to chkdsk via the following command.
Note: again, replace the letter "e" with the letter assigned by Windows to your USB key.
Batch
chkdsk e: /f /r
As you can see, this time the file system scan completes successfully without detecting any problem.
Which means that your USB key is normally repaired.
Launch the "HD Tune" software again, go to the "Error Scan" tab, select your USB key and click "Start".
Wait while your USB key is retested.
As you can see, your USB key has been repaired since no red blocks appear.
Articles 2/17/2017
Articles 1/21/2017
Windows 8/26/2024
Articles 11/2/2014
Pinned content
InformatiWeb Pro
Contact
® InformatiWeb.net 2008-2022 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.
You must be logged in to post a comment