August 24, 20241 yr Diagnostics attached. This has happened three times now, where I'll get a bundle of read errors, and it has only happened with these drives so far. The first time it happened was with a single 12 TB drive that I assumed was just defective and swapped for a Seagate of the same capacity. A couple of months later I picked up three 18 TB drives of the same model, two for parity and one for data, to start upgrading my array disk sizes. A week after installation it happened with the one that was assigned to data (two months ago). It had clear SMART data so I ran it through another preclear cycle to make sure it was actually working okay before reassigning it to the array. All has been well since then. This morning I awoke to both parity disks in a failed state and both showing 80 read errors. It may bear mentioning that the first time this occurred was with an LSI 9300-16i HBA in IT mode that has since been replaced with an integrated Intel JBOD-only SAS HBA. I can't recall offhand which LSI chipset is in the new HBA, but it has no RAID capability. While it's certainly possible that both HBAs had issues, it's unlikely that both would only affect a specific brand of drive. Thank you all so much in advance for your help! glizzyxl-diagnostics-20240824-0612.zip
August 24, 20241 yr Community Expert If you can retest with those disks connected to the onboard SATA controller.
August 24, 20241 yr Author Hi @JorgeB Thank you for the response. They aren't SATA drives so that won't work.
August 25, 20241 yr Community Expert Sorry, missed that, in that case I would remove the SAS spin down plugin, or report the issue in the plugin support thread, it doesn't work correctly with all SAS drives.
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.