How safe is it to run CHKDSK /b on an SSD?

I have a SSD drive that is going bad. So I've run:

chkdisk /x/b d:

in an attempt to repair it by forcing the entire drive /b to be scanned, and remapped to bad-sectors to usable sectors.

The options /b and /x are described below and in this URL

/b - Use with NTFS only. Clears the list of bad clusters on the volume and rescans all allocated and free clusters for errors. /b includes the functionality of /r. Use this parameter after imaging a volume to a new hard disk drive.

/r - Locates bad sectors and recovers readable information. The disk must be locked. /r includes the functionality of /f, with the additional analysis of physical disk errors.

/x - Forces the volume to dismount first, if necessary. All open handles to the drive are invalidated. /x also includes the functionality of /f.

So the question I have is: Does the /b option cause the drive to wear out more quickly (by relocating bad sectors)?

My belief is that if the /r scan and repair bad-sectors option was used, this would be OK because only sectors that couldn't be read are moved to a new location and the bad-sector-list would be updated only if a new bad-sector were found.

But I'm not sure about the /b option.

Searching for answers

Other similar questions are listed below:

Update

In the end, running chkdisk /b did not fix the drive. The command continued to end with an error:

 Phase duration (User file recovery): 20.97 minutes.
An unspecified error occurred (75736e6a726e6c2e 500).
3 Reset to default

Know someone who can answer? Share a link to this question via email, Twitter, or Facebook.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like