Main Forum > Tweaking.com Support & Help

Chkdsk

<< < (4/4)

Boggin:
A chkdsk /f will report but not "fix" any bad sectors and will most likely report that it cannot continue to run when it does come across bad sectors, because it is unable to repair corrupt files in the bad sectors.

I always run a chkdsk /f first.

If you run a chkdsk /r first and it takes "for ever", then you know it has found bad sectors.

Running a chkdsk /f first gives you the opportunity to back up your personal stuff before running the /r switch if /f reports any KBs in bad sectors - but how you choose to run it is up to you.

whiggs:
I am afraid you are mistaken sir.  Running chkdsk without any parameters (for example chkdsk C:) is the command that scans for errors, or the "read-only mode" that keeps returning incorrect information if you will.  The pictures below show the command prompt help for chkdsk, and even a snapshot from Windows AIO repair, as even shane put the command switches used for the chkdsk when you select "run chkdsk at next boot".  Try running "chkdsk /f C:" on your computer.  It will return immediately say that it can't perform the scan for fixes because the drive is locked.  Not soon after, immediately after.  Its not scanning the drive for errors to report them, its trying to scan the drive for errors to FIX them, but cannot because it is being used.

Boggin:
I think we are talking at cross purposes here.

You are talking about running a chkdsk from within the program or from the WRE.

I'll run a chkdsk /f in normal mode and yes, the volume has to be dismounted first because it cannot be checked whilst in use and is why a reboot is required for it to take place before Windows is loaded.

In the WRE it doesn't have to be because you are already outside of Windows - I have also run it in that mode, but I'll still run it with the /f switch first.

Navigation

[0] Message Index

[*] Previous page