Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: chkdsk /r

0 views
Skip to first unread message
Message has been deleted

David Candy

unread,
Apr 15, 2006, 6:39:31 PM4/15/06
to
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.

--
--------------------------------------------------------------------------------------------------
How to lose a war in Iraq
http://webdiary.com.au/cms/?q=node/1335#comment-48641
=================================================
"Pez D Spencer" <colec...@gmail.com> wrote in message news:1145140026.1...@v46g2000cwv.googlegroups.com...
> wondering if anyone has ever had, or caused, more problems AFTER
> running chkdsk /r in the recovery console.
>
> just out of curiousity...
>

David Candy

unread,
Apr 15, 2006, 6:50:57 PM4/15/06
to
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.

--
--------------------------------------------------------------------------------------------------
How to lose a war in Iraq
http://webdiary.com.au/cms/?q=node/1335#comment-48641
=================================================

"David Candy" <.> wrote in message news:%23Xlm41N...@TK2MSFTNGP05.phx.gbl...

Message has been deleted

philo

unread,
Apr 15, 2006, 7:05:15 PM4/15/06
to
Pez D Spencer wrote:
> 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.

Message has been deleted

Kerry Brown

unread,
Apr 15, 2006, 8:38:27 PM4/15/06
to
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.

--
Kerry
MS-MVP Windows - Shell/User

pau...@efn.org

unread,
Apr 15, 2006, 10:57:02 PM4/15/06
to

Pez D Spencer wrote:
> 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.

Steve N.

unread,
Apr 16, 2006, 10:14:08 AM4/16/06
to
Pez D Spencer wrote:

>>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.
>

David is an interesting person. :)

Steve N.

0 new messages