Everything was fine until i do a full parity check.  First time it cam back with 1000000s of read only errors on pairty drive #2. Fine RMA'd the drive awaiting return. Ran another pairty check hard lockup, same thing this morning. The only recent change was adding a 10G nic which has been working fine. Logs are not helpfull due to the hard lockup. Any thoughts? I am currently removing the 10G card and going to re  run the checks........... But a NIC shouldnt be hardlocking the system over a pairty check.

 

Edited April 22, 20215 yr by pyrater

Ok not sure what's going on. Replaced the disk and started a new party rebuild and the now brand new disk has 4000+ errors. Can anyone please take a look at the attached logs. 

icarus-diagnostics-20210422-2001.zip

Disk looks OK, replace or swap cables/slot with another disk and try again.

Jorgeb ty. Do you think it's nic related to the 10g?https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/page/4/?tab=comments#comment-14426

Just took the 10G card out to rule that out. Now i randomly have 3 disk with errors? icarus-diagnostics-20210422-2038.zip

24 minutes ago, pyrater said:

Do you think it's nic related to the 10g?

Not the disk errors, looks like disks 9 and 10 dropped offline.

 

 

Ok i just checked and Pairty Disk 2, Disk 9 and 10 are all on the same breakout cable from the HDD controller Card. So i added a New cable to a new sas port to those drives. Maybe bad controller? Maybe Bad Cable? Maybe Bad Power?

I started getting read errors all over the array. I started to suspect the LSI00244 9201-16i expander card. I have since replaced the card with 2 8X cards and i am running a parity check. Checked all cables and connections. Heres to hoping its just that card.