jkirkcaldy

I’ve resolved my issues now. I thought it was a bad usb stick but it was actually a bad stick of ram. I thought I’d do a contest to rule it out, there was no errors until the first pass got to about 80% and then there were thousands. I’ve since replaced and upgraded my ram (32gb to 64gb) and my server has been stable ever since.

So being away from home mea t I couldn’t reboot the server and it came back up after a couple of days. it was a weird issue, half of my containers were still up, I could watch Plex, access gitea, Immich but others I couldn’t. I have been having separate issues with authentik so anything that was proxies through that I couldn’t access. I couldn’t log on via ssh or via the physical server (via pikvm) but now it’s come back up I had to restart docker with the rc.d command as all the containers had been stopped and have a system error if I tried to start them from the webui. bit I was able to get the diagnostics which may help get down to the root of the issue. storageserver-diagnostics-20240831-0717.zip

It’s plugged into an ups so can’t use the smart plugs. I’m going to get the atx power control for the pikvm. i moved my home assistant to a dedicated machine for these exact reasons. My other half doesn’t mind Plex going down because she’ll just watch Netflix but if she can’t turn the lights off I’m up all night diagnosing it. I think I’m going to downgrade back to 6.11.11 when I’m home again.

Yep. Upgraded to the beta and got this behaviour so downgraded and I’m still getting this issue. everything is down except Plex, that’s still up but playback fails. So I suspect it’s something to do with the main array. I can see the shares but trying to access them crashes explorer. Accessing docker containers that don’t have the main array mounted works fine. I’ve got portainer installed and I can access the webui but as soon as it tries to connect to the docker socket it crashes. I can ping but I get errors trying to ssh. Trying to log on via the server itself gives me timeout errors. So I can’t log in to do any diagnostics etc. I’m currently away from home so can’t do a hard reset. But I have a pikvm so can try other things.

No, That is an issue some people have had before. I'm still trying to understand why it happens as it can be difficult to reproduce. I'm testing something that may help with an update coming later today.

I am working on a fix for this now. It is due to the way some plex containers map their media at the root of the container so the script was swapping out the '/' for '/films' ther ewill be an update to address this in the next day or two.

Mine is still up and running. Finished the parity without issue. One other thing I did was turn off all my scheduled scripts in the user scripts plugin. I don't think that should have anything to do with anything though. Have you removed any remaining files from the /boot/config/modprobe folder Or is there anything in your go file?

It’s not only for unraid so it needs to be configured for systems where it is not automatically passed on. I suppose I can take it out of the template so it wouldn’t be configured twice on unraid systems.

Monday Morning and it's still up. uptime is nearly 4 days now. I have had multiple people streaming from my plex server over the weekend, some with hardware transcodes some with direct play. My working theories so far: Something in Intel-GPU-TOP or GPU-Statistics wasn't playing nice with 6.10-rc.2 and my hardware. My other theory is that the server kept kicking off a parity check on each reboot so it could be something to do with that. I'm running a parity check now to see if anything happens. My thinking being that if one of my HBAs got too hot then it may have locked up the system. But I've been using these HBAs for a while now and they were in my old system so I don't think it should be that.

I had to upgrade back to 6.10-rc2 (I tried the tpm bios and Windows won't boot without it and I couldn't be bothered with trying to do a fresh install of everything) I have left the install as stock so it has loaded the i915 drivers and it has been up for nearly a day so far. It still needs way more time to be labeled as stable. But considering last time it was a matter of hours before it locked up I am cautiously hopeful. Perhaps it was installing GPU-TOP that caused the crashing? Incidentally, hardware transcoding is working, it just takes a second for Tautulli to show that the transcode is hardware accelorated. I will give it the weekend and if it locks up again I will submit the bug report. The only thing that isn't working for me is the HDR tonemapping on plex, but I believe that is a Plex driver issue rather than Unraid specific.

Everything works flawlessly for me until I enable the i915 drivers. Tested on both 6.9.2 and 6.10-rc.2 Doesn't even seem to be related to a transcode. It happened mostly overnight when there was nobody using the server. Though one thing I haven't tested is, hardware transcoding with plex didn't work (even with 6.10) unless I installed ich777 intel-gpu-top plugin. I haven't tested without installing that yet.

Ok I’ll do it on my current hardware. on a side note, downgrading back to 6.9.2 and not loading the igpu drivers and the system has been stable for nearly a week. So it seems to definitely be related to the igpu.

Not yet, it's next on my list of things to do. Can I do the memtest on a separate computer or should it ideally be done on the same machine? My home assistant container runs on unraid and taking that down for a couple of days will be a real chore. But if I can run the memtest on a separate PC, I can test a couple of sticks at a time.

use a different port other than port 80 in the docker config. use something like 8080 or another unused port.