I was very happy using IBM drives, but then it turned out they were following the Wile E. Coyote rule: Soon after I read about their DeathStar drive failures, mine did too.My 320mb (megabyte) IDE IBM hard drive from 1994 still boots Win3.1 and loads Doom II just fine.
Who says older drives are unreliable?
I'm actually OK with that. The IMPORTANT shit is backed up and if those drives last longer, you have less concern about the important shit crapping out.The problem with Backblaze's figures is they only have one type of workload - backup. So as much it might tell you what backup does to disks I don't think you can extrapolate this to other uses.
Fucking VERY justified. I will NEVER have another platter drive in a normal end-user computer. Do I use them in my NAS, and as external backups for my NAS? Sure, but that is a very different use case.
I can help with that sample size. As an I.T. guy, I've fixed and/or replaced a lot of computers and their parts over the years.Interesting claim. I have yet to have an SSD fail. Back when I was using HDDs, I had one fail every year or two (I typically have 3-5 drives in my main personal PC). The 7200 RPM drives seemed to fail a lot more, regardless of brand, so before making the transition to SSDs (~13 years ago?), I was sticking with those.
Obviously, my sample size is pretty small, but the high failure rate I was experiencing with HDDs (On 24/7 but definitely closer to a typical consumer workload, otherwise) was just as much reason for me to transition as performance.
My main drives are solid state but I still run a couple platter drives in mirror, everything of course gets backed up to my NAS/Cloud. Maybe If i won the lottery or something i could make this all SSD.
View attachment 120438
Same over here. Before I always had one or two go through warranty every year, and now I haven't done that in years!This matches my experience. It has been a long time since I have had a hard drive over 2 years old fail. The last one was a Seagate 3TB Barracuda, a model which was known for its excessively high failure rate forget which one), which failed at 6 years old.
I have still got a stack of 2TB and 4TB WD and Seagate drives that all function perfectly fine and have no bad sectors. They're just not really useful.
In many ways, you can think of a datacenter’s use of hard drives as the ultimate test for a hard drive—you’re keeping a hard drive on and spinning for the max amount of hours,
#!/bin/sh
for i in `ls /dev/sg*`; do
/usr/bin/openSeaChest_PowerControl -d "$i" --idle_a disable
/usr/bin/openSeaChest_PowerControl -d "$i" --idle_b disable
/usr/bin/openSeaChest_PowerControl -d "$i" --idle_c disable
done
I have 4 2TB WD drives in my NAS still going strong. I went with the "WD Green" 5400 rpm drives. Can't complain. Now, QA comes and goes, so when it's time to replace them I've no idea what I'll go with, but low-power (aka "green") and 5400rpm seemed fine for a NAS environment.I had a set of 4TB WD Nas drives installed in my NAS, had one failure (which my warrantee happily handled). The rest of the drives in the nas had reached almost 11 years old with no issues before I replaced them. I've since replaced them (ran out of room) with a set of 8TB Ironwolf drives, which are approaching 1 year old now with no issues.


We have many high IOP clusters and the SSDs fail at a higher rate than the spinning rust. It's the nature of SSDs. They are fast, but there are only so many write/erase cycles in them before they are done, even with wear leveling.Obviously mechanical drives. Has anyone done any sort of life testing on SSD?
Its also really awkward to get a reasonable figure of 'lifespan' in time for an SSD, as even though they tend towards being measured in Terabytes Written (TBW), the endurance is going to depend a lot on the types of NAND memory used (SLC, MLC, TLC) as well as the type of file system the disk is formatted for - ie something using a 'CopyOnWrite' type, whilst more stable in a practical sense, is going to clock up far larger write volumes more quickly.We have many high IOP clusters and the SSDs fail at a higher rate than the spinning rust. It's the nature of SSDs. They are fast, but there are only so many write/erase cycles in them before they are done, even with wear leveling.
However, with the SSDs that have failed, I've only seen a SMALL handful reach their write/erase limit. Most of them have failed due to data integrity errors long before hitting their cycle limit.
I've generally liked HGST drives a bunch, but when I was setting up my current RAID, I tried ordering a big batch of used 4TB models, which per Backblaze are very good indeed. And those drives were a disaster. Most of them were throwing errors in short order; ZFS really didn't like them. I ended up having to return the whole pile.Used enterprise drives are the way to go. Cheap, high-performance, large capacity, and they're often available with 3-5 year no-questions-asked warranties. Yes, they're used, but any home server should be running a RAID or have some sort of redundancy. I have been running my unRaid server with nothing but re-certified HGST drives in the array for several years, and I'm never going back to consumer drives.
At my workplace, we're seeing a spate of Samsung SSD failures at the 3 year mark. Mine failed three years to the day of its purchase, which also happens to be when its warranty runs out. Others are failing slightly before and slightly after that warranty date, but it appears to be statisically significant (4 out of 50 purchased at the same time).Anecdotal evidence, but I've had two SSD failures total. And for those failures, I think that was a bad Sandisk lot, because I had two other drives from the same line that are still kicking since 2017 but were manufactured at a different time period. My 14-15 year old Crucial C300 is still puttering along just fine. Of course, I have some even older WD Velociraptor 300GB drives that are still working too. That said, cheaper HDDs have had a lifespan of about a decade for me and I simply wouldn't trust them to reliably backup my data past that point. In contrast, my MLC based Crucial and Samsung drives still have 95%+ health and those are all 10+ years old now.
Full disclosure: I’m the delivery guy for hard drives to Backblaze. I always drop the Seagate drives a couple times before taking them in.
Many years ago I worked for a small PC manufacturer. Our product frequently arrived at customer sites with peculiar damage. We were able to replicate this damage by dropping the boxes onto their corners from a 2 meter height, about the height of standing on a delivery truck bed.Full disclosure: I’m the delivery guy for hard drives to Backblaze. I always drop the Seagate drives a couple times before taking them in.
I don't think they intended to produce some kind of research grade reporting, its interesting observations and they could have just kept it internal.am happy people are calling out the poor back blaze study
Always good to hear from Backblaze again!
Only Exos drives for me, have never failed me yet![]()
Ouch. Brutal.You really don't need to, Seagate did it already.
Edit: grammar
OMG____Many years ago I worked for a small PC manufacturer. Our product frequently arrived at customer sites with peculiar damage. We were able to replicate this damage by dropping the boxes onto their corners from a 2 meter height, about the height of standing on a delivery truck bed.
issue is most people think so... that the problemI don't think they intended to produce some kind of research grade reporting, its interesting observations and they could have just kept it internal.
The Backblaze stats are good, as long as you remember the way they choose their drives: the absolute cheapest per TB at the time of purchase. So, at any given time, they're generally sampling the worst drives available. If you're buying upmarket from where they are, your drives may do better.issue is most people think so... that the problem
If you go through to the the quarterly reports (dig around a little), they list the average age of each drive model along with its AFR. Smaller models are generally older, and will thus have much higher average months of service. As they rotate the smallest drives out, that also rotates the oldest drives out, so they gradually drop off the standings altogether.Is that still the case for 2025? It's only been 4 years.
I think most people's data needs expand before most HDDs hit their MTBF, I know my RAID that everyone in the house backs up to certainly do. I have had one drive fail in 15 years in the array (annoying but no loss obviously just popped another in and up it came). One failure that has mostly gone away is since most RAIDs are no longer hardware RAID they are software there is no longer that RAID controller to fail (yes the computer can die, but another computer (assuming not HW key encrypted) can just attach and keep going. I do have it make a backup of the RAID map and partition maps in a separate sector so a file system corruption hopefully won't bork the RAID setup. I am going to have to upgrade from the 12TB drives (Hitachi if I recall) that are running it to 20s soon, as backups keep getting bigger and more machines hit the RAID (enough bandwidth that I had to move that to my 2.5gbs ethernet subnet from the gigabit)A LOT of people used to cite Backblaze stats as a reason to not buy any kind of storage made by Seagate, and it was always annoying to me. Thankfully I don't see it as much now.
I've had 3-5 HDD's in all my computers ever (starting from the late 90's, most of which were scavanged/bought used, also I would replace my computers every year or so, so that is a lot of drives) and I think I've had ... four HDD failures, if I count the ones that worked when I took them out but a decade later was dead. Live HDD failues, as in a HDD that failed when it was in use? One.
I think people are forgetting a major problem in analysis/statistics that you have many variables that are very obvious, but people forget. Such a, the fact higher density data drives,, take longer to fill certain sections that could be bad, that the drive and FS systems work to hide. And they don't re-use the same sections anymore. So the larger the drives, the longer it takes to determine if they are failing, which means there is not a true linear curve to HDD usage, and HDD destruction from usage takes longer to determine now, because of how the FS and internal hardware manages the data., you have to treat all the data periodicity as a black box, which means the data curves will be longer and higher on a crunched axis because of this performative drive longevity magic they try to perform. The data charts can't be compared this way, make it 3D.There's a strange oeriodicity to the graph that makes me wonder if we're seeing a methodological problem that's creating aliasing. Why would drives fail most often at "odd.5" ages, and least often at "even.5" ages? I'd expect the individual ticks to show more random noise next to their neighbors, and less of a modulated 2-year sinusoid.
Backblaze fills their drives in days or weeks.I think people are forgetting a major problem in analysis/statistics that you have many variables that are very obvious, but people forget. Such a, the fact higher density data drives,, take longer to fill certain sections that could be bad, that the drive and FS systems work to hide. And they don't re-use the same sections anymore. So the larger the drives, the longer it takes to determine if they are failing, which means there is not a true linear curve to HDD usage, and HDD destruction from usage takes longer to determine now, because of how the FS and internal hardware manages the data., you have to treat all the data periodicity as a black box, which means the data curves will be longer and higher on a crunched axis because of this performative drive longevity magic they try to perform. The data charts can't be compared this way, make it 3D.
It's not a 'study' - if you were doing a 'study' and could somehow get someone to pay for it you would do things very differently. This is 'hey, we buy thousands of times as many drives as you will ever see in your entire life to get our job (backup) done, we track when they go bad, here's what we saw.'am happy people are calling out the poor back blaze study
I've had an SSD fail, but it was definitely at least partially user error. I forgot to pull the tape off the thermal pad for my mobo's M.2 heat spreader, so it was likely running much hotter than intended.Interesting claim. I have yet to have an SSD fail. Back when I was using HDDs, I had one fail every year or two (I typically have 3-5 drives in my main personal PC). The 7200 RPM drives seemed to fail a lot more, regardless of brand, so before making the transition to SSDs (~13 years ago?), I was sticking with those.
Obviously, my sample size is pretty small, but the high failure rate I was experiencing with HDDs (On 24/7 but definitely closer to a typical consumer workload, otherwise) was just as much reason for me to transition as performance.
I was wondering something similar about their algorithms for writing and reading data. Do their results assume the drives are spinning at a constant rate per minute 24 seven? Maybe a different metric is failures per billion360° rotationsSomething not mentioned in the original blog post or remarked on here is that Backblaze has improved their enclosure design over that time. They're published articles about their bespoke storage server cases and how they've evolved. That includes improved vibration isolation and temperature management. That could be a large confounding factor in them seeing decreasing failure rates in their fleet.