chkdsk /r

  • Thread starter Thread starter Pez D Spencer
  • Start date Start date
P

Pez D Spencer

wondering if anyone has ever had, or caused, more problems AFTER
running chkdsk /r in the recovery console.

just out of curiousity...
 
You don't run chkdsk without a reason. Chkdsk job is to repair the disk not save your data. If it has to throw all your data away to repair the disk it will. A repair is to meet certain integrity tests.
 
Image a car crash that you are trapped in. Chkdsk will repair the car even if it kills you while doing so. It will try not to kill you but if the only way to repair the car is to kill you it will. Chkdsk is not a rescue vehicle or an ambulance but a smash repairer. If you want to live you need to call the ambulance first before calling chkdsk.

--
 
Chkdsk will repair the car even if it kills you while doing so.

so, what you're saying is that the cure will be successful even if the
patient dies?

interesting analogy.
 
Pez said:
wondering if anyone has ever had, or caused, more problems AFTER
running chkdsk /r in the recovery console.

just out of curiousity...


chkdsk /r will repair logical errors...
that *can* destroy your operating system...
but does not necessarily destroy it either.

even if the OS itself is destroyed...
the data *could* very well be left intact...

Just as an example...All the folders could be renamed...
but with a little searching...the data might still be there.

of course...depending on how bad the file system is damaged...
the data could be left in hundreds or thousands of .chk file fragments.
 
of course...depending on how bad the file system is damaged...
the data could be left in hundreds or thousands of .chk file fragments.



does that mean that i could do a quick eyeballing of the files in the
windows folder and the program files folder to see if there are any
files with the .chk attachment? this is all hypothetical at this
point. i tried to open a file in my itunes folder which was,
apparently, an xml document...at least, that's what explorer called
it...and it brought my comp to a standstill. it was the "itunes music
library" that looks like a page with an earth surrounded by < > with
three lines under it.

i couldn't figure out what the hell was going on. i tried to end task.
all of a sudden, things weren't responding and it took forever for
task manager to open. tried to end task on the window and it just hung
and hung and hung. thought something may have been damaged, so i ran a
chkdsk /p and it said that one or more sectors were damaged (or,
whatever the exact terms were). so, i ran a chkdsk /r.

everything seems to be running just fine. i like to think that i know
what i'm doing with my xp machine, but it's probably impossible to
understand all the nuances of xp unless you run into them yourself.
i've never even had xp crash on me in the year i've had this machine,
and i like to think that it's because i know what i'm doing. but, you
could probably just about shoehorn everything i don't know about
windows into the grand canyon.

thx
 
Yes. I have learned through experience that you always do a backup before
running chkdsk. When you think about it, it only stands to reason that
chkdsk may make things worse, especially if the error was caused by a
hardware problem. Chkdsk will try to fix the file system no matter what. If
there is a hardware problem such that the data chkdsk is receiving is
corrupted then things will go downhill rapidly.
 
Pez said:
wondering if anyone has ever had, or caused, more problems AFTER
running chkdsk /r in the recovery console.

Well, if I was going to recover files, from a disk that was bad, i
think i'd clone off the dirve first before chkdsk has a chance to mark
them as bad, and thus nonreadable.
 
Back
Top