6 ms·
Uh... is one broken drive such a big issue? Hardware will fail, usually when it is very new or very old (Bathtub curve). Or are there more such events the artic
by bad_alloc 3y ago
Uh... is one broken drive such a big issue? Hardware will fail, usually when it is very new or very old (Bathtub curve). Or are there more such events the article didn't mention?
- momirlan 3y agoyes there are, and they mention an Ars Technica story, as well as reddit users complaining. I lost 1TB on such a SSD I hardly used.
- RadixDLT 3y agonew drives should never crash or lose data, also WD and SanDisk lie through their teeth, there is no integrity.
- worthless-trash 3y ago> new drives should never crash or lose data, In your small sample size maybe.
- JonChesterfield 3y agoIt'll be true for sufficiently short periods of time, or for ages if you never put any data on it. About 1/4 of hard drives I buy die in the first 24 hours since I unsportingly run badblocks on them to see whether they're on the start of the failure curve.
- worthless-trash 3y agoOh wow, that is -bad-. I'm usually being 10-12 and i think i've only had one or two over the last 5 years.
- PrayagBhakar 3y agoWhat do you mean you run badblocks? Can you talk more about your drive testing process?
- JonChesterfield 3y agobadblocks has a destructive write mode. It writes numbers to disk then reads them back a while later and tells you if they differ. That seems to work hard drives fairly hard - they warm up at least. A day is usually how long my patience lasts. There are probably better stress test approaches out there. The basic idea is to find out if your drive is one that'll die early before putting a load of data you want to keep on it. I don't do this to ssd as they have lowish write limits anyway, so I just assume any data written to a ssd will vanish at some point. Hard drives in a network share, ssd in dev machines treated as scratch storage.
- nfriedly 3y agoNot the person you asked, but I do something similar. This is the guide I like to follow for new drives: https://www.truenas.com/community/resources/hard-drive-burn-in-testing.92/ https://www.truenas.com/community/resources/hard-drive-burn-... It's on the TrueNAS forum, but it'll work on basically any Linux system. I'm currently using Unraid, which is based on Slackware. (I must be luckier than the parent, because I've only had a single drive in a dozen or more die during testing - and that was a used one off ebay!)
- gochi 3y agoYes, here are the linked articles indicating it's a WD issue and they're continuing to push this product with sales: https://www.theverge.com/2023/5/22/23733267/sandisk-extreme-pro-failure-ssd-firmware https://www.theverge.com/2023/5/22/23733267/sandisk-extreme-... https://arstechnica.com/gadgets/2023/05/sandisk-extreme-ssds-keep-abruptly-failing-firmware-fix-for-only-some-promised/ https://arstechnica.com/gadgets/2023/05/sandisk-extreme-ssds...
- MR4D 3y agoIf you read the article, the first paragraph explains that this was the replacement drive that WD sent him when his previous one failed. So it’s at least 2 drives in a row in a short period of time. Statistically that will happen, but it’s like gambling - if you win too much you get shot.
- bcrl 3y agoWhich points to a firmware bug in the SSD that the use-case managed to trigger repeatedly. Firmware bugs were around in abundance when performant SSDs first came to market more than a decade ago, and while manufacturers have gotten better at testing SSD firmware, it is still inevitable that bugs will occasionally make it into shipping hardware. Moral of the story: don't trust your valued data to any one storage device. I've tried to use drives from different vendors in RAID 1 mirrors to minimize exposure to firmware bugs, and I've still seen SSDs die at unexpected times in the last few years.