RogerWilco486

I stand corrected

I was running Unraid RC and therefore on the 5.17 kernel--- still had the lockups.

For what it's worth I wiped Unraid from my Comet Lake NAS and rebuilt with Fedora Server/OpenZFS/Samba/Docker/libvirt and it's been rock solid. I'm using the Intel Media VAAPI driver with the 5.17 kernel and transcoding has been working flawlessly too. When running Unraid on this same exact hardware it would randomly lock up anytime I allowed the i915 module to load.

I have spare Quadro boards and I would do this except for the system in question is ITX and the single PCIe slot is used for the LSI HBA (necessary since I'm using SAS drives).

Yep, I have a HDMI dummy plugged in when not using a monitor. I suppose it's possible the dummy is bad...how likely is that though? TrueNAS Scale is based on Linux to be their "hyper-converged" stack.

I don't use Plex, I'm actually using your Jellyfin-AMD-Intel-Nvidia container with acceleration disabled. Re diagnostics, I've had i915 blacklisted so long it's been a while since I've experienced a crash. But I did provide diagnostics a few pages back in this thread before it was suggested to try disabling i915 which solved the crashes for me. I just consoled into my TrueNAS, the kernel is "5.10.109+truenas" so considerably older than Unraid's kernel.

I don't think its coincidence. I've got a 10th Gen i7 with the EXACT same issue. If I blacklist the i915 module from loading my system is perfectly stable. But as soon as I allow i915 to load, even if nobody is actively streaming or transcoding, after anywhere from a few days to almost a month, it will eventually crash without a hint of what happened being written to the syslog. This happens with either an HDMI monitor attached or a dummy. I travel a lot and use my NAS for a lot of stuff including home security so these random crashes can be a huge inconvenience if I'm out of town. Somewhat off-topic but because of this issue I'm actually in the process of getting myself acclimated with a new TrueNAS Scale system I built to see if it's feasible for me to make the switch from Unraid. I'm not a fan of how it uses Kubernetes for the docker apps but I'm getting used to it, and I used a new docker-compose app they have that basically allows you to easily use docker-compose inside a native Truecharts app--which is awesome. That made it straight forward to setup a cloudflared docker to run an Argo tunnel into the Truecharts Traefik app and reverse proxy back to my various apps just like I do in Unraid. Now I'm getting my "arrs" stack configured how I like and it's working out okay so far. I'll be running both systems in parallel for a while. Assuming Quicksync hardware transcoding works and remains stable, I think TrueNAS will be an okay alternative for me.

Just curious, why would we be installing Ubuntu packages on Unraid?

RC4 just came out and STILL no Linux 5.16. C'mon Lime Tech...

Okay its been three weeks since I blacklisted i915 and stopped using the Intel GPU. I am happy and relieved to report I have not experienced a single lockup since then. Hopefully future RC versions of Unraid 6.10 implement a fix so I can put my GPU back to use, but in the meantime I am thrilled to have a reliable system again. Thanks!

Interesting... that may be it although I seldom do hardware transcoding. From the sounds of it though, the i915 inflicted lockups can occur at any time, with or without the iGPU being taxed at the time so maybe that really is my problem. For now I've blacklisted the i915 module, removed the Intel GPU Top and GPU Statistics plugins, removed /dev/dri from my Plex docker, and within the Plex settings disabled hardware acceleration. lsmod shows no sign of i915 nor does dmsg or any mention in syslog, so I think I've got the i915 module pretty well out of the loop now. Hopefully that finally does the trick for me. I'll keep an eye on that thread for updates... thanks!

Unfortunately it locked up again last night. I was actually in the middle of using the code-server docker when the whole Unraid system suddenly disappeared from the LAN... no response to ping or anything. Switching over to the local console, I could still interact via keyboard in that it would let me enter root to login in, but after hitting enter on root it would just return a blank line and never prompt for a password. All the consoles (ALT-F1, ALT-F2 etc) behaved the same way. Ultimately I had to hit the reset button to force a reboot, and it's back up and running yet another parity check. Is it possible that the corefrq plugin wasn't completely removed from use without a reboot, or does it sound like I have something else going on? In any event, most recent diagnostics are attached just in case. unraid-diagnostics-20220214-1347.zip

Just did, thanks! Wow what a relief if this turns out to be what the issue is.

For the past few months I've been plagued with random lockups that are so severe even the console becomes unresponsive. No ping, no response from keyboard and mouse... nothing. Initially I was running the most recent version of 6.9 but out of desperation I migrated to 6.10.0-rc2 to see if it would make a difference. I was still experiencing lockups on that too so to rule out the flash drive I also migrated that to a new device a few weeks ago. I also replaced the power supply with a new unit around that same time as well. Today I came home to another lockup, so this is getting pretty frustrating. The system is a self-built MiniITX system that's constructed around an ASRock H470 MiniITX motherboard, i7-10700K, 32-gigs of RAM, LSI SAS controller, a pair of WD-Black 1TB NVMEs for the cache drives and a combination of Hitachi 10TB SAS and 8TB SATA drives on a SAS backplane connected to the LSI HBA. I do have syslogging enabled and as far as I can see it looks like the system unexpectedly rebooted at 9:22 this morning, and then sometime between then and this afternoon completely locked up. I don't see any signs of a kernel panic et el, but perhaps folks here will have a keener eye then me. Diagnostics zip attached. Any ideas? unraid-diagnostics-20220211-2354.zip

Well this 30-year IT vet feels like an idiot now. I had been deleting config/shadow and config/smbpasswd, but not config/passwd. After that didn't work I started just deleting the shadow file since that was enough to get me back in without having to reset my user passwords every time. I just deleted all three, rebooted, reset the root password, and reconfigured my users. Logging out and logging back in now works normally. Thank you!