Since I changed from my virtualised UNRAID in ESXI to plain UNRAID I am having read errors across my drives in the array (XFS) when performing a parity check. Probably caused by a hard reboot I had to perform when UNRAID froze up on me. All disks are connected to a HBA M1015. Legacy from being on ESXI.

 

I am breaking my head around this, especially as I never faced these errors before and can't get around them. At this moment the parity is rebuilding by performing a new config. Before rebuilding the parity disk I initiated a SMART test. All disks passed the short and long SMART test. No raw read errors, or pending / reallocated sectors. I do have a high UDMA CRC Error Count. No clue what this entails. Additionally I performed a file system check. Nothing needed to be corrected.

 

I powered down the system and checked the cables. All seem to be in order.

 

Can anyone point me in the right direction? No clue how to resolve this issue.

 

Thanks

syslog.zip

Seems like I solved the issue. Reverting the HBA back to LSI software P19 did the trick for me.

Not only did the parity speed go up, so far no read errors! Seems like UNRAID or "Linux" does not go will with the P20 update.

You did not mention that you flashed to P20 in your OP.

Issues with P20 are already known.

http://lime-technology.com/forum/index.php?topic=12767.msg339192#msg339192

In my Esxi build i did not face the problem with P20, reverting to plain unraid killed it.

OK, good to know.

Obviously an issue with the unRAID driver then.