Samsung PM830 SSD

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


Well-known member
Dec 26, 2020
I got some interesting results from an old SSD I bought as part of an eBay lot a while back. I ran these tests in an old HP DM1Z laptop (AMD E-350 CPU). I used ReadSpeed release 1.

Run #1 shows some lower than expected numbers (compared to a new drive), and inconsistency between regions.
Run #2 is after I ran SpinRite 6.0 at level 2. I see no difference, except at the 75% region, where there is a notable improvement. SpinRite fixed an area that had dropped down to ~100 MB/s (visible in the 75% region of DM1Z-1-1.TXT).
Run #3 is after a secure erase. The numbers look great here.
Run #4 is after using Nwipe (Parted Magic) to write random data to the entire drive (no blanking pass). I'm surprised that this undid the improvement I saw in the 3rd run.


I have attached the log files for each run. -0 is a normal run with no parameters other than the filename, and -1 is a run that includes /1. The -1 runs were performed immediately after the -0 runs. The timestamps are wrong because I had to pull the battery to install the drive.


  • DM1Z-1-0.TXT
    790 bytes · Views: 307
  • DM1Z-1-1.TXT
    5.9 KB · Views: 306
  • DM1Z-2-0.TXT
    790 bytes · Views: 323
  • DM1Z-2-1.TXT
    5.9 KB · Views: 322
  • DM1Z-3-0.TXT
    790 bytes · Views: 304
  • DM1Z-3-1.TXT
    5.9 KB · Views: 308
  • DM1Z-4-0.TXT
    790 bytes · Views: 308
  • DM1Z-4-1.TXT
    5.9 KB · Views: 303
Last edited:
So a secure erase on a SSD with the proper tool, will simply apply enough power to zap all the cells at once. It would also erase any internal tracking. Perhaps the firmware in this drive responds with a "magical" empty sector when prompted to read something it knows is blank (i.e. it is about as fast as the firmware and interface to the CPU will allow.) There is a lot of magic in SSD firmware that is unknown and will lead to situations that seem odd but would probably make sense if we actually knew the inner workings.
  • Like
Reactions: PHoganDive