September 4, 20241 yr So I have a weird problem. My parity drive got disabled due to read errors; this was due to a bad connector, and I have fixed the issue. But because the drive was disabled, I had to mount it and do the parity check again. I started the check over 2 days ago, and it was doing fine. But now all the numbers for Parity-Sync progress have been stuck except elapsed time, and when I try to pause the parity check, it does nothing. All the other information (read/write speeds, cpu usage, temps) changes and updates. I get the following error after about a minute in the logs: Sep 3 11:51:10 Tower nginx: 2024/09/03 11:51:10 [error] 22002#22002: *719411 upstream timed out (110: Connection timed out) while reading response header from upstream, client: cip, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket/update.htm", host: "hip", referrer: "http://hip/Main" I can't find a similar problem online. I hope someone can help me? See diagnostics below. tower-diagnostics-20240904-0832.zip
September 4, 20241 yr Community Expert The parity check is not advancing, you can type reboot in the CLI and then start over.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.