February 2, 20251 yr Hey everyone! I moved over to Unraid a couple months ago, and everything has been going really smooth. About 2 weeks ago I woke up to a notification that a parity check was started, which seemed strange since it wasn't following the schedule I had set. I found out that the server had an unclean shutdown which caused the parity check to start on boot. I checked my UPS to see if there was a power failure that caused the shutdown, but didn't see anything. Around a week later I had the same issue, and learned that I should enable the Syslog Server so if it happens again, I can try to figure out the issue. This morning I woke up to all of my docker containers being down, and the docker service failed to start after another unclean shutdown. It looked like my docker.img was corrupt so I removed that and got everything back up and running. From this mornings unclean shutdown, I did get a syslog-previous file, but it doesn't seem like a new diagnostic.zip was generated. I've attached the syslog-previous here. Is anyone able to take a look to help figure out what's causing the unclean shutdowns? syslog-previous
February 2, 20251 yr Author 26 minutes ago, trurl said: Attach Diagnostics to your NEXT post in this thread. Sorry, I thought diagnostics were automatically generated and didn't see anything in my /log folder. Just created a new one. cz-server-diagnostics-20250202-1237.zip
February 2, 20251 yr Community Expert Any idea why these are spamming your syslog hundreds of times per second? Feb 2 10:57:54 CZ-Server sshd-session[16435]: Starting session: command for root from 192.168.86.32 port 47622 id 0 Feb 2 10:57:54 CZ-Server sshd-session[16435]: Starting session: command for root from 192.168.86.32 port 47622 id 1 Feb 2 10:57:54 CZ-Server sshd-session[16435]: Close session: user root from 192.168.86.32 port 47622 id 1 Feb 2 10:57:54 CZ-Server sshd-session[16435]: Close session: user root from 192.168.86.32 port 47622 id 0
February 2, 20251 yr Author Hmm, possibly the Home Assistant Unraid integration: https://github.com/domalab/ha-unraid But that's set to refresh sensors every 5 min so it might be something different. How can I identify where that's coming from?
February 2, 20251 yr Author 192.168.86.32 is my Unraid server. I just went and disabled the integration in Home Assistant and it's been a few minutes since that line has shown up, so most likely that was the cause for those logs.
February 2, 20251 yr Community Expert Is the server rebooting itself? Is your BIOS set to restart when power is restored?
February 2, 20251 yr Author I also have my UPS integrated into Home Assistant and don't see any events where it switched to battery. Are you seeing a power loss in the Unraid logs?
February 3, 20251 yr Author Just ran into the same issue. Seems to be happening more frequently. Attached the latest diagnostics. cz-server-diagnostics-20250203-1640.zip
February 4, 20251 yr Author It's enabled. It doesn't look like it added anything to the diagnostics this time though. I've attached it here. syslog-previous
February 4, 20251 yr Community Expert You need to set the IP address, it can send it to another or it can send it to itself.
February 4, 20251 yr Author Didn't realize I had to set that up. I guess ill need to let it run until the problem happens again?
February 4, 20251 yr Author Just had another unclean shutdown. The syslog is attached. For reference, the parity check after boot started at 1:13 PM if that helps to track down the issue. syslog-192.168.86.32.log Edited February 4, 20251 yr by czonin
February 5, 20251 yr Community Expert 9 hours ago, czonin said: Just had another unclean shutdown Do you mean the server is rebooting by itself?
February 5, 20251 yr Author 4 hours ago, JorgeB said: Do you mean the server is rebooting by itself? Could be. Not sure why that would happen though.
February 5, 20251 yr Community Expert Check the uptime, if it's lower than you expect, it means the server is rebooting, and that is almost always a hardware problem, or bad power.
February 5, 20251 yr Author 8 minutes ago, JorgeB said: Check the uptime, if it's lower than you expect, it means the server is rebooting, and that is almost always a hardware problem, or bad power. Right. I thought you meant that Unraid was triggering a reboot. It's definitely being restarted one way or another. Hardware is what I was starting to think. First thing that came to mind was the PSU if the system is just shutting down.
February 5, 20251 yr Author Looking at the latest syslog that I attached, it basically just looks like the session ends and then we see the server start up right? There's no indication from Unraid that something is going wrong before the restart.
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.