January 16, 20251 yr Freshly upgraded to 7.0.0, brand new problem. Couple days ago I upgraded the parity disk. Got it fired off on the GUI and walked away. Came back a bit later to check progress and disk temps, GUI was non-responsive. Tried to SSH in, unable. Opened the console and the keyboard did not work. The disk activity lights were still going, so it looked like the rebuilt was still going... I decided to try to re-do it and pressed the power button on the front of the machine. I got the initial runlevel 6 message and then the system paused (see pic). I gave up an walked away, hoping the disk rebuild would finish. I came back two days later and the system had rebooted, the parity disk had been rebuilt, and when I started the array it wanted to do a parity check ala unclean shutdown. I aborted it as I wanted to do another disk upgrade. I have now started a disk upgrade, and the system is now once again full hanged. No ssh, no web, but it will respond to ping. I am going to blindly let the disk rebuild continue because I see the array activity lights are all going. So bottom line... 90% system hang during disk rebuilds. And ideas?
January 16, 20251 yr Community Expert 10 minutes ago, tucansam said: the system had rebooted If it rebooted itself probably a hardware problem. Attach Diagnostics to your NEXT post in this thread. Could be they were written to flash during shutdown.
January 16, 20251 yr Author It didn't reboot itself. I pressed the power button to initiate a shutdown and it waited until after the parity disk was rebuilt and then followed my command. I won't be able to post diags until after this next disk rebuild is done. No hardware has changed except the new disk, which was verified good as it came from another system.
January 16, 20251 yr Community Expert It may write diagnostics to flash before shutdown, so see if you can get those.
January 17, 20251 yr Author Diags for the first server attached, that seems to have "woken up" on its own and is now responding to the usual. The disk rebuild finished during the night, so maybe that's when it woke up. No reboot occurred, it just started responding again once the disk rebuild was done. BUT It is now giving me "out of memory" errors, and my primary server is too (and has been for over a year, I have a thread about it). 'FFS1' is running a small number of plugins and one docker, which is rarely turned on (and was not on when the errors started). 'FFS2' is running a lot of plugins and dockers, and everything is memory-limited by the docker. Furthermore, at no point have I ever checked on either server and seen more than a few GB of RAM in use at the most. Diags for both attached. ffs2-diagnostics-20250117-1102.zip ffs1-diagnostics-20250117-1100.zip
January 17, 20251 yr Author Original server mentioned is in the middle of a rebuild and is not responding to web or ssh traffic again.....
January 17, 20251 yr Author All memory in use and a pegged CPU and a sysload I've never seen all for a disk rebuild.
January 17, 20251 yr Author BTW the console is frozen so htop wasn't updating in realtime so I have no idea what the system looked like in that instant.
January 22, 20251 yr Community Expert If it's still happening, enable the syslog server and post that after a crash/hang.
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.