Old Samsung PB22-JS3 rejuvenated

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

jonny

New member
Sep 17, 2020
1
1
Just wanted to share my findings of a drive that haven't been written to in several years.

First run:
Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  128GB SAMSUNG SSD PB22-JS3 2.5"     126.6    65.4    52.5    84.0    62.2

                  Benchmarked: Friday, 2021-01-08 at 10:28

The drive don't support TRIM, at least that's what blkdiscard told me, so I instead wrote random data to the entire drive:
# dd if=/dev/urandom of=/dev/sda bs=1M
(write speed was very consistent at about 54.7 MB/s, which is probably due to urandom not being faster)

Second run:
Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  128GB SAMSUNG SSD PB22-JS3 2.5"     230.7   229.5   230.7   230.3   229.0

                  Benchmarked: Friday, 2021-01-08 at 10:53
:cool:

/Jonny
 
Last edited:
  • Like
Reactions: rfrazier
Hi, welcome to the forums, and thanks for posting!

Interesting results! I guess that you're doing the equivalent of a Spinrite level 3 pass, except that your version is destructive of data? It's useful to see that it has similar results to level 3 in terms of refreshing the read speeds?