Back Blaze said that firmware caused a lot of those Seagates to fail, but they also said they didn't count drives that failed during their ~3 weeks of initial testing. So does that mean those Seagates had an even higher failure rate, or does it mean Back Blaze's initial testing isn't very good?
| Processor | AMD Ryzen 7 7800X3D |
|---|---|
| Motherboard | ASUS TUF x670e |
| Cooling | EK AIO 360. Phantek T30 fans. |
| Memory | 32GB G.Skill 6000Mhz |
| Video Card(s) | Asus RTX 4090 |
| Storage | WD m.2 |
| Display(s) | LG C2 Evo OLED 42" |
| Case | Lian Li PC 011 Dynamic Evo |
| Audio Device(s) | Topping E70 DAC, SMSL SP200 Headphone Amp. |
| Power Supply | FSP Hydro Ti PRO 1000W |
| Mouse | Razer Basilisk V3 Pro |
| Keyboard | Tester84 |
| Software | Windows 11 |
| Processor | Intel Core i7 10850K@5.2GHz |
|---|---|
| Motherboard | AsRock Z470 Taichi |
| Cooling | Corsair H115i Pro w/ Noctua NF-A14 Fans |
| Memory | 32GB DDR4-3600 |
| Video Card(s) | RTX 2070 Super |
| Storage | 500GB SX8200 Pro + 8TB with 1TB SSD Cache |
| Display(s) | Acer Nitro VG280K 4K 28" |
| Case | Fractal Design Define S |
| Audio Device(s) | Onboard is good enough for me |
| Power Supply | eVGA SuperNOVA 1000w G3 |
| Software | Windows 10 Pro x64 |
Another issues with BackBlaze's study is the testing method, or rather what they consider a "failed drive". To them, a drive has failed when it starts generating RAID errors. But a RAID error can be caused just by the drive taking too long to respond to a command, which wouldn't matter in a desktop environment. That doesn't mean a has actually failed, but to them and their study it does.
