eevblog.com/…/whats-behind-the-infamous-seagate-b…
this thread has multiple documented instances of poor QA and firmware bugs Seagate has implemented at the cost of their own customers.
my specific issue was even longer ago, 20+ years. there was a bug in the firmware where there was a buffer overflow from an int limit on runtime. it caused a cascade failure in the firmware and caused the drive to lock up after it ran for the maximum into limit. this is my understanding of it anyway.
the only solution was to purchase a board online for the exact model of your HDD and swap it and perform a firmware flash before time ran out. I think you could also use a clip and force program the firmware.
at the time a new board cost as much as a new drive, finances of which I didn’t have at the time.
eventually I moved past the 1tb of data I lost, but I will never willingly purchase another Seagate.
skankhunt42@lemmy.ca 2 days ago
In my case, 10+years ago I had 6 * 3tb Seagate disks in a software raid 5. Two of them failed and it took me days to force it back into the raid and get some of the data off. Now I use WD and raid 6.
I read 3 or 4 years ago that it was just the 3tb reds I used had a high failure rate but I’m still only buying WDs
HiTekRedNek@lemmy.world 2 days ago
I had a single red 2TB in an old tivo roamio for almost a decade.
Pulled out this weekend, and finally tested it. Failed.
I was planning to move my 1.5T music collection to it. Glad I tested it first, lol.
keen@lemmy.world 2 days ago
Thanks, yeah that makes sense.