I can not longer reboot or shutdown my server gracefully. I am also unable to stop the array. I have been able to stop all of my docker containers and my vms. I can flag them not to start automatically too. However, I cannot turn off docker, it just spins. I also cannot download my trouble shooting log. It's been sitting here for 30 minutes (see attached).

 

I noticed this issue yesturday. I shutdown by holding the power down. Then on again. 19 hours later with a clean parity rebuild, I'd rather not do that again. I have direct access. I've tried doing various versions of "reboot -f" Including just ctrl-alt-del which gives "The system is going down for reboot NOW!" but it never does. Even left it for an hour at that state. Nothing.

 

The Dashboard reports very high CPU usage, though htop does not seem to agree. Any ideas?

 

Thanks

kill that shfs process ( usually signal -9 is needed, the atomic bomb) 11308. Then the machine will shut down again normally.

Update to 7.1-rc the problem might be fixed there already.

(At least what I had was close to yours, so there is a good chance that the patch will work for you too)

 

Thanks for the quick response. I was out for a minute. I have now tried

 

killall -9 11308

 

It went away, but I still can't stop the array or reboot. I also tried running an OS update, just to 7.0.1. Just hangs. Now I probably did more damage! At least there are no more shfs processes running that I can find.

 

I hard shutdown again, as in pushed the butten till dead. I thought I had disabled "auto start" for the array. I had not, so it's rebuilding parity. At least none of my docker containers started, nor did my vms. So it's almost "clean". In 20 hours I'll try stopping the array. I'll follow up with anything else, but I will not try anything else till the parity check is done. Thanks.

 

Edited April 21, 20251 yr by kteach
Just more information.

waiting 20hrs wont help you I am afraid. Its just a check, it does not fix anything.

You better should think about the real problem that is going on.

(BTW, you might have disabled autostart, but that is not written to the stick until you do a graceful shutdown.)

Take a diagnostics and show it here. maybe there is something in there that can be found.

Fair enough. I guess I get a little paranoid with data. Rebuilding a server is easy. Getting my created content back is tough. Yes, I have it backed up off this, but it's still tough! If you recall, I started by trying to run a Diagnostics and it was just "hung". Good news. Now, after the forced restart, not only has the CPU settled down, I was able to complete a Diagnostics. I've attached.

kon-bee-diagnostics-20250421-1246.zip

It is clearly related to try to update to 7.1. Each time, the CPU pin to max as shown, and it refuses to reboot. I left it in that state for 18 days. Nothing changed. I'll just keep running 7.0.0 for now. Wait for another release and try then.