The file or directory H:\ is corrupt and unreadable. Please run the chkdsk utility

dsi1

Honorable
Jul 14, 2013
12
0
10,510
WIN 7/64: I get the error message 'The file or directory H:\ is corrupt and unreadable. Please run the chkdsk utility.' It won't run, how do I fix this?
 


How long has it been since you have had your system is it relatively new or old?

I did some research and found a recovery method for a similar situation]

"Try this 1

Click on Start --> Run --> Type cmd and press Enter.

"Command Prompt" will be opened.

Since you are having problem with G & H drivers, enter the below command

chkdsk /f g: --> Press Enter.

chkdsk /f h: --> Press Enter.

Good Luck" So just do what that says and it should work it had lots of upvotes

Here was my source use it at your own basis
-http://ccm.net/forum/affich-706028-file-or-directory-is-corrupt-or-unreadable
 

If that solution did not work try this one

"It is possible the hard drive died, but it is equally possible a corruption happened in the file table.
If it is the latter then Chkdsk could fix it.

First, you need to get to a Command Prompt. For that use Option Two in this tutorial: (Use at own Risk)
System Recovery Options
And choose Command Prompt from the list of recovery options.

Then at the Command Prompt type this: chkdsk C: /f
And then press ENTER

Let it run all 5 tests without interruption.
Good luck."
Source-http://www.sevenforums.com/hardware-devices/266444-boot-corrupt-unreadable-repair-re-install-windows-fails.html
 


I get a response of Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if the volume is dismounted first. All opened handles to this volume would be invalid. would you like to force a dismount on this volume Y/N?
I have no idea what that means, so I said NO. I then go would you like to schedule this volume to be checked the next time the system restarts? that sounds reasonable so I will say yes.
A question for you is about the /f will that reformat and is it safer to use /r which I read includes /f...? I have no idea if that is a fact, it is just a question.
 
The unit is a W520 that is about 4.5 years old, however tech support came thru here last June or so and gutted it and replaced everything but the keyboard and disk drive and screen. They said they couldn't be sure from their test results what might be affected, so... lucky me.
 


 
First off, I want to thank you for taking the time to try and help me out. Your suggestions were all excellent, and I think if it had proven to be something slightly different they might very well have been the hoped-for cure. What they did do, is enable me to run a series of relatively safe command actions that narrowed down, and more clearly isolated and identified the exact nature of the problem through the surgical practice of elimination. In the end result, Chkdsk in all its permutations was not a willing partner to the process as a direct cure, but were, quite definitely by the response results, a big diagnostic help.
I first did a rename of the partition just on the wild chance that it might be a fix, and is a harmless act, in and of itself. I then used 'Recuva' (of Piriform/CCleaner/Speccy fame) in order to see 'into' the folders, and it was apparently a rescue partition filled with the necessary OS files. The partition was not corrupted, only the file addresses necessary to open the drive sector were 'lost' so I was able to wipe and reformat within the partition. It became apparent through using your toolset of suggestions, extremely important to determine if it was the partition OR the files contained within the partition. They seemed to represent two very divergent paths that could prove inimical to each other as to solutions and losses.
What I realized was that when faced with this kind of issue it is imperative first to diagnose and identify, before trying random fixes, especially if the issue is 15GB of unknown files and another 450GB+ of at-risk data files if you blunder on your choice of command line switches. The problem being that you can't necessarily 'undo' many of the possible choices if you happen to guess incorrectly.
It would be great if someone with real knowledge created a workflow/solution set just identifying the steps and choices in narrowing down the potential issues.
Your suggestions were a big help in that process.