SSDs by Kingston, Samsung, HP: three computers in one post

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

Aldo

Member
Sep 18, 2020
14
4
Code:
Drv Size  Drive Identity  Location:    0      25%     50%     75%     100
--- ----- ------------------------- ------- ------- ------- ------- -------
8a 240GB KINGSTON SA400S37240G       45.8   257.6    48.6    75.0    15.9
8b 500GB Samsung SSD 860 EVO 500GB  273.9   273.9   273.9   274.0   274.0
8c 120GB HP SSD S700 120GB          533.4   543.9   543.9   541.2   543.8
Backgrounders

The 240 has been the only drive in a Win8.0 system for four and a quarter years. It was an in-warranty replacement for an identical SSD that lasted only six months in 2015. This one was driven hard by its first user, but has slowed down only for its second user. Looks like it's time to run Kingston SSD Manager, maybe update the firmware and oh yeah - make backups!

The 500 is two and a quarter years old, stuck in a SATA-2 laptop.

The 120 was on clearance for $20 six months ago. It is a boot+system drive for Win8.1, with non-Win data folders stored on spinning drives. Very snappy :)
 
Code:
Drv Size  Drive Identity  Location:    0      25%     50%     75%     100
--- ----- ------------------------- ------- ------- ------- ------- -------
 8d 500GB HP SSD S700 500GB          543.9   543.9   543.9   543.9   543.9
Update

Kingston SSD Manager 1.1.2.6 reports the 240 has used up 97 percent of its lifespan, so the HP 500 was purchased today on special for $56 as a trickle-down replacement. The 120 will be cloned onto the new 500, and the Windows partition will be enlarged in the process. It turns out that 16 GB is much too small for a Win8.1 system disk trying to host various development and media editing packages. Then the 240 will be cleaned up from 47 percent full and cloned onto the 120, which may end up around 90 percent full. In case the dying 240 is too far gone, the 120 can take a shrunken clone of the 240GB partition on the Samsung 500. Finally the 240 can be sacrificed to the deities of firmware upgrades, just to see what the heck happens. Maybe it will stay useful as a rarely-written long-term backup medium. Notice all this is happening just as the annual backups should be encrypted and stored offsite.
 
@Aldo : If you can, keep the "nearly used up" Kingston around. It would be super-interesting to see whether a future SpinRite will be able to bring some like back to it! ... and/or restore its performance. There's some reason to believe that it might be able to.