6 ms·
"When a HD died early, you could also imagine undetected manufacturing flaws that finally gave way. With SSDs, at least in theory that shouldn't happen" Why sh
by Waterluvian 8y ago
"When a HD died early, you could also imagine undetected manufacturing flaws that finally gave way. With SSDs, at least in theory that shouldn't happen"
Why shouldn't it? Isn't it just hardware too?
"With spinning HDs, drives might die abruptly but you could at least construct narratives about what could have happened to do that"
Why can't you do the same with SSDs?
It feels like the author's main complaint is the frustration of not understanding SSD hardware as well.
Is this a valid complaint? Are SSDs magical in some way? I'm not an expert but... It's just hardware with pieces that do stuff. Why can't we come up with an understanding of why it fails?
- gpvos 8y ago> Why can't we come up with an understanding of why it fails? Indeed, that is the question that the article's author seems to be asking.
- Severian 8y agoWell, considering it's the cheapest consumer SSD they could afford, and then connecting it to a SAS port might be a whole story in itself.
- NikolaeVarius 8y agoWell to be fair, there is an entire layer of abstraction at the SSD controller level that does tons of black box magic. It allows the OS to treat the SSD as another other storage device without letting the OS know what is going on. So the combination of non-moving parts (making it hard/impossible to debug via physical inspection) combined with a tons of wear leveling/misc magic can defo make it seem like SSD's are magical.
- hanikesn 8y agoThe exact same thing happens hard drives. There's a ton of magic going on.
- NikolaeVarius 8y agoLots of extra magic happens in an SSD though https://www.youtube.com/watch?v=C5JoC4-qsO0 https://www.youtube.com/watch?v=C5JoC4-qsO0 https://www.forensicswiki.org/wiki/Solid_State_Drive_(SSD)_Forensics https://www.forensicswiki.org/wiki/Solid_State_Drive_(SSD)_F...
- relieferator 8y agoThanks for this youtube link. In the case of recovering deleted files from SSD's that have the trim command enabled (Forensics Writeblocker was used,) the following drives have a low probability of recoverability: Crucial, Intel, and Samsung (3core controller). Whereas Seagate, Supertalent (parallel ATA to SATA bridge chip,) OCZ, and Patriot; files could be recovered. If the drive is quick-formatted, and if trim is enabled, the data is completely gone on the following drives: Crucial, Intel and Samsung. The trim state impacts the most whether or not the data can be recovered. You can check if trim is enabled with the command: fsutil behavior query DisableDeleteNotify - if your result is 0, it is enabled (default).
- gpvos 8y agoYes, but most technical people seem to have a mental model that explains most failures pretty well. Not so for SSDs, apparently.
- Wowfunhappy 8y agoIs there a good reason why we use separate SSD controllers instead of letting the primary cpu handle it? The obvious reason is backwards compatibility, but as more of computing moves to SSDs, is this still relevant? ZFS has shown that removing layers of abstraction with regard to storage can be beneficial.
- pixl97 8y agohttps://azure.microsoft.com/en-us/blog/project-denali-to-define-flexible-ssds-for-cloud-scale-applications/ https://azure.microsoft.com/en-us/blog/project-denali-to-def...
- pjc50 8y agoThat adds a round of latency, and makes it pretty much impossible to boot off the drive. The blocks aren't in the same order in the Flash as they are presented by its interface, and one of the main jobs of the controller is to re-order them. It would be an interesting product to have, a raw block API to a Flash device with all the temporary state stored on the host - but a hard one to sell, as it's not differentiated in any way.
- blattimwind 8y agoThere are host-managed SMR drives, which share a number of characteristics with flash storage.
- selectodude 8y agoApple uses their T2 security enclave as the SSD controller and it's caused quite a stir.
- joosters 8y agoI wonder if you can read any extra state out of the T2 as a result, e.g. more information on wear leveling, temporary read failures and so on, more than the standard SMART counters?
- ars 8y ago> Why can't you do the same with SSDs? Because they don't die incrementally. Wtih a hard disk you'll get bad sectors, growing slowly over time. Or a head crash and then it's all dead. What could cause an entire SSD to die at once? I would totally understand bad sectors, but the whole thing at once? Where it doesn't even try to read existing data?
- marcosdumay 8y ago> What could cause an entire SSD to die at once? SSD has a problem in that almost every failure case looks more like a head-scratch than a bad sector. Even the most local problem that is excessive writing on a sector can take the entire chip down.
- jclulow 8y agoOne potential cause is poorly constructed drive firmware which fails to account for a minor failure of some kind and crashes. If that unaccounted minor failure is persistent, the firmware may crash constantly and then you'd be unable to access even theoretically good parts of the drive. Firmware -- undebuggable, unobservable, unfixable software, jammed into your devices -- is the enemy.
- jug 8y agoSounds like there is a business opportunist here for open firmware or even one running on the CPU especially for the enterprise? But maybe they won’t bother either despite valuable data and uptime, and just rather throw more redundant SSD’s at the problem.
- someguydave 8y agoYou would need to convince the very small number of Flash memory fabricators to release their detailed specifications and known product weaknesses.
- ryanmercer 8y ago>What could cause an entire SSD to die at once? A component failing? Electrical components fail. Sometimes it's a manufacturing defect, sometimes a design defect, sometimes something under or over-volted and it was enough to cause damage to any given component. Could be an IC, could be a capacitor, could be a poorly laid trace. A poorly shielded RF source could even damage any number of components. I mean, in theory a single high charge particle from that rare cosmic ray that reaches the surface of earth running full-steam-ahead through an IC could cause just the right amount of damage to make it fail although this would be an incredibly improbable scenario. Same goes for HDDs, televisions, your clock radio, whatever.
- rsync 8y ago"It feels like the author's main complaint is the frustration of not understanding SSD hardware as well." What is so frustrating about SSDs is how very poorly they compare to previous incarnations of solid state storage. Using Disk-On-Chip and/or IDE-pin-compatible CF cards, I had many, many devices in the field that lasted, mounted read-only, for decades An entire sect of the computing industry came to rely on these parts as alternatives to spinning media that could not mechanically fail. This is not the case with SSDs at all. They fail left and right, even mounted read-only, for all manner of complicated and interesting reasons. It's very frustrating that SSDs are not a step forward in reliability from spinning media and are a step downward compared to (for instance) a 16MB consumer CF card from Sandisk, circa 2000. rsync.net filers, which need a boot mirror, are always constructed with two unrelated SSDs - usually one Intel part and one Samsung part - so that when the inevitable usage-related failure occurs, it does not occur simultaneously to both members of the mirror which have, being a mirror, been subjected to identical usage-lives.[1] We shouldn't have to do that. [1] I can't overstate this - if you need a RAID mirror, do not use identical SSDs for the two members of the mirror. There are many, many cases of SSDs failing not due to "wear" or end-of-life, but due to weird usage edge cases that cause them to puke ... and in a mirror, you give the two parts identical usage ... we either get two different generations of Intel part (current gen and just-previous gen) or we get current Intel and current Samsung ...
- Mister_Snuggles 8y agoI've heard very similar advice for non-SSD mirrors too. Use different manufacturers or, at the very least, use different batches of disks from the same manufacturer.
- blattimwind 8y agoMost importantly, never assemble an array from drives that took the same shipping path i.e. came out of the same parcel.
- lsc 8y agoMost people use different batches but the same manufacturer, mostly because they remember advice from back when you could get a hardware raid card that would synchronize your scsi drives. Also, though, because most serious RAIDs contain more drives than you can find manufacturers of hard drives.
- blincoln 8y ago<i>Why shouldn't it? Isn't it just hardware too?</i> In a mechanical hard drive, there are moving parts which can wear out due to friction, etc. SSDs are solid-state, so it seems like at least theoretically, it should be possible to build one that keeps working for decades. e.g. I have solid-state hardware from the 70s and 80s which still functions. I've always been a little mystified as to why SSDs' data areas wear out for that reason,[1] but that's a whole separate issue. The author of the article is writing about sudden failure of the device as a whole. There are only two explanations I've ever heard for short lifetimes in electronics as a general industry.[2] For devices manufactured after about 2000 there's tin whiskers,[3] which began to be a problem because of RoHS requirements. I'm not sure if that applies here, though. If the device includes electrolytic capacitors, my understanding is that those generally have a finite lifetime as well, and it can be fairly short if they're poorly-made. I'm not a hardware expert, though, so I'd be interested in hearing about other factors, and I'm sure the author of the article would too. [1] I've seen lots of writeups of how wear-leveling works, etc., but never a good physical explanation of what is actually wearing out over time. [2] Obviously there are other factors for specific devices, or specific designs. E.g. maybe parts of a specific device break over time due to thermal expansion and contraction if the device wasn't engineered to handle that properly. [3] https://nepp.nasa.gov/whisker/background/ https://nepp.nasa.gov/whisker/background/
- pbhjpbhj 8y agoOn the subject of capacitor death. Is there a robotic device that can take in a circuit board and swap out all the [electrolytic] caps?
- sigstoat 8y agoi've never seen or heard of an automated board rework system. thinking about the steps and things i've had to do to manually rework boards, your machine would need not only be able to apply force to pull parts off of boards without damaging the board, but also be prepared to restore pads / through holes to usable states after desoldering parts, before new ones could go back in. there's a reason companies don't repair circuit boards in consumer electronics.
- rb808 8y agoI think the difference is familiarity. We've been using hard drives for decades so kinda know what to expect. SSDs have only been widely used 5-10y, so we're all just getting used to know how they work and how they die.
- deleted 8y ago[deleted]
- oasisbob 8y agoThe post resonated with me because of a stupid bug I hit in a ca 2011 SSD. (Samsung?) After 100 power-on cycles, the drive would brick itself. Required a firmware update in time to avoid. That defect doesn't strike me as being inherently related to SSD media, but really left a bad taste in my mouth with what might be going on in the development process to lead to such instability.