Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 18807
  • Last Modified:

The file or directory C: is corrupt and unreadable. Please run the Chkdsk utility.

Experts:

I am run Windows 2000 server with SP up to date.

However, by now I got approx. :

5% of files and directory under c:\Program Files\ is not accessible.
90% of file and directory under C:\ other than c:\Program Files\ is not accessible.

And any clicking on those files or folders will invoke a popup window with messages :

>>>"The file or directory C: is corrupt and unreadable. Please run the Chkdsk utility."

when I do chkdsk in cmd window, I got :

>>>"The file or directory C:\WINNT\system32\CHKDSK.EXE is corrupt and unreadable. Please run the Chkdsk utility. "

I have not reboot so far and do believe if I do that the CHKDSK utility at Windows start up ( Black screen will take forever to fix the problem),

Could someone give me a clue about how I can get my files back.....

Thank you very much indeed in advance.

0
ca_roland
Asked:
ca_roland
  • 6
  • 5
  • 2
  • +3
1 Solution
 
210011999Commented:
Run Chkdsk /r from recovery console by booting from os disk.
0
 
ASW3382Commented:
Id just buy a new disk,  usually this isnt really worth fighting when $30-$40 bucks on newegg will make the problem go away.  Dont forget the more times you run the recovery or Chkdsk the worse the disk will get.
Then I would get a util like spinrite or Restorer 2K and restore the files.  I have had extremely good luck with both.   Spinrite is a tried and true solution and I have brought Hard drives back from the ticking stage to restore most of the data.
In any event,  if you value this information get a new disk,  install it and recover as much as you can from the old disk slaved to the system.  With a failing disk them more you use it the more you risk further corruption....

Good luck
0
 
ASW3382Commented:
If you are running a raid setup you may need to just find the corrupt disk and replace it...I really hope you are not striping.....
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
phototropicCommented:
If chkdsk is corrupt on your pc, try running it from a PE disk.
Download here:

http://www.nu2.nu/pebuilder/

chkdsk is found under the "storage" tab.
This will run chkdsk /r
It will take awhile to run.
When its finished, reboot.
Any change?
0
 
dcliveCommented:
As 210... said, this is easy to fix.

Just put your 2000 OS CD in the drive (or XP, or 2003 CDs...), boot from it, hit F10 at the first (Hit enter to continue) prompt, key in your password, and use CHKDSK to fix the disk.  If this is a filesystem/software problem, that's a good, clean way to fix things up.  

It might take a little while, but that will fix your disk.  I disagree with purchasing a new disk - you don't know if this is a hardware or software issue, and could quite likely be just a software issue that chkdsk will completely fix.

I disagree with chkdsk only being able to be run a finite amount of time.  There is no limit, although if your disk keeps getting corrupt and chkdsk keeps fixing it, I'd ask what you're doing (constant power outages?) that would corrupt the filesystem on the disk.

Are there any disk-related errors (50, 51) in the event logs?
0
 
ASW3382Commented:
Was just trying to save the guy some time.  We dont know what kind of data is on the disk but if it is data that is not too important then trying to restore it would be the way to go.  But myself being the guy who takes care of important data such as intelligence and SS#s I know that when disk corruption is spotted that unless I have a good backup the first step after confirming data corruption is to get a backup.  Then play with the data.  If a head is failing,  it can drag on the disk or if a bering is going out, any scan disk method will wear the disk down even more.  If it is a hardware malfunction you usually do have a finite amount of time before the drive becomes unreadable.  
However we can now just leave it up to Roland to decide how careful he needs to be.
0
 
mrandymanCommented:
1.  Boot from the Windows CDROM  (thanks I know you have it right)
2.  Go to Recovery CONSOLE (yup command line chief)
3.  login
4.  type  CHKDSK  /?   to get an overview of what cool features you can use!
5.  I use CHKDSK C: /R  (this locates and maps out bad sectors...ALWAYS good to use!!!)
6.  Don't trust moi?  FINE....go to Microsoft and read all about it.... http://support.microsoft.com/kb/314058/

Love ya!

Andy  
0
 
dcliveCommented:
210's answer is correct and should be used. Buying a new disk isn't a good solution to this problem without confirmation the disk is bad first!
0
 
dcliveCommented:
There is no description saying that the disk itself is bad.  The description given only comments on the disk's filesystem, which is corrupt.  CHKDSK is the normal way to fix this problem.  If the disk's version of chkdsk cannot be run from recovery console on the disk due to the corruption, the normal way to fix this problem is to boot to a 2003/XP CD, which has its' own version of the recovery console on it with its' own version of chkdsk, which will then fix the problem.  
0
 
dcliveCommented:
I'm sorry, but I still cannot agree.

If the filesystem is unrepairable, CHKDSK will tell you.  You can't know that until you've run it.  For all we know, it could be a bug in scsiport.sys, a bug in his disk controller driver, a power outage at the wrong time, or any of a thousand other problems which caused a temporary issue with the disk filesystem.  Until he runs chkdsk and tells us what happens, all of this is a guess.

However, I completely disagree with you concerning "it's probably bad" - at Microsoft, while working in the Setup group (responsible for handling disk issues for premiere customers) I saw all kinds of disk corruption issues, and many of those had nothing to do with the physical disk hardware itself.  Throwing out disk hardware just because he's prompted to run chkdsk is silly and wasteful.

If he has lots of 51s and similar errors in his eventlog, THEN one should start looking at disk hardware.  Until that time, run chkdsk, just like the prompt says, and from there we can form our next course of action.

Chkdsk is there to fix this *exact* problem.  That's *why* MS wrote it.  We should at least try it, first, before assuming things.  
0
 
rindiCommented:
I still don't agree. Chkdsk will most likely fix some errors and also result in many files getting moved to the folder that it creates and which are then not readble or usable. This will result in a system with missing software and therefore unstable. In a way therefore chkdsk masks the real problems as the system might look as if it was working. If nothing more is done that will result data being lost when the disk really goes bad. Therefore at least the diagnostic of the disk manufacturer should be run. From personal experience these errors are almost allways indications of a disk going bad.
0
 
dcliveCommented:
*IF* this is a disk problem.

If it's "just" the filesystem getting corrupt, Chkdsk will resolve the issue.

Until we run chkdsk, we're all just guessing.  To say the disk should be thrown away, just like that, without looking deeper into the problem is absurd.
0
 
rindiCommented:
Not thrown away, but rather RMA'd if it is still inside warranty. But even then you need another disk to save your data to. From experiance it is a disk problem most of the time.
0
 
ASW3382Commented:
No one said to throw away a disk.  Listen to what is being said.  chkdisk will fix some issues.  You are correct.  BUT what IS being said is to make a BACKUP to another disk.  This is the SAFEST way to work with a disk that may be failing.  Even if it is a file structure issue and the disk is fine you still need a BACKUP.  You do not know what is on the drive, you do not know what state the drive is in.  Therefore the FIRST thing to suggest is make a backup.  THEN run your checkdisk utilities and have fun with it.  It is a hard lesson learned and that is what rindi is trying to show here.  Backing up is the first step, always has been, always will be.  Should have been being done before the error occurred so we wouldnt have to discuss if chkdsk is the end all.  
0
 
dcliveCommented:
That I'd agree with, ASW3382.  :)
0
 
ASW3382Commented:
;)  where did the roland fellow go anyway?  Hope they fixed the issue,  of course this could be just a person learning the backup lesson the hard way ;)
0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 6
  • 5
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now