Main Forum > Tweaking.com Support & Help

Chkdsk

<< < (3/4) > >>

whiggs:
scroll down until you see "option two".  The picture right above that.  So it would be everything under "option one" on the page at that link.  And the fact that it is outside of Widows is the whole point for doing this.  Windows can't be writing files to the disk when it is not running, right?

Boggin:
That's why when you do it in normal mode with a parameter, it requires a reboot before it runs.

whiggs:
What I think the orginal poster is trying to determine (I apologize if I misunderstood by the way) is if chkdsk is actually repairing anything.  During the boot time scan, there is no indication if chkdsk is finding anything wrong, repairing it, not repairing it, it tells you nothing.  I think he was looking for some validation that "there is nothing wrong with my HD", as I have sought the same thing which is why I do the scans in this way.

Boggin:
Shane has a Stickie about running chkdsk in read-only mode because it can give false errors - I'm not sure why it is included as such in the program, but prior to running WR, it's best to run either a chkdsk /f or /r to see if it reports any bad sectors because when the program writes to the disk, if it writes to bad sectors then problems will occur after the reboot.

http://www.tweaking.com/forums/index.php/topic,2546.0.html

whiggs:
I'm not sure what you mean by that.  All running chkdsk /f is going to tell you is that the drive is locked and can't be scanned until you restart.  That doesn't tell you if there are any bad sectors or not.  Plus, the Windows recovery environment, at its core, is a extremely slimmed down version of the same os.  If you run chkdsk from it, it will find and repair the same corruptions that the version on the full os would.

Navigation

[0] Message Index

[#] Next page

[*] Previous page