- If it's a single drive situation and reliability is very important, something aimed at "enterprise" tends to be a good bet. More firmware testing, more over provisioning, and so on. And if nothing else there tends to be less BS around getting warranty coverage honored. Also costs significantly more. Micron, Intel D3s etc.
- If it's multi-drive, don't focus on finding the one best brand, use ones from different major brands with redundancy. The goal isn't to try to ensure no drive failures, but rather lower the risk of correlated drive failures so that when they happen the system has time to restore redundancy and there's no issue.
- If it's single drive and some down time is acceptable for cost then just roll the dice, though even there I'd stay away from QLC and the ultra mega bargain basement stuff.
In all cases buy from somewhere reputable that actually sells drives directly, like B&H or CDW or the like. If you buy from Amazon beware of counterfeits and also "new" stuff that is heavily used. Always check SMART stats right away and make sure drive lifetime is where you expect (not hundreds/thousands of hours on something "new"). And of course, always have good backups and/or some way to rapidly bring stuff back up.
Same basic idea as SMR hard drives: the savings are too minor to be worth the asterisks. If you're running at megascale and can afford to customize your workloads, software, OS, and firmware, around it and at scale the ROI crunches out as worth it that's fine of course. But at the individual or even SMB level? Nah. Like, taking Samsung as a fairly large, decent brand example, their 4TB TLC EVO drive is ~$220 right now, whereas their 4TB QLC QVO is... $200. Heck for whatever reason their 1TB at B&H costs (a very little) more, $65 for the QVO, while the EVO is $60. Is $5-20 over terabytes and years worth the slightest hassle or weirdness? QLC is IMO essentially a scam at the consumer level, dramatically impacting reliability/flexibility/performance consistency for really minimal cost savings.
>Does it not have its place in high-read low-write consumer workloads, such as software or media libraries?
Frankly no. I mean, putting aside whether SSDs themselves make sense in such an application at all vs spinning rust (same money will buy you a nice 14TB hard drive), but to the extent they do I still think the above holds. QLC is just physically fundamentally sketchier tech. And how sure are you (and how much trouble do you want to go through) about what your workload will be like long term? If you put the money/time investing into getting together a decent little SSD NAS with a bunch of terabytes, and then a year or two down the road want to have some VMs on it too, or have a fileshare and then it gets hit harder than you expected, or there's some bug that causes some write amplification, and then your QLC drives end up hosed was that really worth a few cups of coffee?
Maybe so! SMR really is worth it to a few places as well. Or ZFS dedup for a software example (with hardware implications). But all of this for me falls under the heading of "if you don't have a specific reason for it, don't".
But I think to a certain extent it's a bit of a crapshoot as to whether you're hitting a manufacturer while they have an undiscovered issue.
I bought a whole series of Samsung drives in both NVME and SATA and they've all been perfect but this just all happened to be before their more recent issues. Before that I bought a bunch of Intels that all died in annoying ways (I believe they turned out to have a pretty bad write amplification bug tied to their power saving behavior).
Our buying cycle a couple years ago we ended up with some "Toshiba THNSN81Q92CSE 1.92TB SATA eSSD" in two systems, and ran into some severe performance issues, system IO wait time going through the roof. Ended up spending significant time with Dell support, them identifying a couple drives in each box to replace, and also doing full "RAID chain" replacements (controller, cabling, backplane). All of the replacement drives we've gotten have been Intel 1.92TB, so maybe Dell is seeing problems with Toshiba? Since then the systems have been solid, so maybe it was part of the RAID chain.
Aside: Decades ago, right when Intel was coming out with their SSDs, I had a consulting client that was a Rural ISP. Their NFS server was on 8x 10K WD hard drives in RAID-10. The continually struggled with performance, and we kept tuning, but would regularly just outrun the IOPS, mostly with e-mail access. A friend of mine happened to have a 600GB Intel SSD production sample, so I asked if I could borrow it for a few weeks. Sent this laptop SSD that would fit in the palm of my hand out to this client, had them hook it up to the NFS server, and then did "pvmove" from the RAID array over to the laptop drive. Steadily, over the next few hours, the performance issues were gone. It was pretty fantastic to see an 8 drive RAID array bested by a laptop form factor drive.
For SATA though... we have several Crucial MX500s 1TB that are approaching 2PB written, and none have failed. It's a shame this didn't transfer to their NVMe SSDs- they are all pretty harsh underperformers (though none broke).
Nobody’s perfect.
> openSeaChest is a collection of comprehensive, easy-to-use command line diagnostic tools and programming libraries for storage devices that help you quickly determine the health and status of your storage product. The collection includes several tests that show device information, properties and settings. It includes several tests which may modify the storage product such as power management features or firmware download. It includes various commands to examine the physical media on your storage device. Close to 200 commands and sub-commands are available in the various openSeaChest utilities. These are described in more detail below.
I also recommend reading the Arch Linux wiki [2].
I'd also have a look at the Linux kernel quirks [3][4].
[1]: https://github.com/Seagate/openSeaChest
[2]: https://wiki.archlinux.org/title/Solid_state_drive/NVMe#Firm...
[3]: https://www.kernel.org/doc/html/latest/nvme/feature-and-quir...
[4]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...