NPole49

I am newb, I shutdown and rebooted after changing a cable out that seemed to be bad, no drives were tied to this cable at this point, server was running flawless and just finished parity ck 2 days ago w/zero errors. rebooted, two exiting drives disabled/emulated, 2nd parity gets read error. Log show's a disk 29 with read errors..........I only have 24 drives total in this system (parityx2, datax22) here is snipit of log: Oct 11 20:19:31 TheCanik kernel: md: disk29 read error, sector=2930425160 Oct 11 20:19:33 TheCanik kernel: md: disk29 read error, sector=976830608 Oct 11 20:19:35 TheCanik kernel: md: disk29 read error, sector=976766192 Oct 11 20:19:36 TheCanik kernel: md: disk29 read error, sector=3907129048 Oct 11 20:19:37 TheCanik kernel: md: disk29 read error, sector=3907121768 Oct 11 20:19:38 TheCanik kernel: md: disk29 read error, sector=3907200720 Oct 11 20:19:39 TheCanik kernel: md: disk29 read error, sector=3907283168 Oct 11 20:19:40 TheCanik kernel: md: disk29 read error, sector=3907211344 Oct 11 20:20:00 TheCanik kernel: md: disk29 read error, sector=3907099880 Oct 11 20:20:01 TheCanik kernel: md: disk29 read error, sector=2930425168 Oct 11 20:20:03 TheCanik kernel: md: disk29 read error, sector=976830616 Oct 11 20:22:13 TheCanik nginx: 2022/10/11 20:22:13 [error] 5099#5099: *6733 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.167, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket/update.htm", host: "192.168.0.144", referrer: "http://192.168.0.144/Main" my 2nd parity shows in unassigned devices: Of course I'm lost on this....thx in advance