112
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Jul 2025
112 points (100.0% liked)
Technology
73606 readers
1570 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
no thanks Seagate. the trauma of losing my data because of a botched firmware with a ticking time bomb kinda put me off your products for life.
see you in hell.
I had a similar experience with Samsung. I had a bunch of evo 870 SSDs up and die for no reason. Turns out, it was a firmware bug in the drive and they just need an update, but the update needs to take place before the drive fails.
I had to RMA the failures. The rest were updated without incident and have been running perfectly ever since.
I'd still buy Samsung.
I didn't lose a lot of data, but I can certainly understand holding a grudge on something like that. From the other comments here, hate for Seagate isn't exactly rare.
I can certainly understand holding grudges against corporations. I didn’t buy anything from Sony for a very long time after their fuckery with George Hotz and Nintendo's latest horseshit has me staying away from them, but that was a single firmware bug that locked down hard drives (note, the data was still intact) a very long time ago. Seagate even issued a firmware update to prevent the bug from biting users it hadn’t hit yet, but firmware updates at the time weren’t really something people thought to ever do, and operating systems did not check for them automatically back then like they do now.
Seagate fucked up but they also did everything they could to make it right. That matters. Plus, look at their competition. WD famously lied about their red drives not being SMR when they actually were. And I’ve only ever had WD hard drives and sandisk flash drives die on me. And guess who owns sandisk? Western Digital!
I guess if you must go with a another company, there’s the louder and more expensive Toshiba drives but I have never used those before so I know nothing about them aside from their reputation for being loud.
but then wd and their fake red nas drives with smr tech?
what else we have?
Wait.. fake? I just bought some of those.
they were selling wd red (pro?) drives with smr tech, which is known to be disastrous for disk arrays because both traditional raid and zfs tends to throw them out. the reason for that is when you are filling it up, especially when you do it quickly, it won't be able to process your writes after some time, and write operations will take a very long time, because the disk needs to rearrange its data before writing more. but raid solutions just see that the drive is not responding to the write command for a long time, and they think that's because the drive is bad.
it was a few years ago, but it was a shitfest because they didn't disclose it, and people were expecting that nas drives will work fine in their nas.
Didn't they used to have only one "Red" designation? Or maybe I'm hallucinating. I thought "Red Pro" was introduced after that curfuffel to distinguish the SMR from the CMR.
I don't know, because haven't been around long enough, but yeah possibly they started using the red pro type there
I've had a couple random drop from my array recently, but they were older so I didn't think twice about it. Does this permafry them or can you remove from the array and reinitiate for it to work?
well, it depends. if they were dropped just because they are smr and were writing slowly, I think they are fine. but otherwise...
what array system do you use? some raid software, or zfs?