• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

CHKDSK on a SSD?

Synomenon

Synomenon

Lifer
Usually when I run error checking / check-disk, I don't run it in Windows. I'll open the command prompt and type:

chkdsk c:/f/r


It will say something to the effect of, "The drive is currently in use. Schedule this drive to be checked next time the system restarts?".

Is it safe to do this on a Vertex? Is it even necessary to do this on a SSD?
 
I am not very experienced so don't take my word like I'm an expert, but I think it should be safe and I think it's normal for your system drive/partition to be in use and usually requires a restart for me. Also I think that checking your SSDs for bad sectors is just as important (if not more so) than checking a normal HDD. (Just my opinion and 2 cents)
P.S. please wait for a more experienced member to reply before you run any procedures on your SSD.
 
Last edited:
Its fine to run on the file system (/f) but AFAIK the /r switch (media scan with bad sector relocation) is completely unnecessary.
 
No, chkdsk is a filesystem integrity tests. The only thing that an SSD changes to this situation is that the chkdsk scan runs faster. And the fact that you should never have an exposed bad sector; so indeed the /r parameter would be unnecessary.

Because this is your system disk; you need to schedule chkdsk to run when Windows boots. This is because Windows doesn't have a filesystem that can fix filesystem damage on the fly (while being used/active).
 
sub.mesa said:
No, chkdsk is a filesystem integrity tests. The only thing that an SSD changes to this situation is that the chkdsk scan runs faster. And the fact that you should never have an exposed bad sector; so indeed the /r parameter would be unnecessary.
Click to expand...
Wasn't /r the switch where chkdsk wrote data to all bad sectors and then compared it afterwards to see if they were still useable? Which obviously for a SSD wouldn't work since you can't specify to which sector you write..
 
/R = check for bad sectors
/B = re-check previously flagged bad sectors whether they still are bad

Both options do not make much sense for SSDs; and can be safely omitted.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top