Seagate IronWolf, 8 TB, NAS, Internal Hard Drive, CMR, 3.5 Inch, SATA, 6GB/s, 5,400 RPM, 256MB Cache, for RAID Network Attached Storage, 3 year Rescue Services (ST8000VN004)

Product Information

I didn’t get around to testing this but it did help in getting more information! More hints appear… During the first scrub ZFS found some CRC errors but I believe those to have been caused by the issue earlier and that those just hadn’t been fixed yet, I was able to run the 2 scrubs mentioned above after fixing those. Working for me! Moving on and building my 8x10TB Seagate IronWolf ZFS Mirror pool like discussed in this video, all worked well and thus I started moving over my data. I just created POOL in raid 5 with 5 disks and started to copy data. This happened in first 8 hours of drive working. I performed several scrubs and while no data was lost or corrupted, each time one or more disks would generate some amount of CRC errors just like my friend had been having! What is going on here….. LSI/Avago controller related? Per disk chance?

I have same problem with completely new Seagate IronWolf NAS 8Tb drive ST8000VN004, dropping disk from ZFS on Qnap TS-h973AX NAS. I am running SeaTools for Windows on other computer and everything looks good, but NAS marked my drive with Warning, to many S.M.A.R.T. errors “Uncorrectable sector count”. IronWolf Health Management (IHM) is an embedded software designed on the tenets of prevention, intervention and recovery. It aims to manage the health of the drive through the useful life, and provide ease of data recovery should a catastrophic event damage the drive and render it non-functional. Tough. Ready. Scalable. So I am as of yet still unsure if it is LSI controller related or not. I’m inclined to say yes, but I am not 100% sure. Also I’m not sure if it’s only certain disks that show this problem and others don’t. That would concur with what I’ve seen but that’s still a weird conclusion.Probably what you have been waiting for, this issue has been fixed in a new SC61 firmware that Seagate has released. All Seagate IronWolf 10TB drives I have ever received, even the examples I bought recently came with the SC60 firmware. For myself I am now running for about a month with the new firmware and having done lots and lots of tests during that period not a single error has occurred anymore so I believe the new SC61 firmware fixes this issue for good. Also important, I have noticed no negative side affects regarding this new firmware, speed and everything else is still great! Upgrading your own drives Ok, to make sure this is actually a fix working for everyone I created the before mentioned ixsystems.com post. What I do know for certain is that the errors occur while the disks are connected to these controllers while otherwise these controllers are held in high regard as functioning well. Potential Workaround “Fix” The Seagate ST8000VN004 IronWolf 8TB SATA Hard Drive is optimised for NAS in multi-RAID environments and can handle both the vibration and the high user workload rate in a high data traffic network. With this Seagate ST8000VN004 IronWolf drive you can get used to tough, ready and scalable 24/7 performance that can handle multi-drive environments. Vital Statistics

I’ve been using Seagate IronWolf disks for a few years now and currently have about 20 in service, most of those are the 10TB (and 12TB) Non-Pro (ST10000VN0004) variety. Most of my experience with them has been great so when the new server build came along I bought a few more to run as my main ZFS pool. Sadly, things didn’t go exactly as planned, but I think I was also able to fix it, so let’s see what happened! I haven’t been able to form a 100% certain answer to this question. With my friend I believe we tested motherboard ports and LSI ports and he would always have these errors and in my old server I believe the disks where also connected to my LSI controller and there I had 0 issues.Cảm biến rung động quay (RV). Đầu tiên trong lớp ổ cứng của nó bao gồm các cảm biến RV để duy trì hiệu suất cao trong các vỏ NAS nhiều ổ. 3 A potential fix was presented again on the ixsystems forum. One of the forum members had figured out he would no longer have issues if he disabled NCQ for the disks. This was something that had to be done each boot but could be scripted. If this worked that would be great, without NCQ performance would be a bit lower, but ok. Seemingly this had been going on for a while but recently someone from Seagate started replying to the topic and recently it was mentioned that new firmware was now available after which, combined with a Synology update, would re-enable the write cache and fix this issue on these drives. The actual Fix! The exact issue was described as “flush cache timing out bug that was discovered during routine testing”. Hmm, that sounds a lot like the same issue as several members on the ixsystems and on reddit where describing and also what I’m seeing in my logs! Sat Jan 1 21:51:17 2022] sd 0:0:6:0: [sdg] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK

Represents an improved total cost of ownership (TCO) over desktop drives with reduced maintenance costs. AgileArray enables dual-plane balancing and RAID optimisation in multi-bay environments, with the most advanced power management possible.During this move however errors started popping up. The disks where in the hot swap bays of my new server and connected to one of two LSI SAS2008 based cards running the newest 20.00.07.00 firmware. After migrating about 20TB of data I was left with the following: As far as is known by me right now is that this issue only occurs with the 10TB variant of these drives, but if you have a different experience, please make sure to comment!

After flashing one of the disks I started a scrub and ZFS found no issues with the data still on the drive, ok! So I flashed all my disks and was able to start my pool normally without any data loss so I started testing. Before writing this post about this issue I started a topic on ixsystems.com since there where several post describing this problem already. Since writing there I believe enough information is now known that I can “release this to the public”. If you are looking for a condensed version take a look at the link (It’s the forum post). The topic might also contain some extra information not in this article. Full article but also in video formSat Jan 1 21:51:17 2022] sd 0:0:6:0: [sdg] tag#0 CDB: Read(16) 88 00 00 00 00 01 9c 00 28 40 00 00 00 08 00 00 Before using any disk I subject them to a full verify pass using a separate PC. This is a full 14Hr pass of HDAT2 which verified that each disk was 100% ok before using it. Actually, I’ve never had one of the Seagate IronWolf 10TB or 12TB disks fail me in this test or during service, QC in the factory must be really good (I’ve had different experiences with other brands). As you can see I had write errors on several disks. These didn’t all happen at the same time but over time while I was copying.