This is an odd one, but anytime I go out of state (I live in Missouri), my server goes offline. Like the entire thing, no more activity on my Unifi network. This has happened twice so far. The first time I was driving to Florida, I noticed it went offline. Thought it was a fluke and had some family friends go to. my house and restart my server, and within a couple of hours, offline again. They did it one more time, and the same thing, so I thought I'd deal with it when I got back. Got back, restarted it as it was offline on my network, so I couldn't even get to the GUI. Restarted and it's been fine since. This week I went to Illinois and within an hour after crossing the state line, boom. Offline. Again. Can't remotely restart, but I can get into my Unifi network and see it dropped off right about the time I was in Illinois. What in the WORLD could be causing this??? It's either a crazy coincidence or location-based.... somehow. I run Home Assistant, Pi-Hole, Immich, Jellyfin, Nexcloud, and a few miscellaneous Docker containers. I also have Tailscale. Everything goes offline at the same time. I have no automation in Home Assistant that would cause this, and I'm not sure if there's any in Unraid preventing it. It's also on a UPS, so I know power hits aren't the cause.

Any ideas? Will get logs when I can get back home from Illinois, but wanted to start a topic here in case this was a known thing I accidentally set up.

Enable the syslog server and post that together with fresh diagnostics if it happens again.

Here you are. It happened again (although I had the syslog set up incorrectly initially, so I'm not sure how much use that will be). Typically it'll help once or twice once being back home and then not again.syslog-UNRAID.logsyslog.txt

18 hours ago, JorgeB said:

together with fresh diagnostics

Click the diagnostics link if you don't know what we mean.

Attach Diagnostics ZIP to your NEXT post in this thread.

I don't see any relevant logged; post a new syslog after the next crash, and mention the aprox. crash timecode, together with the diags mostly to see the hardware.

Sorry, I knew exactly what you meant by diag. I had just gotten back from my trip, and after I got to tools just forgot what I was looking for. Here you are. Also provided a screenshot of Unifi or rough time estimates. When you see like 8 or so connections drop, it's when it's going down. First segment was when I got home, restarted, then took a nap, got up, realized it was down again, restarted. Woke up this morning, saw it was down, and just restarted. This is likely the last time it will go down after being home... At least this was the same experience I had from getting home from Florida back in March. Also, the only way to get the server back is to HARD restart via the front panel, as I have no way to get into it. Even the monitor hooked up to it is just green.

This could totally not be location-based, but the only two times I've had this issue are when going out of state, and it happens right around crossing a state line. It could totally be an insane coincidence, though. Mighty inconvenient as my server is then down for the rest of my trip.

unraid-diagnostics-20260608-1147.zipsyslog-UNRAID.log

Edited June 8Jun 8 by lukeb873

There are some ATA issues logged, but that doesn't explain a crash.

Since you are using a Ryzen CPU, make sure this has been taken care of: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Copy... It did it again. It's odd, though. Why suddenly it has this problem only when I leave the state, and within an hour of leaving state lines is quite odd. From March to now, there has never been another issue. Or before March, when I initially built it. It literally only opens when leaving the state and then a couple of times after being home. Then it's perfectly fine for months.

I've got a Ryzen 9 9950x and (2) 64 GB sticks of RAM. I can't recall what speed they run at, but I do know it's downclocked from expo speeds, as I initially had a few issues with stability. I'm going to update the bios later tonight, and I'll take a look at that article.

Until then, here are further diags from the last reset.syslog-UNRAID.logunraid-syslog-20260608-2204.zip

The only issues logged are what look like power/connection issues with disk 4, which should not crash the server but should still be fixed, check/replace its cables.