Smart errors, packaging problems
I've never had 100% failure rates on brand new drives like this, but here we are. I bought four of the 6tb ironwolf drives. Plugged them into my nas and right off the bat, one of them was completely doa - didn't spin up, was never recognized by the server, just sat there and made a repetitive beeping noise. I exchanged it to outletpc. The meantime i was running nwipe on the other three drives. Keep in mind that these are on the same controllers, cables, and everything else as my existing hard drives. Nwipe was crawling along at about 2mb/sec on each drive, and they were all adding up huge numbers in the ecc right counter in smart. When i received the replacement for the first dead drive from outletpc and subjected it to the same test, it as well had the same result.Just to rule anything else out, i make a raidz zpool on the four drives and started writing to it. After about a minute or so it bottomed out in the 5-10 mb/sec range, and the smart errors kept piling up.At this point i split my losses, wiped the partition tables, and returned them to outletpc. When packing them up for return i noticed that seagate's single-drive packaging allows for an alarming amount of longitudinal movement. The drives are secure along the two short axes, but it can slide in the box at least a centimeter back and forth, even with everything snugged up as tight as the box will let it. So i'm not sure if this is a poor product design or even worse packaging, because i've never had drives shipped to me with the ability to move that much.Oh, and just to make everything even more annoying, these drives don't have the middle set of holes on either the side or the bottom. Makes it a pain to mount in most cases.7/11 followup: i received my replacement drives from another manufacturer, and installed them in the exact same sleds / slots as the ironwolf drives, just so i could completely rule out any chance of a cable or controller issue. They have performed flawlessly. The drives i received had manufacture dates of both 3/2017 and 6/2017, so they weren't even from the same batch. I don't know what made them act up, but i definitely wouldn't buy these again.