Running RS twice on same drive amlost 57% faster??

  • SpinRite v6.1 Release #3
    Guest:
    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.
    /Steve.
  • 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!

    /Steve.
  • 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.)

orion2921

New member
Jan 9, 2021
3
0
Not sure whats going on behind the curtains here. Just ran back to back runs on the same drive the speed increase a good deal.

Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  2.0TB WDC WDS200T2B0B               275.9   525.3   534.3   541.5   536.8

                  Benchmarked: Saturday, 2021-01-09 at 16:14

Code:
  AHCI '.' and IDE '-' drive reset & diagnostic latencies in milliseconds:

  61.607

  Associating BIOS drive [80-81]:

  [ 80 81! ]

  BIOS drive count: 2

  BIOS Inter Bus Location Dev Port Intr
  ---- ----- --- -------- --- ---- ----
   80   USB  PCI  0:29:0  17                                                 

  BIOS Location Type Clas Pg Vend Devi Prt Intr Cmmd Ctrl Mast Driv Link Size
  ---- -------- ---- ---- -- ---- ---- --- ---- ---- ---- ---- ---- ---- -----
   81   0:17:4  AHCI 0106 01 8086 8D62  1   11  < AHCI Cntrl >  6.0  6.0 2.0TB

BIOS Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  2.0TB WDC WDS200T2B0B               475.7   538.1   541.8   541.9   539.3

                  Benchmarked: Saturday, 2021-01-09 at 16:15
 
Not sure whats going on behind the curtains here. Just ran back to back runs on the same drive the speed increase a good deal.
Yes, we've seen this often and your question is a good one. I'm not sure that we even have a theory about it. =I= would be inclined to suggest that if a readback of a very troubled sector "frightened" the SSD controller, it might have recovered the data then swapped it into a new location, thus "healing" the drive for the second and future passes. But it's unknown whether SSD controllers will do that on the fly.
 
  • Like
Reactions: lovecakeboy
Suspected this SSD was having issues for some time now. Crazy a speed test would wake it up, least in that spot. Thanks Steve!