#Samsung pcie ssd disk health tools pro#
#Samsung pcie ssd disk health tools software#

Many choose to sell out and simply echo the approved selling points they receive directly from the company, but not every outlet does this and it shouldn't be held up as something that tech journalists should aspire (or be allowed) to do. Informing potential customers about extremely serious flaws in the product is quite literally their job - at least if they wish to have any semblance of integrity, trustworthiness, and respect. > And the manufacturer that sent you the review sample definitely doesn't want to see (focus on edge case negative). I disagree and I think most consumers would be extremely interested in durability of their storage devices, especially since most of them rely on it in the absence of backups. > Have very little real life consumer relevance.

Either way you gain reputation for being a trustworthy outlet that people can rely on for accurate information. What's boring about that? This is extremely valuable information for any perspective buyer. > That's a lot of time investment to get result that are boring AF ('we tested them. > In a world where hardware news drops simultaneous by multiple outlets literally within minutes of news embargoes being lifted.Īny outlet interested in journalism rather purely PR can purchase a retail sample on release and publish an endurance report at a later date, however long it takes.įrom my experience people buy storage whenever they have a need for something faster or larger, unlike CPUs and GPUs which have peak interest around their release dates. I also got uncorrectable read errors when evacuating data from the devices. Less than 4 months in service and 10 TB written. As you can see from the smart log they're barely used.

However I replaced them in a hurry because I no longer trust Samsung SSDs.

#Samsung pcie ssd disk health tools software#

Due to running them in RAID 1 I caught the issue early and I had no data loss or downtime because the Linux software raid compensated for the bad hardware. He also had a 870 EVO, issued a dd if=/dev/sdX of=/dev/null bs=8M and guess what, he got uncorrectable read errors. In 2021 I told a friend of mine about the issue.

I no longer use Samsung SSDs and replaced them them with SSDSC2KB076T8, Micron SSDs and KC3000 Kingston NVMes. During the raid check Debian reads all data from both devices. The pattern is always the same: I have them configured in a raid 1. All devices failed within 6 months on barely used systems.

#Samsung pcie ssd disk health tools pro#

In 2021 I bought at least ten 870 EVO 4 TB SATA and six 980 Pro 2 TB NVMe.