chkdsk continues to find errors

[Guest Juerg Reimann]

I ran into a mystery with chkdsk that I could verify with a dozen

different Windows XP systems. Chkdsk seems to always find some errors on

the C: drive that need to be fixed with the /F switch while rebooting.

During the reboot chkdsk usually finds nothing but as soon as the system

is up and chkdsk is run against die C: drive again, the game starts from

new.

 

I bet if someone tries this on a system with all the recent updates, it

will result in the same. But I know it used not to be so, usually if

chkdsk would find errors, after repair it should report a clean file

system.

 

Does anybody know why chkdsk all over sudden behaves like this?

 

Thanks, Juerg

[Guest nass]

RE: chkdsk continues to find errors

 

 

 

"Juerg Reimann" wrote:

> I ran into a mystery with chkdsk that I could verify with a dozen

> different Windows XP systems. Chkdsk seems to always find some errors on

> the C: drive that need to be fixed with the /F switch while rebooting.

> During the reboot chkdsk usually finds nothing but as soon as the system

> is up and chkdsk is run against die C: drive again, the game starts from

> new.

>

> I bet if someone tries this on a system with all the recent updates, it

> will result in the same. But I know it used not to be so, usually if

> chkdsk would find errors, after repair it should report a clean file

> system.

>

> Does anybody know why chkdsk all over sudden behaves like this?

>

> Thanks, Juerg

 

Try it with chkdsk /R

Also note that there are some Bad sector beyond SFC to repair or mark as

bad! If the HDD on its last legg.

HTH,

nass

---

http://www.nasstec.co.uk

[Guest Larry(LJL269)]

Re: chkdsk continues to find errors

 

Me 2! Ran chkdsk 4 times in-a-row with fix option & now it's gone.

PM's check disk on boot & BartPE chkdsk never did find anything.

 

Buy 1 of those copper bracelets from my cousin Vinny :)

 

Hope that helps. Larry

 

On Wed, 15 Oct 2008 14:23:36 +0200, "Juerg Reimann" <jr@jworld.ch>

wrote:

>I ran into a mystery with chkdsk that I could verify with a dozen

>different Windows XP systems. Chkdsk seems to always find some errors on

>the C: drive that need to be fixed with the /F switch while rebooting.

>During the reboot chkdsk usually finds nothing but as soon as the system

>is up and chkdsk is run against die C: drive again, the game starts from

>new.

>

>I bet if someone tries this on a system with all the recent updates, it

>will result in the same. But I know it used not to be so, usually if

>chkdsk would find errors, after repair it should report a clean file

>system.

>

>Does anybody know why chkdsk all over sudden behaves like this?

>

>Thanks, Juerg

 

----------------------------------------------------------------------

 

A working unsecure OS is infinitely better than non-working secure OS.

Just spent 1 week cleaning up the mess WUpdate made preventing

hypothetical security problems. http://microscum.com/comsense/

[Guest philo]

Re: chkdsk continues to find errors

 

 

"Juerg Reimann" <jr@jworld.ch> wrote in message

news:4A2355AAB6A344A981A38D3A8633227C@jworld.local...

> I ran into a mystery with chkdsk that I could verify with a dozen

> different Windows XP systems. Chkdsk seems to always find some errors on

> the C: drive that need to be fixed with the /F switch while rebooting.

> During the reboot chkdsk usually finds nothing but as soon as the system

> is up and chkdsk is run against die C: drive again, the game starts from

> new.

>

> I bet if someone tries this on a system with all the recent updates, it

> will result in the same. But I know it used not to be so, usually if

> chkdsk would find errors, after repair it should report a clean file

> system.

>

> Does anybody know why chkdsk all over sudden behaves like this?

>

> Thanks, Juerg

>

 

 

I've found that I often see errors when running chkdsk

on a "live" system as there are files in use and the drive is dynamically

changing.

 

As long as there are no errors while actually running chkdsk /f

you are probably OK

 

However, as a precaution, you should run the harddrive mfg's diagnostic