I have so many issues right now with those drives. I guess it is a firmware bugs that make the drive crash, but the drive just disconnect themselves and my pool disappear without any reason. Even after rebooting they aren’t coming back up.
What I tried :
In a shelf netapp ds2246 connected on a H310 HBA, I also tried with a lsi 9207-8e, also using different cables, using (freenas or fedora) zfs raidz1, in all the cases, I had the same issue.
I also tried to connect the drive directly to the sas card thinking the issue would come from the shelf at first. I used SFF 8088 to SATA cables, same issue.
Then, I tried to use hardware raid so I install the drives in a Dell r620 using a H710 mini in raid 5 and drives became unresponsive after initialization is done.
I think I tried all the possible configuration and each time the drives were not stable.
The only time I was able to get it stable was if I connect all the drives directly to the motherboard.
I installed windows to test the drive with the seagate tool using the H310, lsi and direct connect to motherboard.
With the sas controller, some of the test was failing (it was pretty much random on which drive) and connected to the motherboard, it was fine. In all the test, it never looked like I had bad sectors…
Anyway, I will try to call seagate support and see if I can exchange the firecuda for normal barracuda. I guess making a drive with integrated caching need a lot more work in the firmware than a normal harddrive and clearly they didn’t test all the possible cases with that drive…
Any of you had similar experiences? It took me months to really try all the possible tests all of my other drives are perfectly stables in all the cases, only firecude are giving me hard time.