Jump to content

Parity check slow and lots of errors


Recommended Posts

Hello -   I run a parity check monthly, but this last one was taking a very long time to finish.  When I checked, it had been running for a little over 23 hrs and had over 500K errors.  I've since tried it a few more times and each one starts off with good speed, then drops way down.  All the the drives are not reporting any trouble and I've even tried stopping Docker thinking that may have something to do with it since I recently set it up.  I recently moved to new hardware (second time in 8 years), and nothing stood out - no errors, etc.  I did add a 10 GB network card, and the driver is throwing errors about the SPF module not being supported.  I asked our Linux administrator about it and his guess was that it wasn't configured to support generic modules, but that should not affect a parity check.


I appreciate any insight, and have attached a diagnostic log.





Link to comment
2 hours ago, trurl said:

Controller issue?


It certainly is, and I bet the reason is this:

03:00.0 RAID bus controller [0104]: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller [1b4b:9485] (rev c3)
	Subsystem: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller [1b4b:9480]
	Kernel driver in use: mvsas
	Kernel modules: mvsas

The mvsas driver is broken under unRAID 6 (maybe it was the move to 64-bit) and Marvell HBAs are generally problematic. The symptoms are that disks randomly get disconnected. It's often worse if you have IOMMU enabled but the workround of disabling IOMMU doesn't seem to work any more. You really need to replace it with a card based on an LSI controller. This issue crops up time after time and I've been affected by it myself. I replaced my Marvell controllers with Dell Perc H310s bought second hand on ebay (quality server pulls) and cross-flashed to LSI/Avago/Broadcom IT mode.

Link to comment


This topic is now archived and is closed to further replies.

  • Create New...