Another before/after SpinRite story

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


Active member
Sep 19, 2020
Dell Latitude E7440 w/ 256GB Samsung PM851 SSD
Laptop was feeling sluggish.

ReadSpeed results:
131.3 / 173.8 / 542.9 / 542.7 / 142.6

Ran SpinRite on level 3, which took about 2 hours to complete.

New ReadSpeed results:
533.2 / 528.5 / 533.4 / 530.7 / 531.2
  • Like
Reactions: Dakar Dad
Performed a secure erase on the SSD, which (from what I understand of SSD-aware secure erase utilities) causes the drive to do a quick voltage spike that clears all cells and resets them to a blank state.

ReadSpeed now shows:
542.7 / 542.6 / 542.7 / 542.6 / 542.5

Seems to support the idea that a SpinRite level 3 can make some regions appear slower since the drive now thinks there's data in those cells. After a secure erase the drive knows the cells are empty and instead of actually reading them it just spews zeros as fast as possible on the SATA interface.
@Steve reported that you could also run a TRIM on the drive so that it becomes aware that certain regions are actually not in use. This would achieve the same goal and not wipe the drive contents.
@Lob - yep that makes sense. In this case I already imaged the contents to another drive, so I didn't care about erasing it. I wanted to do the readspeed before/after test though. :)