ReadSpeed before/after SpinRite ran

  • SpinRite v6.1 is Released!
    Guest:
    That's right. SpinRite v6.1 is finished and released. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in:

    This forum does not automatically send notices of new content. So if, for example, you would like to be notified by mail when Steve posts an update to his blog (or of any other specific activity anywhere else), you need to tell the system what to “Watch” for you. Please checkout the “Tips & Tricks” page for details about that... and other tips!

    /Steve.
  • Announcing “BootAble” – GRC's New Boot-Testing Freeware
    Please see the BootAble page at GRC for the whole story.
  • 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.)


dale

New member
Dec 28, 2020
3
2
Hi,
This WD 500GB Blue SSD was purchased 18 months ago and installed in a 9 year old computer that served mainly,
until recently as a PLEX server, which probably accounts for the low speed in region 0.


Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  500GB WDC  WDS500G2B0A-00SM50        17.9   349.3   544.7   544.7   541.4

                  Benchmarked: Monday, 2020-12-28 at 16:19



After running SpinRite:


Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  500GB WDC  WDS500G2B0A-00SM50       326.5   532.7   531.6   531.3   534.5

                  Benchmarked: Wednesday, 2020-12-30 at 13:06


Nice!! Way to go Steve!!

Dale
 
@dale That's very interesting. What level did you run SpinRite on? It's very interesting that an SSD would show this difference in read speed across the different blocks of the drive after you fixed it.

@Steve Is it true that the drive will only refresh the sectors or reallocate sectors on a write, not a read? Does that mean that running SpinRite on level 2 would NOT rejuvenate the drive? Does it also mean that running a full AV scan, which would read the whole drive, would NOT rejuvenate the drive?

Ron
 
@rfrazier : I believe that's all correct. A read-only pass might teach the drive something about itself, but Intel's Allyn Malventano who's their storage guy stated that unlike HDDs, SSDs will not write their own media unless written to. I don't fully understand what's going on, since a barely readable block should, it seems to me, upset the SSD and cause it to consider that block for reassignment.
 
@rfrazier I ran it on Level 3. I had heard Steve mention on Security Now!, that was the level to use on SSD's.

FYI - I have never used level 3 before in 14 years of owning SpinRite. I new it was there but I had to find it.
 
@dale I've never used Level 3 either until recently with these ReadSpeed tests. However, I do a Level 4 when I get a new drive to burn it in. Maybe I'll do a Level 3 once every year or two or when ReadSpeed starts looking odd. I googled the data sheet for your drive. It appears to be rated at 600 TBW (TeraBytes written). So, doing a full write on a .5 TB drive uses up 1/1200 of it's life, less than .1%. Not too bad a penalty to pay for refurbishing it. If you're interested, I posted more info on drive endurance on the following thread.


May your bits be stable and your interfaces be fast. :cool: Ron
 
@rfrazier : I believe that's all correct. A read-only pass might teach the drive something about itself, but Intel's Allyn Malventano who's their storage guy stated that unlike HDDs, SSDs will not write their own media unless written to. I don't fully understand what's going on, since a barely readable block should, it seems to me, upset the SSD and cause it to consider that block for reassignment.

But SDD's rewrite all the time. ISTM most definitely the SSD has been doing some reallocation here, except it may not be the reallocation we normally refer to (grown defects table). On a spinner, if we discard SMR drives, the only type of reallocation we know is bad sector reallocation which is basically nothing else than editing a table which translates LBA whatever to an actual sector (the spare).

SSD drives are managed of course using one big translation table all the time, there's no relation between LBA and actual blocks other than in a translation table. So what I suspect happens is that indeed the drive reallocated blocks, just not to a grown defect list. A block that is harder to read is not bad by definition, the data may just have been sitting for a while and bit errors creeped in (though still recoverable using RR to compensate for drift and/or ECC). Drive can simply store data in different blocks and queue original blocks for garbage collector. So next time ReadSpeed runs, blocks can be read without having to wait for error correction.

The drive only needs to add original blocks to a grown defect list if garbage collector routines fail to erase these blocks.
 
Last edited:
In the podcast yesterday (which I just listened to today) @Steve suggested I try some things after my post last week.

So, this first run of RS.exe was on the same machine which had been turned off for several days. Maybe that's why region 0 improved a little bit. The machine was cold, if that makes a difference.

Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  500GB WDC  WDS500G2B0A-00SM50       447.7   529.4   531.2   531.0   531.9

                  Benchmarked: Wednesday, 2021-01-06 at 19:59


The next one was done after a SpinRite level 2

Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  500GB WDC  WDS500G2B0A-00SM50       534.9   533.4   532.8   532.3   532.3

                  Benchmarked: Wednesday, 2021-01-06 at 20:59

This last one was run after @Steve suggested a TRIM command be used in Windows10.
Here is the command listed in the show notes yesterday:

“Optimize-Volume -DriveLetter C: -ReTrim -Verbose”

Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  500GB WDC  WDS500G2B0A-00SM50       528.8   542.3   544.7   544.7   537.8

                  Benchmarked: Wednesday, 2021-01-06 at 21:18

Looks like the TRIM command did the job.

Regards, Dale
 
  • Like
Reactions: Steve
Thanks for following up!

We're seeing some impressive results from level 2 Spinrite passes, and this adds to them!

Weird that the 0% spot was down after TRIM?
 
In the podcast yesterday (which I just listened to today) @Steve suggested I try some things after my post last week.

So, this first run of RS.exe was on the same machine which had been turned off for several days. Maybe that's why region 0 improved a little bit. The machine was cold, if that makes a difference.

Code:
  +--------------------------------------------------------------------------+
  | ReadSpeed: Hyper-accurate mass storage read-performance benchmark. rel 1 |
  |  Benchmarked values are in megabytes read per second at five locations.  |
  +--------------------------------------------------------------------------+

Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
81  500GB WDC  WDS500G2B0A-00SM50       447.7   529.4   531.2   531.0   531.9

                  Benchmarked: Wednesday, 2021-01-06 at 19:59
-----------------------------------------------------------------------------
   See the ReadSpeed forums at forums.grc.com for help and community support.


The next one was done after a SpinRite level 2

Code:
  +--------------------------------------------------------------------------+
  | ReadSpeed: Hyper-accurate mass storage read-performance benchmark. rel 1 |
  |  Benchmarked values are in megabytes read per second at five locations.  |
  +--------------------------------------------------------------------------+

Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
81  500GB WDC  WDS500G2B0A-00SM50       534.9   533.4   532.8   532.3   532.3

                  Benchmarked: Wednesday, 2021-01-06 at 20:59
-----------------------------------------------------------------------------
   See the ReadSpeed forums at forums.grc.com for help and community support.

This last one was run after @Steve suggested a TRIM command be used in Windows10.
Here is the command listed in the show notes yesterday:

“Optimize-Volume -DriveLetter C: -ReTrim -Verbose”

Code:
  +--------------------------------------------------------------------------+
  | ReadSpeed: Hyper-accurate mass storage read-performance benchmark. rel 1 |
  |  Benchmarked values are in megabytes read per second at five locations.  |
  +--------------------------------------------------------------------------+

Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
81  500GB WDC  WDS500G2B0A-00SM50       528.8   542.3   544.7   544.7   537.8

                  Benchmarked: Wednesday, 2021-01-06 at 21:18
-----------------------------------------------------------------------------
   See the ReadSpeed forums at forums.grc.com for help and community support.

Looks like the TRIM command did the job.

Regards, Dale
How full is the drive, how much data on it approximately? Just wondering if we see TRIM effect there where memory isn't even actually read because known to be empty? Again very cool to see level 2 has some effect.