lukeb873

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

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

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

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.

So this is what Lime Support said: I can see the exact same issue with the Nvidia driver still occurring quite often. I can see repeated cycles of out of memory followed by RmInitAdapter failed The drive is still crashing and trying to reset the GPU. Hopefully the Nvidia forums might be able to help you with this. But I'd say this is almost certainly the cause of your parity checks pausing because when the driver crashes, it can freeze the system and so interrupt the I/O operations like the parity check. The system will recover from the driver crash, but the parity process isn't always able to actually resume on its own. Looking at the logs, this is what I would suspect. Now, as you've already tried just reseating the cables, I'm assuming you've got a sufficient power supply because your RTX 5070 does use quite a lot of wattage, and an unstable power supply can cause this kind of issue. But that said, if it's happening when the GPU isn't really under load, it makes this probably less likely. I do have a Corsair RM1000X so the PSU isn't the issue. As he stated, I've been having issues with the parity check randomly pausing which he's saying seems to be related to the driver crashing. Something seems to be messed up with 5000 series and the PCIe 5.0 specification, however for your usecase that shouldn affect performance. So when the GPU diagnostics plugin does work, it says PCIe Gen (MAX): 4 (4), which I would think means it's not even running at Gen5 in the first place. Would you still recommend going down to gen3? I want to see if I can get my Immich container fixed first prior to going to a beta, but after that, I'd be open to moving to the beta.

JellyFin. Typically, I see it disappear from my GPU stats plugin, and that's how I know it's now messed up and won't be able to do any sort of hardware transcoding. Could you say more about why I need to lower this? Gotcha. In the other post, you've recommended moving to the beta. Is this still something you might recommend? I'm still waiting to hear back from Lime support to see what they have to say.

Okay, so sorry for the delay. Been troubleshooting some bad RAM, had a drive die, and been moving. After all these other issues have been fixed. I'm still having an issue with the driver. Attached are diags. I saw that you suggested updating to the beta. I actually have a ticket open with Lime support about long restart times, and it's apparently related to the NVIDIA driver. (at least according to them) I'd like to prevent updating to the beta until they advise me to. Thoughts based on what you're seeing? unraid-diagnostics-20250912-0036 ANON.zip

I've noticed that since my upgrade to a 5070 that when a Playback fails for whatever reason, which also happens more often than when I had a 3060, the card then disappears and can't be used unless the server is restarted completely. Is there any reason why this would be, or what I could do to help?

Wow, I feel like an idiot. This would be me straight up not reading the other options in the driver. Thank you

How exactly do you install the Open Source Driver? I just swapped a 3060 for a 5070