November 10Nov 10 Smart report say good when i run it. they are my two oldest disk on the array tower-smart-20261110-0951.zip
November 10Nov 10 Author Sorry i have to admit this array has been pretty reliable for the past 4 years tower-diagnostics-20261110-1032.zip
November 10Nov 10 The disks are fine, SMART is clean on all of them. The errors are always on the three ST8000VN004 IronWolf disks (disks 2, 3 and 4). When they are spun down and something reads from them, they take more than 15 seconds to spin up on the LSI controller. A power-state check sent to the disk times out during the spin-up, the controller resets the disk, and the reads that were waiting fail.On Nov 7 this happened to disk3. Unraid then tried to read the data from parity, but that needed disk2, which was also spun down and failed the same way. With single parity, two disks failing in the same stripe can't be corrected, so both disks show read errors. Nothing was written, so no disk was disabled and the data on the disks is fine. If something was reading or copying files at about 19:08 that day, it may have gotten a read error, so just retry it.These IronWolf models are known to have issues with LSI HBAs when Low Current Spinup and EPC are enabled. You can disable both with Seagate's SeaChest tools, see here: [SeaChest guide link]. Do this for those three disks only. As an alternative, set the spin-down delay for those three disks to Never.The error counters will reset the next time you reboot.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.