Live data from Hacker News

Backblaze Drive Stats for 2024

backblaze.com

181–190 of 209 posts

Re: Backblaze Drive Stats for 2024

#181
post #113

Earlier quoted context omitted.

Sure, but it's hard to blame that on Seagate. The AFR is their fault.

It's not Seagate's fault, but it would behove them to clamp down on such activity by authorised resellers. After all, it's not just the buyer getting ripped off; it's also Seagate. A customer paid for a brand new Seagate drive and Seagate didn't see a penny of it.

Yes. Nothing would lead me to believe Seagate isn't fervently working to shut down fraudulent resellers behind the scenes.

Re: Backblaze Drive Stats for 2024

#182
Polite data viz recommendation: don't use black gridlines in your tables. Make them a light gray. The gridlines do provide information (the organization of the data), but the more important information is the values. I'd also right align the drive failures so you can scan/compare consistently.

Re: Backblaze Drive Stats for 2024

#183

> I have been authoring the various Drive Stats reports for the past ten years and this will be my last one. I am retiring, or perhaps in Drive Stats vernacular, it would be “migrating.” Thank you for all these reports over the years.

Thanks for dutifully providing us this info on (many a) silver platter.

Re: Backblaze Drive Stats for 2024

#184
post #96

Earlier quoted context omitted.

>Often you will read online of people experiencing multiple failures from drives purchased from the same batch I'll toss in on that anecdata. This has happened to me a several times. In all these cases we were dealing with drives with more or less sequential serial numbers. In two instances they were just cache drives for our CDN nodes. Not a big deal, but I sure kept the remote hands busy those weeks trying to keep…

This has been the "conventional wisdom" for a very long time. Is this one of those things that get "lost with time" and every generation has to rediscover it? Like, 25+ years ago I would've bought hard drives for just my personal usage in a software raid making sure I don't get consecutive serial numbers, but ones that are very different. I'd go to my local hardware shop and ask them specifically for that. They'd sho…

Same thing I did except I only wanted WD Red drives. I bought them from Amazon, Newegg, and Micro center. Thankfully none of them were those nasty SMR drives, not sure how I lucked out.

Re: Backblaze Drive Stats for 2024

#185
post #47

Earlier quoted context omitted.

In fact for home users backup is WAY more important than RAID, because your NAS down for a (restore time) is not that important, but data loss is forever.

For essential personal data you're right, but a very common use case for a home NAS is a media server. The library is usually non-essential data - annoying to lose, but not critical. Combined with its large size, it's usually hard to justify a full offsite backup. RAID offers a cost-effective way to give it some protection, when the alternative is nothing

That assumes disks never age out and arrays always rebuild fine. That's not guaranteed at all.

Re: Backblaze Drive Stats for 2024

#186
post #78

Earlier quoted context omitted.

Having to restore my media server without a backup would cost me around a dozen hours of my time. 2 bucks a month to back up to Glacier with rclone’s crypt backend is easily worth it.

Have you checked the costs for restoring from Glacier? It's not the backing up part that's expensive. I would not be surprised if you decided to spend the dozen hours of your time after all.

The retrieval cost is less than 1 hour of my time and I expect less than 10% chance I'll ever need it.

Re: Backblaze Drive Stats for 2024

#187
post #78

Earlier quoted context omitted.

Having to restore my media server without a backup would cost me around a dozen hours of my time. 2 bucks a month to back up to Glacier with rclone’s crypt backend is easily worth it.

How are you hitting that pricing? S3 "Glacier Deep Archive"? Standard S3 is $23/TB/mo. Backblaze B2 is $6/TB/mo. S3 Glacier Instant or Flexible Retrieval is about $4/TB/mo. S3 Glacier Deep Archive is about $1/TB/mo. I take it you have ~2TB in deep archive? I have 5TB in Backblaze and I've been meaning to prune it way down. Edit: these are raw storage costs and I neglected transfer. Very curious as my sibling comment…

Yup, deep archive on <2TB, which is more content than most people watch in a lifetime. I mostly store content in 1080p as my vision is not good enough to notice the improvement at 4K.

Re: Backblaze Drive Stats for 2024

#188
post #152

Earlier quoted context omitted.

Nobody should ever have peace of mind about a single drive. You probably have odds around 5% that the storage drive fails each cycle, and another 5% for the OS drive. That's significant. And in your particular situation, 3 refurbished WUH721414ALE6L4 are the same total price. If you put those in RAIDZ1 then that's 28TB with about as much reliability as you can hope to have in a single device. (With backups still bein…

My understanding is that with the read error rate and capacity of modern hard drives, statistically you can't reliably rebuild a raid5/raidz1

Not an expert but I’ve heard this too. However - if this IS true, it’s definitely only true for the biggest drives, operating in huge arrays. I’ve been running a btrfs raid10 array of 4TB drives as a personal media and backup server for over a year, and it’s been going just fine. Recently one of the cheaper drives failed, and I replaced it with a higher quality NAS grade drive. Took about 2days to rebuild the array, but it’s been smooth sailing.

Re: Backblaze Drive Stats for 2024

#189

Earlier quoted context omitted.

"My most recent drive [...] it should be fine for the next few years until it's time for the cycle to repeat." The amount of time they stay on a single drive.

Drive manufacturers often publish the AFR. From there you can do the math to figure out what sort of redundancy you need. Rule of thumb is that the AFR should be in the 1-2% range. I haven't looked at BB's data, but I'm sure it supports this. Note, disk failure rates and raid or similar solutions should be used when establishing an availability target, not for protecting against data loss. If data loss is a concern,…

You picked a weird place to reply, because that comment is just saying what "cycle" means.

But yes, I've done the math. I'm just going with the BB numbers here, and after a few years it adds up. The way I understand "peace of mind", you can't have it with a single drive. Nice and simple.

Re: Backblaze Drive Stats for 2024

#190
post #152

Earlier quoted context omitted.

Nobody should ever have peace of mind about a single drive. You probably have odds around 5% that the storage drive fails each cycle, and another 5% for the OS drive. That's significant. And in your particular situation, 3 refurbished WUH721414ALE6L4 are the same total price. If you put those in RAIDZ1 then that's 28TB with about as much reliability as you can hope to have in a single device. (With backups still bein…

My understanding is that with the read error rate and capacity of modern hard drives, statistically you can't reliably rebuild a raid5/raidz1

The bit error rates on spec sheets don't make much sense, and those analyses are wrong. You'd be unable to do a single full drive write and read without error, and with normal RAID you'd be feeding errors to your programs all the time even when no drives have failed.

If you're regularly testing your drive's ability to be heavily loaded for a few hours, you don't have much chance of failure during a rebuild.

Post reply on HN