[SOLVED] WD vs Seagate barracuda 4tb HDD reliability?

Jeff_120

Honorable
Dec 11, 2016
330
8
10,795
Hello
As my Seagate Barracuda 4tb bought 15 months ago is failing (slower and slower), I am searching for the best replacement
Unfortunately we don't have but this choice in my country:
-WD Blue 4tb WD40EZRZ
-WD Purple 4tb WD40PURZ
-WD Red 4tb WD40EFRX / WD40EFAX
-
Seagate 4TB ST4000DM004

I know the Seagate is the fastest one, but I need a drive that won't fail after a year
Usage: Raw photos and videos backup as well as some not very demanding games

So what to pick?
 
Solution
WD's 4 TB drives have mixed in newer SMR drives with earlier CMR models...

I think I read that all drives 6 or 8 TB and larger were CMR, ending the concern over the CMR models' 13-24 hour rebuild times.
Ive been running a WD 6TB red since 2018 that holds all of my steam games, I also have 2 WD 6TB red pro that hold movies and ISO copies of older computer games. All 3 of these drives live in my desktop computer that is left on 24/7.

The steam library and some other stuff from the other 2 drives all get backed up to another computer running 3 8TB seagate Ironwolf drives in raid 5. So far the 3 Ironwolfs have only been spinning for 3-4 months but they dont have any issues.
 
  • Like
Reactions: Jeff_120

Jeff_120

Honorable
Dec 11, 2016
330
8
10,795
My actual HDD Barracuda is very weird, one day it's getting so slow that it's nearly unresponsive, and one day it's back to normal, yesterday night it was back to normal. Though there was an update of Win 10 update if it could explain it
 

img

Prominent
Dec 27, 2020
48
2
565
Based on the collective experience , every manufacturer has better and weaker series (actually, manufacturers produce only few types due to production optimization, and then sort them in tests to see which piece gets which label): of the WDs, Gold, RED and RED Pro are the most reliable, most frequently those (Green and Blue) dies out of all WDs whom designed for office work (just 8 hours a day, only with few on / offs), with Purple falling between the former two groups. In my servers e.g. I only use REDs (32 of them in the last 8 years) and none have ever died before (OFC I disabled the agressive head parking and they're on UPS).

Seagate far worse than any WD despite of the fact there is a typical WD and Seagate HDD disease, a slowdown (named "slow responding issue" - usually it has one or more weak heads and the resulting unstable / bad sectors that are diligently collected by the firmware and this slows down the drive - i.e. the firmware overrides certain processes - like read / write operations - because sector list data cannot be updated), what is the first user noticeable sign of the dying drive: weak heads constantly developing bad sectors, if one or more of them in the disk's Service Area named "SA" (where the neccessary informations stored to up & running the drive itself), various problems can occur. When they start to slow down noticeably it means their end, because under the hood, only the "chewing gum" holds them together: they are probably full of bad sectors, but the firmware can still replace them from the spare area for a while. In this case (using home methods), your drive can't stand a full user data area backup. If the drive has not stopped completely, with special software like PC3K can be used to disable the weak heads and turn off realtime error-correcting background processes, thus speeding up the drive, then with the good heads can make a disk image copy of the sectors covered by them at normal speed, and then by switching the faulty heads back on, one can also try to save it's sectors. Thus, by putting as little stress on the drive as possible, there may be a minimal chance of recovering the data without breaking it and replacing the head block (because that would make it significantly more expensive - unfortunately, the heads have often been degraded to such an extent that the replacement cannot be swept away).

HDDSuperclone (it runs in Ubuntu too like DDRescue) has script to manage WD's slow responding issue, but sadly not working on newer drive families.