Tristankin

Could you share your diagnostic data and syslog mirrored to flash?

No worries. Glad to help.

Yeah ignore and dont update, Try clicking the advanced toggle in the top right of the docker list and click force update, that might fix it?

You will also need to do a reboot for it to take effect, or you have to change a line of config and I can't remember how to find that one.

I know as I am another lowley intel user fighting for stability with the i915 module loaded. from terminal nano /boot/config/go Paste that sed string to the end of the go file content.

Have you considered submitting a bug report? It might get through to limetech and you have done more testing than I have. Perhaps reference this and your thread? Yeah, it does not require active load, just having the module loaded seems to be causing the issue. I achieved gpu transcoding on 6.9.2 without the intel-gpu-top and still had the issue.

That bit is a bit beyond my understanding.... But this I think steers you in the right direction: https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.9.0 just remove the /boot/config/modprobe.d/i915.conf file?

Also if you get a error saying updates are not available for your packages, add this to your go file sed -i 's#@Docker-Content-Digest:\\s*\(.*\)@#\@Docker-Content-Digest:\\s*\(.*\)@i#g' /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php

There is a url for the 6.8.3 compatible version. https://raw.githubusercontent.com/Squidly271/community.applications/d075fda8b8337c4c6bbd0b6d1d66b80a8870d9ba/plugins/community.applications.plg

Absolutely nothing for me. It's the reason it has been generally blamed on hardware faults. For me it would happen within 2 days but generally at random. No load required. If you don't have a lot of people transcoding you could try unloading the i915 module?

Only crons I have going are mover and trim. They run at very different times so they shouldn't be causing an issue.

I think there may be an issue with the intel iGPU module causing the system to hang (even just being loaded). 6.8.3 fixes this for me but I am talking with the moderators about a solution that allows a more modern version of the OS.

On 6.8.3 it is enabled, could someone on 6.9.2 confirm that error capturing is enabled?

I assume it has to be loaded as per this to allow for the low power bitrate encoding control. https://wiki.gentoo.org/wiki/Intel#GuC.2FHuC_firmware So disabling it would most likely kill the transcoding anyway. Something else I noticed though is the option for : Enable capturing GPU state following a hang Is this enabled in 6.9.x kernels on unraid. I do not know enough about kernel inspection to comment any further but it could explain why no one sees reports in syslog?

Perhaps it might have something to do with this? I am not sure if there is a specific date that the issue has been fixed, but this might be a workaround? https://wiki.archlinux.org/title/intel_graphics#Enable_GuC_/_HuC_firmware_loading

Well it is certainly not a hardware issue as I have demonstrated due to 6.8.3 uptime. I am worried with all the continuous reports from intel users there is an issue being glossed over and now I finally have found a thread that demonstrates a tangible solution to the issue. If I am going to attempt the upgrade again is there a syslog type service that I can install specifically looking for errors regarding intel iGPU issues? This server is used heavily and I don't mind trying to catch the issue but weeks without transcoding abilities is not feasible.

Whether or not you have the same configuration and have experienced any issues. Obviously you don't, but the snarkyiness sure helps. Look, I have been reporting issues for weeks as have many others. I am prevented from being able to run the latest version of Unraid, and potentially even the next one. There are a few reports every week coming through for people having the exact issue of hangs without anything showing in the kernel log on intel hardware and the mods have always blamed the issue on hardware. I have provided a link to someone who has done the testing. What I am looking for is for someone to take the issue a little more seriously...

110 Days uptime on 6.8.3. I am pretty confident now it is not a hardware issue. So it appears that the intel iGPU implementation could possibly be to blame. From this thread it appears not loading the intel iGPU prevents the lockup issue on 6.9.2 at least. Can the mods please chime in?

Sorry you did not get a reply to this. Are you using the intel iGPU for transcoding?

Interesting. I had issues with 6.9.2 freezing every couple of days and was told it was a hardware issue too due to nothing in the syslog. I am using an i3-9100 with the iGPU for plex transcoding. 6.8.3 I get 0 issues with months of uptime and had to revert back. So it appears even 6.10 won't be fixing the intel iGPU hangs...

I went back to 6.8.3 for 3 months then tried the upgrade to 6.9.2 again. Here is the thread covering my experience. In short, 6.9.2 still hates my hardware. I got the iGPU stuff worked out the second time by turning off the iGPU load in the go file but the system would still hang every 2 days or so. Nothing appears in the syslog mirrored to flash, everyone blamed the hardware over and over again. I offered to help dig further to try and find out the root source of the issue, was ignored, went back to 6.8.3 and im up 80 days now with no issues. I still see so many threads on the forums and the admins/mods constantly blame hardware, but there is a software issue, most likely the kernel, with intel hardware on 6.9.2, and from what I have seen, 6.10 might even have the same problem. I'm just biding my time till we aren't seeing people with the same issue reported a few times a week, week after week.

Config stays the same, you may have to redo your cache drives but that's it. I downgraded by replacing everything on the usb drive except for the config folder. (ran out of rollbacks trying multiple 6.9 versions. Its cheaper than buying replacement hardware if you don't find another fix. MAke sure you have the ram at the recommended speed for the cpu, disable c states, make sure you don't have anything funky with power supply power control etc.

Pretty sure you would need to configure your router to relay DHCP leases that your ISP delegates rather than giving the device a manual IPv6 address, then you will need to set up a dynamic dns forwarder with something like duck dns to update when that v6 address changes.

From memory I just had to replace everything outside of the config folder with the zip file contents. Make a backup of your usb drive first. You may need to redo your cache drives as part of the downgrade so make sure nothing is set to only be on the cache.

Is your system freezing? This does not seem relevant to the current thread.