I lost 2 data disks and I precleared the replacements and I am getting read errors during the rebuild, i then did a extended smart test on each of the drive in my array including the parity drives. Now it is stuck trying to doing a "read-check" and is not responding when i try to cancel it or stop the array.

 

I am getting this in syslog

 

nginx: 2024/03/22 12:11:32 [error] 13191#13191: *3434928 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.1.73, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "192.168.1.200", referrer: "http://192.168.1.200/Settings/ManagementAccess"
Mar 22 12:11:34 Fury nginx: 2024/03/22 12:11:34 [error] 13191#13191: *3437484 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.1.73, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "192.168.1.200", referrer: "http://192.168.1.200/Settings/ManagementAccess"
Mar 22 12:12:01 Fury Parity Check Tuning: DEBUG:   Automatic Read-Check paused

 

 

Attach Diagnostics to your NEXT post in this thread.

added diagnostics

fury-diagnostics-20240322-1246.zip

Disk2 disconnected (as sdh) and reconnected as Unassigned Device (sdr).

 

Syslogs flooded with those errors you posted so can't see much else, including what disk should have been Disk5. Doesn't look like it is showing up at all.

 

Both emulated disks seem mountable, but looks like emulated disk5 may be empty. Did you format?

 

Looks like you are trying to use USB for many of these. USB connections are NOT recommended for assigned disks for many reasons, including the disconnects you are getting.

 

I doubt you will be able to get this many disks as a stable array as long as you are using USB.