Question Locked

CHKDSK doesn't repair disk errors

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I know my hard drive is failing, and I need to buy a new one asap! But I'm curious about something...

I boot from my Vista install disk, and start up the recovery console. I get to the command prompt, and run CHKDSK c: /r

During the scan I notice a lot of errors being repaired. (File sysytem and surface errors) At the end of the scan I get "Failed to transfer logged messages to the event log with status 50".

I get this every time I run CHKDSK, using the X switch, or R switch, or F switch. And the funny thing is, I get the SAME ERRORS being reported as fixed every time. The same! So I guess even though the errors are being reported as fixed, CHKDSK is not actually doing the repairs?

Sorry for the long message, but I was trying to give a clear explanation of my problem!

9 replies

by older mycroft

You are not using the correct command structure!

'chkdsk c: /r' - ain't gonna cut the mustard

First: run 'chkdsk c:'
If it reports any cluster problems answer 'yes'
Then: run ' chkdsk c: /f /v '
This should give a running commentary as it works.

[u]Afterthought![/u]
Ofcourse, your HD may be too badly corrupted for CHKDSK to cope with.

by kcox2

Old Mycroft,

I'm constantly amazed not only by mis-information given out by people like yourself, but also by the fact that in the last YEAR, no one ever bothered to call you out for being WRONG in what you said.

Regardless of the OS being XP or Vista, CHKDSK C: /R does EVERYTHING that your suggested two-step process of CHKDSK C: followed by CHKDSK C: /F /V would do PLUS it adds the system checking for bad sectors on the hard drive and recovering any readable information they may contain. The /V switch is simply there for window-dressing as it initiates a more Verbose output.

Although your resposne was the ONLY one made to this person, I'm dismayed that the only response contained misinformation.

by older mycroft

Nice to see that my contributions are read by another peer, even if it is a year later and irrespective of the fact that it it misinterpreted.

The '/R' function specifies the recovery of Bad Sectors.

The '/F' function specifies the fixing of file system errors.

Clearly there is little or no reason to attempt recovery of bad sectors until any corruption of the file system has been remedied.

The '/V' function is to make Chkdsk verbose, reporting everything it is doing. It is best invoked if previous runs have not fixed any problems, because in verbose-mode you can SEE where Chkdsk is failing!

FYI - if you were to start Chkdsk from [b]INSIDE WINDOWS[/b] by clicking on 'Check Now' from within the Properties box of the disk in question - Windows itself would invoke '[u]CHKDSK /F[/u]' automatically.

Isn't it rather odd that Windows itself will run with the same command line that I advised, yet you must reckon that Windows is wrong too!

I suggest you get your arse on an aeroplane and present yourself to the bods at M$, for you are clearly in possession of information that the rest of the world should benefit from, and where better to correct this glaring error than at source. :)

by willcomp

chkdsk /r implies the /f switch as well, meaning that the /r switch repairs file errors as well as locating bad sectors and recovering data. As we know, the "recovered" data is usually not very usable.

by older mycroft

There isn't any good sectors left to transfer the 'recovered' data to.

I take your point about /r implying /f, but I still reckon that Windows runs an initial chkdsk with /f alone. ;)

Microsoft still uses /f as the first step in the use of Chkdsk from the command line:

http://support.microsoft.com/kb/315265

by willcomp

The /p switch is also useful and can only be used from the Recovery Console. It simply reports errors and does not repair.

by older mycroft

Nor is it infallible.

When your hard drive has reached the point of data corruption on a large scale, Chkdsk may be fighting just to find somewhere good, to put all the data it is also fighting to rescue.

You also have to understand that the more you run Chkdsk, and the more arduous these scans become, the quicker the drive will reach the point where it won't boot at all.

When you reach this point the catchphrase is "LESS IS MORE." The less you use this hard drive, the longer it is likely to remain intact. Your main concern should be to copy any existing data over to a backup facility (another hard drive) before it dies completely. Preferably by fitting and then installing your OS to a brand new hard drive, then connecting this old drive as a slave (NOT booting from it) and rescuing whatever intact data is remaining, before finally consigning this drive to silicon heaven.

by awilo2001us

I had the same problem with my computer last week, it could not load windows. When i went to recovery console the error could not be fixed.
So what i did i slaved the harddisk with errors on another computer. After booting the computer I right clicked went to properties -> Tools->Check now..->Then I checked the two options Automatically fix file system errors and Scan for and attempt recovery of bad sectors. You will be told that the drive scan will be scheduled to scan on reboot. accept and restart the computer. On reboot the drive will be scaned and the system will open windows. Shutdown the computer reomeve the slaved drive and take it back to the other cpu. it will work

This discussion is closed to new replies.