Hello everyone,

 

Recently a drive failed. I have a replacement and when I attempt to stop the array to replace the failed drive with the new one I see the following error in the log and the array will not stop.

 

Jan  5 12:14:33 BlackHole nginx: 2024/01/05 12:14:33 [error] 18699#18699: *6884397 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 10.10.20.20, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "10.10.20.12", referrer: "http://10.10.20.12/Main"

 

I have had an issue that I haven't found a solution to for a long time now. The array automatically goes into auto parity check after a power failure or reboot. I have found disabling the docker service and the VM manager prevents this from happening, usually. I like to disable these services when rebuilding a drive anyway. But, I am not sure what to do now. Of course I don't want to lose the data on the failed drive. And I cannot stop the array to replace said drive. I am also afraid to reboot the array with the for-mentioned error.

 

Diagnostic file attached

 

Thank you 

blackhole-diagnostics-20240105-1216.zip

I have noticed I get the above mentioned error when trying to, unsuccessfully, make changes in the array's settings. 

Do you have anything accessing the storage on the server? Do you have a command line open to the server?

I don't think there is anything accessing the storage drives. I disabled the docker and VM service. And there was no terminal open to the server.

 

Do you have an attached keyboard and monitor?

That is a negative.

 

But I just noticed the failed drive, disk 13 with the red X is also showing up under unassigned devices.

 

I have unplugged all devices aside from one desktop. I know there is nothing accessing the storage on the server. I still cannot stop the server and I still get the same error.

1 hour ago, elco1965 said:

just noticed the failed drive, disk 13 with the red X is also showing up under unassigned devices.

Not unusual. The disk disconnects (was sdh) which causes it to become disabled, then reconnects as a different device (now sdad).

 

You  could try disabling autostart then when you force reboot it should allow you to assign the new disk as disk13. Autostart is in Disk Settings. You can also edit config/disk.cfg on the flash drive to disable it.

 

Do you have a flash backup?

Its been a while since I made a backup. I was using unRAID Connect but had trouble with it also. I cannot change the Management settingd like UseSSL/TLS to Strict for manual port forwarding. The same error pops up in the log when hit apply. 

I get the same error as I try to change disk settings. Swapping auto start from yes to no will not take.

 

Jan  5 19:22:40 BlackHole nginx: 2024/01/05 19:22:40 [error] 3170#3170: *135011 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 10.10.20.20, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "10.10.20.12", referrer: "http://10.10.20.12/Settings/DiskSettings"

12 hours ago, trurl said:

You can also edit config/disk.cfg on the flash drive to disable it.

 

Sorry I missed that yesterday. 

 

I have navigated to flash/config/disk.cfg set start Array to no. When you say "force a reboot" do you mean via command line or the button on the mail page? I haven't tried the main page button yet but I am wondering if the array will respond and I will get the same error.

 

And thanks for your time. Your help is appreciated. 

13 minutes ago, elco1965 said:

"force a reboot"

I probably should have said "cold shutdown". The power button on the server. I doubt anything in the webUI or command line will behave any differently than the buttons in Main - Array Operation.

 

You might also check out this sticky which discusses the various timeout settings:

 

Thanks for the suggestion. I actually I saw that yesterday when I was searching the forum and attempted to make some changes but nothing I did in gui would take. I will take another look after the disk is rebuilt. 

trurl,

 

I have rebuilt the failed drive and made the changes as suggested in "Dealing with unclean shutdowns". The server now shuts down and restarts without error and does not initiate a party check once restarted. 

 

Thanks again for the help.