Likely WD140EDFZ or WD140EDMZ. As good as any for NAS usage imo. Some good information here: https://www.reddit.com/r/DataHoarder/comments/edhzsvWhat drive is actually inside one of these? Would it be good for NAS usage if I shuck it?
Likely WD140EDFZ or WD140EDMZ. As good as any for NAS usage imo. Some good information here: https://www.reddit.com/r/DataHoarder/comments/edhzsvWhat drive is actually inside one of these? Would it be good for NAS usage if I shuck it?
Do you know if these 14TB drives have 512mb cache?Mine were all WD140EDFZ . All 8 tested fine with h2testw while in their USB enclosures.
Thanks. As far as I know my PSU is up to the latest ATX specs.@madbrain Check SATA plug specs and your cable if this one drive gets 3.3V on PWDIS pin. Test with a Molex to SATA power converter temporarily, drive should then spin up. Because Molex has no 3.3V just 5+12V. If that is the case you need a "3.3v pin mod" for this drive.
What is happening is that some shucked drives need this mod and some don't. The HDD's label will not show this in any way, have to test it. I ended up buying a spare PSU to 4x SATA cable and removed the 3.3v rail in a safe way (no chance for short circuit).
I believe all WD 14TB drives do.Do you know if these 14TB drives have 512mb cache?
That's awesome. I bought one last night and I was going to use another email for another one today but the steep discount is goneI believe all WD 14TB drives do.
Just watch the Best buy site around black Friday. They should have the same sale going again.That's awesome. I bought one last night and I was going to use another email for another one today but the steep discount is gone
I don't think Amazon has matched Best buy prices on these drives historically.Waiting for Amazon to match with the elements. Free global shipping and EMFZs instead of EDFZs
What's the difference between the two other than EMFZ doesn't suffer from the 3.3v issue?Waiting for Amazon to match with the elements. Free global shipping and EMFZs instead of EDFZs
I don't think the 3.3V issue has anything to do with the model. According to a poster above, it is random on certain drives. Out of 14 drives (6 x 10TB, 8 x 14 TB), I have one drive that presents something that might be this issue, but not confirmed yet.What's the difference between the two other than EMFZ doesn't suffer from the 3.3v issue?
They've sold the 12TBs $5 lower than BB's historical prices twice now.I don't think Amazon has matched Best buy prices on these drives historically.
The lack of TLER is a deal breaker on the EDFZ. People say you can write a script to turn it on every boot but I don't believe that a value that doesn't persist on reboot is actually being set at all.What's the difference between the two other than EMFZ doesn't suffer from the 3.3v issue?
Not sure why you would think that. It's pretty standard for firmware to keep state in RAM.The lack of TLER is a deal breaker on the EDFZ. People say you can write a script to turn it on every boot but I don't believe that a value that doesn't persist on reboot is actually being set at all.
Well you only know if the drive actually has TLER on failure and by then it's too late for your dataNot sure why you would think that. It's pretty standard for firmware to keep state in RAM.
Many others have been using various WD drives and setting various features on via smartctl for years, not just TLER.
ZFS and green drives/TLER
I'm setting up a NAS box based around freenas and ZFS. I've read lots of posts (like this one) about "deep recovery" and green drives when using RAID-5. Does ZFS (vs Raid-5) mean that this proble...serverfault.com
Well, the other values that are changed dynamically like sleep timeouts can be observed to take effect after being set via smartctl. I don't see any reason why the TLER wouldn't be the same. Certainly if you want to theorize that's the case, you should come up with some evidence to back it up. I don't have access to the WD firmware source to tell you. But as a firmware developer (though not HD firmware developer), I think it would be pretty shitty for the drive to accept a value and then just throw it away. The proper response would be to reject the command. Anything else would be a bug.Well you only know if the drive actually has TLER on failure and by then it's too late for your data
Like I said, there's no way to know if it works until a drive actually fails. I'm not very willing to risk my data or drives to test this so I'll just wait for the reports. I also have enough of 14TB EMFZs so no reason for me to gamble with my data. Hope it works out for you anyway.Well, the other values that are changed dynamically like sleep timeouts can be observed to take effect after being set via smartctl. I don't see any reason why the TLER wouldn't be the same. Certainly if you want to theorize that's the case, you should come up with some evidence to back it up. I don't have access to the WD firmware source to tell you. But as a firmware developer (though not HD firmware developer), I think it would be pretty shitty for the drive to accept a value and then just throw it away. The proper response would be to reject the command. Anything else would be a bug.
Even then, how would you prove a specific drive failure has anything to do with TLER not being enabled ?Like I said, there's no way to know if it works until a drive actually fails.