Chkdsk runs twice?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

If I tell Windows to do a chkdsk on my C drive and D drive on restart,
and then I restart my computer, it will chkdsk the D drive and then
chkdsk the C drive, and then it will restart again and then chkdsk the
D drive again before finally loading up Windows. Is it normal for it
to chkdsk the D drive twice? Is it safe to tell it to skip the second
chkdsk of the D drive?
 
If I tell Windows to do a chkdsk on my C drive and D drive on restart,
and then I restart my computer, it will chkdsk the D drive and then
chkdsk the C drive, and then it will restart again and then chkdsk the
D drive again before finally loading up Windows. Is it normal for it
to chkdsk the D drive twice? Is it safe to tell it to skip the second
chkdsk of the D drive?

Not generally normal, unless there is some message associated with the
second disk check.

If you cancel the second check it will just ask you again the next time you
boot.

There is generally no reason you can't check non system disks in windows, if
you are doing /f or /r switch you won't be able to use the drive, but it can
be a time saver.

Also there is no reason to run chkdsk /f, you can just run chkdsk and if
there are errors reported, fix them but otherwise there is no gain by
running chkdsk /f for no reason.
 
Not generally normal, unless there is some message associated with the
second disk check.

If you cancel the second check it will just ask you again the next time you
boot.

I'll see if that happens when I reboot next time then.
There is generally no reason you can't check non system disks in windows, if
you are doing /f or /r switch you won't be able to use the drive, but it can
be a time saver.

Also there is no reason to run chkdsk /f, you can just run chkdsk and if
there are errors reported, fix them but otherwise there is no gain by
running chkdsk /f for no reason.

Is it quicker to run "chkdsk" instead of "chkdsk /f"? Otherwise I'd
just run "chkdsk /f" because sometimes the chkdsk output disappears so
fast that I don't see what it says.
 
snip<


Is it quicker to run "chkdsk" instead of "chkdsk /f"? Otherwise I'd
just run "chkdsk /f" because sometimes the chkdsk output disappears so
fast that I don't see what it says.


chkdsk (no switches) is audit only

if you have problems which need to be fixed you'll have to run chkdsk /f or
chkdsk /r
 
Back
Top