Hi,

 

I woke up this morning (late, due to no alarm) and realized pretty quickly Home Assistant wasn't running. In fact, my unraid array wasn't started, and so all my Dockers weren't running. It looks like the unraid server rebooted itself just before 4 AM. My mover runs nightly at 2 AM, and my backups run on Mondays so it wasn't that. How can I go about diagnosing what caused this? I grabbed a diagnostic log before i started the array, not sure if it would help.

tower-diagnostics-20250307-0759.zip

Looks like it definitely did just reboot.   Your system event log in the BIOS might have some more information as to why.   Almost always though, reboots are caused by power outages / brownouts or a hardware issue (powersupply, RAM etc), and on at least one occasion a cat playing with the buttons on the server.

 

FWIW, you can also enable "autostart" on the array so that if it does happen, the system will automatically start the array when it comes on (Settings - Disk Settings).

 

If it does continue, you can enable the syslog server (mirror to flash) to capture the syslog.  (And also wouldn't be a bad idea to upgrade the OS version to the current stable 7.0.1)

 

Thank you kind sir! My research indicated something power-related or RAM-related as well. I will do the memtest.

 

I have a bunch of components all connected on the same circuit and nothing else shows a restart and I don't see any other evidence of a power failure.

 

I don't have the array auto-start because I use encrypted disks and a passphrase to restart. I believe (research on this was years ago) there wasn't a secure way to get the passphrase to unraid for autostart, so I just live with manual array starts.

 

I also found the syslog server during my research this morning, that seems quite useful and I didn't know about it. I enabled it and just picked an existing share like appdata for now. However, I don't see the syslog file being created there. I manually forced some messages to the logger and I can see them in the actual syslog, but not in the new location I specified. Do I need to restart unraid after enabling the syslog server to get it working?

6 minutes ago, jdubbs23 said:

I enabled it and just picked an existing share like appdata for now.

You have to tell it which server to get the logs from, it can be a different server, or it can be itself.

 

127.0.0.1 is the "loopback" IP

21 minutes ago, jdubbs23 said:

enabling the syslog server to get it working

There's also the mirror to flash option.  No additional settings required.

 

22 minutes ago, jdubbs23 said:

components all connected on the same circuit

Power issues can at times be messed.  In a former employment I wound up diagnosing a crash on a system that was basically impossible to crash that would always occur at a certain time of the day.   Turned out that it was caused by a sodium light in the parking lot that was failing and causing massive EFI / noise on the circuit when it turned on.

31 minutes ago, trurl said:

You have to tell it which server to get the logs from

Actually, I have that backwards. You have to tell it which server to send the logs to. It can send them to itself.

12 minutes ago, trurl said:

Actually, I have that backwards. You have to tell it which server to send the logs to. It can send them to itself.

Either way I didn't have the localhost IP specified and now it works, thanks!