11 ms·
SSD will fail at 40k power-on hours (2021)
- dredmorbius 4y agoPossibly related to recent HN issues, see: https://news.ycombinator.com/item?id=32031243 https://news.ycombinator.com/item?id=32031243
- solardev 4y agoWow, thanks for sharing. I didn't realize how closely related they were. (TLDR For anyone wondering, "recent HN issues" means HN very likely went down yesterday because of this same bug, when two (edit: two pairs, four total) enterprise SSDs with old firmware died after 40,000 hours close together. An admin of HN and its host both like this theory. See details in that thread.) Edit: If you want to discuss that theory, it's probably better to do it in that other thread directly instead... dang and a person from M5 Hosting (HN's previous host) are both participating there.
- kazen44 4y agothe chance of two SSD's failing at the same time under normal circumstances is extremely slim. So this might actually be a good cause of this incident.
- MBCook 4y agoEspecially since one pair was a nearly unused backup server that had a totally different use profile.
- Group_B 4y agoIf both SSD's are from the same lot number and one fails, the chances of the second failing go up by a high amount. Both failing at the same time though is extremely rare.
- oogali 4y agoWe (as an industry) went through this bad batch madness with the IBM DeskStar 75GXP hard drives, which were affectionately referred to as "IBM Deathstar"[1]. It's rare, but it's not _that_ rare. You have to make the effort to understand why it failed. I had a situation where I deployed Toshiba SLC SSDs (that were purchased over the course of several months) and a piece of software that synchronized to disk frequently, resulting in about 1GB of writes per hour. After ~11 months in service, most of the drives died in the same 4 week period. We were astounded that everything failed so close to each other, including instances where both drives in a RAID 1 set were toast. We did extensive troubleshooting between the failed servers and the remaining servers and figured out that write volume (by proxy of in-service date) was the one predictor of failure. Shortly thereafter, wear leveling and TRIM became things we sought out mentions of when spec'ing out hardware. 1: https://en.wikipedia.org/wiki/Deskstar https://en.wikipedia.org/wiki/Deskstar
- jaclaz 4y agoThere was also more recently the case of the Seagate 7200.11, see my previous comment: https://news.ycombinator.com/item?id=32053477 https://news.ycombinator.com/item?id=32053477
- dredmorbius 4y agoSurprisingly few HN submissions under either term: IBM Deskstar: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=ibm%20deskstar%20&sort=byPopularity&type=story https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... IBM Deathstar: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=ibm%20deathstar%20&sort=byPopularity&type=story https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
- xyzzy_plugh 4y agoWhy would there be submissions? These drives predate HN.
- 4y ago
- dredmorbius 4y agoIt seems more likely it was four drives (though dang and Mike both refer to "two" in the earlier thread). Both primary and failover servers had RAID arrays. I suspect RAID 10 (striped mirror), which would mean two drives would have to fail to take down a single server. Four drives of the same manufacturer spec and batch would do that.
- Silhouette 4y agoThis is what always worries me about our home server. It's running ZFS with multiple redundant drives but the supplier refused (when I explicitly asked) to supply it with disks known to be from different batches claiming that the odds of multiple failures close together were negligible. Obviously we have backups as well but the time and cost to restore a full server from online backups can be significant.
- dredmorbius 4y agoWithin an earlier thread "Tell HN: HN Moved from M5 to AWS", there's an excellent comment by loxias about risk diversification across multiple factors. Well worth reading: https://news.ycombinator.com/item?id=32031655 https://news.ycombinator.com/item?id=32031655 I've increasingly come to view systems operations / SRE as a risk management exercise, where the goal is to reduce the odds of a catastrophic failure. Total system outage is one level, unrecoverable total system outage is even worse. Having multiple redundant backups / storage systems, in different locations, with different vendor hardware / stacks, all helps reduce risk of a single-factor outage. Though complexity risk is its own issue.
- kqr 4y ago> I've increasingly come to view systems operations / SRE as a risk management exercise, where the goal is to reduce the odds of a catastrophic failure. s/reduce/find an appropriate level for/ It's a common misconception that risk management and risk reduction are synonyms. Risk management is about finding the right level of risk given external factors. Sometimes that means maintaining the current level of risk or even increasing it in favour of other properties.
- pca006132 4y agoperhaps they are the same model. iirc people recommend not to use the same model of hardware to provide redundancy.
- jeffreygoesto 4y agoTrue. But it's more about the probability of things being "normal", isn't it? I had multiple Evo970 fail within a very short time. Turns out to be a systematic problem of drives produced in one specific month. Just how much difference is enough to be safe is the price question...
- pmlnr 4y agoHeh, no. We had a fleet of HPE Cloudline (CL3100) failing at the same time because the SSDs exhausted the writes.
- somat 4y agoThe way I always put it is, you have identical drives, with identical usage, powered for identical times. and you are still surprised when a second drive fails under the high stress environment of rebuilding after the first drive fails.
- mkl 4y agoNot two SSDs, four: two in the main server, and two in the backup server.
- solardev 4y agoThanks for the correction!
- taneq 4y agoYowch. The old "stagger your drive replacements, stagger your batches" thing might not be quite as outdated as we'd like to think...
- hackmiester 4y agoI had no idea anyone thought this was outdated. We certainly never stopped doing it. I think it is a timeless failsafe.
- icelancer 4y agoYeah, Backblaze and DigitalOcean both talk about it a bunch in their sysops stuff.
- mywacaday 4y agoAbout 20 years ago I worked for a small storage company, the person that managed the returns of disks form customers was very strongly of the opinion that the odd firmware versions on Seagate drives were returned way more often than the even.
- deleted 4y ago[deleted]
- wyager 4y agoI generally replace HDDs in my personal zpool a few days apart, for this reason. I also order them from different suppliers, so I can get different manufacture dates.
- iratewizard 4y agoThis gives me a strong feeling of general unease and flashbacks to the days of WD hard drives.
- usr1106 4y agoCisco is not a SSD manufacturer. They write industry-wide bug. Does that mean that more than one SSD manufacturer is affected (because they use partially the same firmware)? Further down they mention only Sandisk. Or is the industry-wide just their newspeak for saying any Sandisk of affected model, regardless whether installed in a Cisco box or somewhere else?
- dr_zoidberg 4y agoI'm interested here too. I've got a Crucial SSD from 2015 that's been on about: * 100% of 2015-2017, let's add 2 years here * Aboutish 50% of days since 2018 to 2020 * On and off again (5%?) since then until now. So it's about 3 years of full use? I'm eyeballing the use here. So it may be close to the numbers that were given, but I'm not sure. Guess I could check the SMART stats to get a precise number and from there decide what to do about it. Searching a bit it seems it's a well-known bug in "enterprise SSDs"[0, 1] (which my drive certainly isn't) but there aren't any real details about what causes it, other than "a firmaware bug". [0] https://www.servethehome.com/hpe-issues-hpd7-fix-for-ssds-that-will-fail-at-40000-hours/ https://www.servethehome.com/hpe-issues-hpd7-fix-for-ssds-th... [1] https://www.anandtech.com/show/15673/dell-hpe-updates-for-40k-hour-essd-failures https://www.anandtech.com/show/15673/dell-hpe-updates-for-40...
- dredmorbius 4y agoThe problem seems to be widely experienced. The Cisco report turned up in response to a post I'd made of the HN issue on the Fediverse: https://mastodon.infra.de/@galaxis/108622795822100862 https://mastodon.infra.de/@galaxis/108622795822100862
- dredmorbius 4y agoDang also listed a few previous submissions on the topic. None of which gained traction at the time: https://news.ycombinator.com/item?id=32038993 https://news.ycombinator.com/item?id=32038993
- wtallis 4y agoEnterprise SSDs are commonly made by one of a handful of dominant companies and then rebranded by server vendors, so that you can see a SanDisk or Samsung SSD sold as a Dell EMC or Cisco or HPE drive.
- userbinator 4y ago40000 (or even 40960) seems an odd number to fail at. 64k or 32k would make the cause pretty obvious, but 40000 doesn't seem all that round in binary. Perhaps a 12-bit counter incrementing every 10h? This is puzzling. Of course, I am also entertaining the possibility that no one thought they would be in use for this long, which would certainly be evidence of planned obsolescence.
- twawaaay 4y agoVery strange understanding of the word "evidence". No sane SSD manufacturer would do such thing on purpose. You do it and you loose business, that's it. The simplest explanation is that somebody made an honest engineering mistake.
- fartcannon 4y agoGiven the power dynamic between a single customer and large corporations, the smart thing to do is to assume malice until prove otherwise. This puts the onus on the corporations and, if we're lucky, creates an environment where they compete with each other to be seen as the most honest. The worst thing that happens is the single customer has to buy an SSD from someone they don't trust. If we do the opposite, as you say, and assume everything is an honest mistake, that puts pressure on the single customer to prove that the organization with a huge marketing budget is doing something wrong. In this situation, the worst thing that happens is we all get taken advantage of. Our collective distrust is the only power we have against massive marketing/PR budgets. It doesn't have to be angry, or sour, or cranky, we just collectively need to not take their word until we have a reason to do so.
- charcircuit 4y agoAre you seriously saying that by default we should believe they intentionally planned to cause their customers to lose all of their data?
- deleted 4y ago[deleted]
- civilized 4y agoIt's been over two years since this was first identified... since this apparently affected many makes and models of SSDs, it would be nice to know if my laptop could be affected and if there's anything I could do about it.
- pmoriarty 4y agoOne thing everyone could and should be doing is backups.
- m0llusk 4y agoTwo things: Test restores or you don't actually have backups. Just saying.
- chrischen 4y agoI got bit by this with iPhone backups. I did a phone trade in and followed the backup before trading in instructions. Problem is after the trade in the backup failed to restore due to an unknown error. The whole manual syncing and backing up with a cable workflow with Apple is super fickle and riddled with bugs. Luckily I had Time Machine backups of my iOS backups and I managed to avoid losing too much data. As a sidenote it seems like Apple has pretty much neglected their offline backup and syncing workflow to drive more people to just pay for iCloud storage. Half the time my iPhone takes hours just to get detected by the mac when plugged in.
- rexf 4y agoWhile I don't like how annoying Apple is with service upselling (iCloud, Music, Arcade), at least they moved iPhone backup from iTunes to Finder. So their local iPhone backup process is being maintained over time. I don't have issues with my computer (PC or Mac) detecting my iPhone. Generally need to make sure iPhone is unlocked after plugging it in. What is tough is the large size of my iPhone (X gb) and how small my Mac's HD is (2X gb).
- yomkippur 4y agocrap so its certainly HP laptops. so which laptops are safe from this?
- mrkramer 4y agoMy HP laptop has Toshiba SSD. I'm not sure about other models. But I think only enterprise SSDs are affected.
- yjftsjthsd-h 4y agoThis appears to be talking about Cisco enterprise drives; where do you see anything about HP laptops? Edit: If it's a problem in Cisco's upstream vendor then it could affect others, but probably still just enterprise stuff.
- Tempest1981 4y agohttps://news.ycombinator.com/item?id=32052757 https://news.ycombinator.com/item?id=32052757 > HPE is one of the SSD OEMs affected by it: ...
- moffkalast 4y agoAre you looking at the same post we are? Because your comment makes no sense whatosever.
- onion2k 4y agoBackblaze have a great blog about things they learn about hard drives. It's been going for years, less about firmware issues and more about general usage. https://www.backblaze.com/blog/backblaze-drive-stats-for-q1-2022/ https://www.backblaze.com/blog/backblaze-drive-stats-for-q1-...
- lucb1e 4y agoCheck your power-on hours: $ sudo smartctl -a /dev/sda | grep -e Power_On_Hours -e ^ID ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 9743 Just looking at the raw value, it seems to be 9'743 hours in my case
- borplk 4y agoMine is above 53,000 hours ... time to check my backups!
- lucb1e 4y agoSounds like you're in the clear for this particular bug... ...but always check your backups regularly for data that is dear to you! Protip of the day: that includes things on someone else's server. I remember when Grooveshark went offline from one day to the next and I lost nearly my whole library because I remembered only some artists and had to go through thousands of songs to find which ones I actually liked from them. My browser's localStorage object had the playlists but I didn't use those much. Or when 000webhost cancelled my account because I was using the 100MB(?) to back up some files that were most important to me, rather than for actual webhosting (in my defense, I was 15 at the time), and so when I returned from a holiday with my parents with an actual crashed hard drive, that turned double sour. Backing up things from what they now call the "cloud" is something I learned early, as I have virtually no code I wrote before that summer, only some of the music, only essays with WordArt if they were printed, etc. If you use Telegram, Spotify, Netflix, maybe you have videos uploaded to YouTube and not have local copies anymore... my recommendation is to have backups of things that are important to you, onto a medium that you own (it's only a disaster-case copy anyway), and for copyrighted content like Spotify/Netflix it would simply be enough to just have a list of songs/videos. Maybe Netflix doesn't go offline from one day to the next, but your account might be hacked, or that friend you share it with might be hacked, or the right set of hard disks fail at their datacenter, etc. GDPR data exports are your friend, particularly when they're automated and you don't have to bother support. (They might also reveal, as in my case, that Spotify knows how often you shower because I then connect it to a particular waterproof bluetooth speaker at wakeup time. Data exports are also fun to browse!)
- DoneWithAllThat 4y ago
- ParetoOptimal 4y agoIt's a device to identify certain kinds of people who would have a problem with less loaded language without any loss in clarity.
- mancerayder 4y agoOther than DEI administrators, trainers and people in positions with DEI in them, who is actually getting offended?
- rajamaka 4y agoI would love to see some examples of Cisco documentation that ever offended anyone.
- mlyle 4y agoI miss old Cisco documentation, with IP addresses and router names like SanJose3 and 408 phone numbers on PRIs etc.
- bombcar 4y agoIt's a warning that the documentation may refer to master/slave or something like that because Cisco cares enough about DEI to update documentation but not enough to actually update out-of-support firmware.
- mistrial9 4y agorelated topic - leaving SMART control tests ON for a (non-SSD) drive, apparently interferes with sleep; the drive will wake up to test itself. For some drives, I would prefer that not to happen and just stay quiet. Yet, testing for this behavior seems elusive -- querying the disk wakes it, and most linux disk tools seem unaware of sleep state. I just listen for the disk spinning, or notice a long pause before an operation.
- salawat 4y agoSomewhat unrelated, but I recently had a motherboard fried by power instability which has given me a healthy respect for the difference between spinning rust and SSD's. My SSD's were scragged. my HDD's were just fine. I guess it's time to figure out how to get a realistic write-through cache setup going, because from now on, if it ain't on spinnin' rust it ain't hard enough yet.
- gameshot911 4y agoOf what quality was the mobo? I thought the higher-end stuff typically has power protection.
- salawat 4y agoServalWS B450. Was not at all amused. Oddest bloody thing, because had a pair of Samsung EVO's M.2 NVMes in there, and it still managed to let the magic smoke out. CPU/GPU and RAM lived, but the corruption of the drives (even if the data was largely recoverable) and rendering of them as inviable to further writes really took me by surprise. That combined with the way the HDD just did not care one lick despite apparently, just illustrated for me a difference in tolerance to operating conditions that I'd not had the chance to witness first hand yet. Just figured I'd share while we were talking about SSD weirdness and firmware nonsense.
- mbb70 4y agoWe were eviscerated by this (or something just like it) a few years ago. Drives starting failing by the dozens. Had to rebuild from HDD backups, down for a week. I still have nightmares.
- walterbell 4y agoWould companies be willing to contribute to the OpenSSD project? OCP (Open Compute Project) has shown that customer-operators can cooperate on open hardware designs, successfully influencing enterprise hardware supply chains. Commercial DPUs and SmartNICs were preceded by a decade of open hardware and research by the NetFPGA project (https://netfpga.org https://netfpga.org). Why not DiskFPGA? 2017 OpenSSD overview, based on Xilinx: https://github.com/Cosmos-OpenSSD/Cosmos-plus-OpenSSD/blob/master/doc/Cosmos%2B%20OpenSSD%202017%20Tutorial.pdf https://github.com/Cosmos-OpenSSD/Cosmos-plus-OpenSSD/blob/m... 2022 status, http://www.openssd-project.org/ http://www.openssd-project.org/ > OpenSSD platforms are still being actively used in many academic institutions. As of June 2022, we have renewed the homepage hoping that this site will be a forum to share various simulators, tools, traces, etc. not only for the conventional SSDs but also for the upcoming storage devices such as KVSSD, ZNS SSD, and Computational Storage (CSX). This site is being maintained by Systems Software and Architecture Lab. at Seoul National University as a part of the SW STAR Lab. project.
- colejohnson66 4y agoAn open source SSD is also a lot more feasible than an open source hard drive. Even if you managed to get an open source HDD controller, you still need the precision mechanical parts that are impossible for the average person to make. With SSDs, however, it’s just a PCB with ICs. Edit: this obviously ignores any troubles one would have sourcing the ICs (such as possible NDAs)
- belkarx 4y agoIs there anything special about making SSDs that the average person would not be able to do or is it a "if you can outsource PCB printing and maybe solder you can make one" situation?
- ratsmack 4y agoThe limiting factor would be the memory chips themselves and any firmware required for them (if any). I also don't know how well they are spec'd and if full documentation is available without NDA's and lawyers.
- Kalanos 4y agotell that to my 2014 macbook that's been constantly running neural nets for the past 5 yrs
- fijiaarone 4y agoI’m moving all my storage to vellum with papyrus backups.
- dredmorbius 4y agoAlexandria's got an excellent hosting facility.
- ShroudedNight 4y agoSadly rendered effectively write-only
- dredmorbius 4y agoThe original argument for geographically-distributed backups!
- yalogin 4y agoWhat exactly is causing the bug though? If the same area is written to some x number of times the solid state device in that location permanently fails, is that correct? If so in an always on device how can this bug be escaped? They need to randomize the writes and for that the storage size should be a multiple of what is needed for regular operation. Even then the disk will fail eventually. What am I missing here?
- bell-cot 4y agoA Modest Proposal: All $LARGE business insurance policies specify that, to the extent to which any insured loss was caused or worstened by reliance upon the correct functioning of SSD or related drive technologies...YOYO, and any & all losses are solely on you.
- kleer001 4y ago.
- jsemrau 4y agoOne of the dumbest things I have done in my life is buying an SSD and new HDDs to farm Chia. After about a month of farming, the SSD died due to the constant read/writes.
- arthurcolle 4y agoDid you make any money?
- jsemrau 4y agoNice one. For your enjoyment have a look at the "all-time" chart. https://coinmarketcap.com/currencies/chia-network/ https://coinmarketcap.com/currencies/chia-network/ While the concept of Chia was interesting at the time and also reminded me of the "smart fridges of silicon valley (the show)", filling up gigabytes with trash data to prove a technical point made me lose interest. Just glad I didn't invest more.
- champtar 4y agoHPE had the same issue on some of their SSDs. We received an advisory months before it would have been a problem, and had time to upgrade all our customers ... except 2 servers that we missed. Luckily when I saw all disk in error in the iLO on one of the server I remembered this issue, googled the model, confirmed it was affected, and was able to shutdown the second server and start the upgrade. Not sure client was happy but at least it was only a 1h outages instead of maybe a day to get the disks + restoring from backup. HPE did replace the disks under warranty.
- submeta 4y agoHere's how to check the power on hours on a Mac: I didn't have `smartctl` installed on my Mac, so here's how to install it via `brew`: brew install smartmontools My SSD is `disk0` (check `Disk Utility.app`). Running `smartctl` for my `disk0`: sudo smartctl -a /dev/disk0 | grep -e "Power On Hours" Power On Hours: 6,334 So I have only ~15% of those 40k hours used (6,334/40,000).
- DonHopkins 4y agoThey should have used a Free BIOS Language in their hardware like Open Firmware FORTH from the OpenBIOS project, to go with the Bias Free Language in their documentation. https://en.wikipedia.org/wiki/OpenBIOS https://en.wikipedia.org/wiki/OpenBIOS >OpenBIOS is a project aiming to provide free and open source implementations of Open Firmware. It is also the name of such an implementation. >Most of the implementations provided by OpenBIOS rely on additional lower-level firmware for hardware initialization, such as coreboot or Das U-Boot. https://en.wikipedia.org/wiki/Open_Firmware https://en.wikipedia.org/wiki/Open_Firmware >Open Firmware is a standard defining the interfaces of a computer firmware system, formerly endorsed by the Institute of Electrical and Electronics Engineers (IEEE). It originated at Sun Microsystems, where it was known as OpenBoot, and has been used by vendors including Sun, Apple, IBM and ARM. Open Firmware allows the system to load platform-independent drivers directly from a PCI device, improving compatibility.
- ghostly_s 4y agoYikes. Cisco claims this is "an industry wide firmware index bug". Is there any validity to this claim? Are any consumer drives affected by the same issue?
- zinekeller 4y agoYes, HPE is one of the SSD OEMs affected by it: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00092491en_us https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na... https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00097382en_us https://support.hpe.com/hpesc/public/docDisplay?docLocale=en... > Are any consumer drives affected by the same issue? As far as I know it doesn't affect consumer drives, but I wouldn't be surprised if some have the same defective firmware.
- fulafel 4y agoIs there any information about the provenance of this SSD controller? Sounds like enterprisey venodrs all rebranded some upstream supplier's hardware. edit: apparently sandisk: http://forum.hddguru.com/viewtopic.php?f=3&t=39964 http://forum.hddguru.com/viewtopic.php?f=3&t=39964 - also a clue about the magic 40k hour significance: "the SSD alters its performance in some way as it approaches end of life. This appears to shine some light on the reason for a trigger at 40K Power On Hours."
- zymhan 4y agoThis apparently also happened two years ago? https://www.anandtech.com/show/15673/dell-hpe-updates-for-40k-hour-essd-failures https://www.anandtech.com/show/15673/dell-hpe-updates-for-40...
- abrax3141 4y ago4 byte integer rollover: 2^32=4,294,967,296/4.5=954,437,177/365=2,614,896/3600=726/24=30ticks/sec
- Denvercoder9 4y agoUnlikely; a clock running at 30 Hz overflows a 32 bit (unsigned) integer in 39,768 hours, while the HN disk failed after at least 39,984 hours [1], and the vendors wouldn't issues warnings about 40,000 hours if it actually fails about 230 hours before that. [1] https://news.ycombinator.com/item?id=32031428 https://news.ycombinator.com/item?id=32031428
- abrax3141 4y agoNot sure about the mfgr- could be rounding for memory saliency. . . but re HN they’re counting clock time not power on time. Could have easily been turned off total 10 days for maintenance etc. (and good routine could have both servers off about the same no hrs.) That’s only 0.6% downtime.
- Denvercoder9 4y ago> Not sure about the mfgr- could be rounding for memory saliency. . . In that case, I would expect them to be rounding down, not up, and to at least mention the exact number somewhere. > but re HN they’re counting clock time not power on time. Could have easily been turned off total 10 days for maintenance etc. I seriously doubt HN has been down for 10 days over the last five years. As discussed in the other thread I linked, this has been one of the longest HN outages.
- abrax3141 4y agoYeah, no, I don’t mean crashed altogether, just off for routine maintenance on a rotating basis. But anyway, no sense in prolonging this. Anyway, agree that 1% seems high.
- nspattak 4y agoI have an 128gb osz agility (or sth of that era) disk that is still in use in my mom's laptop :)
- jgrahamc 4y agoSo, has anyone opened one of these SSDs and tried to get at the firmware and find out WTAF code was written?
- Neil44 4y agoYou would just find a firmware update file, much easier, there's a hddguru thread linked above somewhere where people have been having a gander.
- fareesh 4y agoFrom what I remember reading this affected Sandisk only, is that correct? I have a Samsung EVO and OCZ SSD. Would these be affected too? Perhaps some shared component? Cisco has written "Industry-wide" here which is confusing
- AtNightWeCode 4y agoThis sounds like the exact same bug that effected HPE products a couple of years ago.
- neycoda 4y ago"the SSD will report that 0 GB of available storage space remains. The drive will go offline and become unusable." Considering this is a firmware "bug" that bricks the drive, due to a misplaced index, not a physical wear issue, it appears to be a 4.5-year planned obsolescence feature.
- deleted 4y ago[deleted]
- codethief 4y agoSince this is "an industry wide firmware index bug", is there a (complete) list somewhere of all SSD models that are affected?
- zoomablemind 4y agoReading the Wikipedia entry on Power-on hours [1] says that: "...Once a [SSD] drive has surpassed the 43,800 hour mark (5 years), it may no longer be classed as in "perfect condition" " And that SSD generally has 5 year life expectancy. So with this bug, should we simply think of it just to become 40,000 hour hard life-time limit? Well, it's 10% less than by design. I'm just not sure how realistic will it be to obtain SSD firmware updates given that it's "an industry wide firmware index bug". How could I even know if a particular SSD has an affected firmware? [1]: https://en.m.wikipedia.org/wiki/Power-on_hours https://en.m.wikipedia.org/wiki/Power-on_hours
- NoMAD76 4y agoSeems that I also need a replacement SSD Using CrystalDiskInfo on my Samsung 850 EVO 1TB it shows Health 99%, 5450 Power on Count, 27463 Power on Hours BUT [FF] Remaining life 10, that's at the lower end...
- FunnyBadger 4y agoNothing has eternal life. Especially not electronics. And certainly not more advanced semiconductors. The rule-of-thumb is the lifespan of planar CMOS processes in years is proportional to the "node size" in nanometers. So we are right now at 2-10 years. Some specific ICs or specific applications or specific designs can be bigger or smaller than this but it's the average. If you've ever worked on "antique" electronics, this is no surprise.