Kansur

That fixed it. thanks.

My unassigned devices just recently stopped loading the info as seen in the screenshot of the main tab. The loading animation just keeps going and never loads. The drive does show up on the dashboard page though as seen in the second screenshot. I have tested this under Firefox and safari and it is the same in each. tower-diagnostics-20230520-1249.zip

So Fix Common Problems appears to not like you anymore

That did not work, but upgrading to 6.11.5 and installing ich777’s intel_gpu_top plugin did the trick

I’ll try that. I am currently running 6.9.2, getting it ready to upgrade unraid anyway. So if this does not fix it, hopefully the latest version will

tower-diagnostics-20230328-0927.zip

My go file already contains: modprobe i915 chmod -R 777 /dev/dri everything was working fine with the i7 10th gen but now with the i5 11th gen cpu

As the title says I just upgraded my CPU from a 10700 to a 11400. Powered up and everything works fine except for Plex. The docker will no start. I deleted and reinstalled and got this error message related to /dev/dri. from the command line I navigated to /dev/ and there is no dri file or subdirectory

After updating to the 2023.03.19 unassigned devices release I am no longer getting the out of memory error after reboots

Reinstalled unassigned devices to shut up nginx, did not reboot. Now it is spamming the log with: Mar 17 16:08:11 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token tower-diagnostics-20230317-1608.zip

Should I try upgrading to 6.11.5 and see if that helps?

Removed unassigned devices and rebooted again, now nginx is throwing a conniption tower-diagnostics-20230317-1601.zip

Sorry for the delay again, I had to wait for a parity rebuild and then a large file transfer befor i could start rebooting the server willy-nilly. Anyway, through the removal and adding of plugins and the culprit appears to be the unassigned devices plugin. You can see in the attached log files that right before avahi crashes out with an oom, unassigned devices throws some warnings while trying to do something with a local synology drive, not sure how or if that is related, I just know that I can boot fine and not get an out of memory error with every plugin installed, but as soon as I install the unassigned devices plugin it craps out. And it will do it with or without the 2 unassigned devices addons. Mar 17 15:17:10 Tower unassigned.devices: Warning: shell_exec(/sbin/arp -a 'ALFRED.local' 2>&1) took longer than 10s! ### [PREVIOUS LINE REPEATED 1 TIMES] ### Mar 17 15:17:26 Tower unassigned.devices: Warning: shell_exec(/sbin/arp -a 'ALFRED' 2>&1) took longer than 10s! Mar 17 15:17:36 Tower unassigned.devices: Warning: shell_exec(/sbin/arp -a 'ALFRED.local' 2>&1) took longer than 10s! Mar 17 15:18:25 Tower kernel: avahi-daemon invoked oom-killer: gfp_mask=0x100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), order=0, oom_score_adj=0 tower-diagnostics-20230317-1518.zip

Had to go out of town, so sorry for the delay. I booted into safe mode and it did not kick up the error. Of course the former parity drive i had just folded into the array decided to go tits up as soon as I left, so I get to deal with that as well tower-diagnostics-20230313-2128.zip

My go file looks like this #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /etc/rc.d/rc.avahidaemon stop /etc/rc.d/rc.avahidnsconfd stop modprobe i915 chmod -R 777 /dev/dri

Unfortunately it did not fix it, still happens every time I boot up. Just now it uses the swapfile before crapping out. I have included my latest diagnostions for shits and giggles tower-diagnostics-20230309-1603.zip

Tried swap, it got filled up as well. Looking at the different diagnostics syslogs I have taken each time, avahi-daemon is what is triggering the out of memory error each time and is then killed. It appears to be for Apple Bonjour services, I use macs, but I do not know if this is needed, or what could be done to fix.

It keeps happening, so it is not a one time thing unfortunately. Th error message is coming minutes after startup, I would not think ram would be getting unduly fragmented so soon after boot. Not sure what you mean by limiting more ram. I am not currently running any VMs, just dockers. The dashboard shows I am only using 10% of 32 gigs of ram. I am about to install the swapfile plugin and will see how that does.

Just realized you answered with a possible fix for the out of memory errors in my other post. I will try that fix before bothering you further

Disabled bluetooth in the bios, that got rig of the error spam. I am still getting out of memory errors though. Latest diagnostic attached tower-diagnostics-20230309-1137.zip

Looking at the current log, the log full error seems to be from the bluetooth controller failing for some reason. This rings a bell that I had to disable that i bios previously, and I updated the bios recently and it probably reset that. Would that constant failing lead to the out of memory error? So I will go and disable that again and hopefully that fixes everything.

Newest Diagnostics, another out of memory error tower-diagnostics-20230309-1112.zip

After multiple power on attempts, checking the usb on another computer, changing usb ports, and just general futzing, it booted this last time I hit the button. unraid is up and running again. Not really sure what happened to change, but happy I waited a little bit before heading to micro center. Anyway, with that out of the way, if you could look at the diagnostics now I would appreciate it

I woke up this morning to unraid yelling at me to run fix common problems, so like an obedient monkey I do so. FCP tells me that (and i am paraphrasing since I cannot quote directly) that my log is getting full, this should not be happening, and to upload the attached diagnostics. The more information says that I will need to reboot to clear the logs, after i download the diagnostics I reboot the computer and now... nothing. The computer powers up, but no post, no loading of unraid. It had been working fine,other than an out of memory error and an MCE error that that I posted about as well. I had just finished 2 full parity rewrites as i swapped in 2 new parity drives. Hoping that my diagnostics might explain what is going on. Thanks tower-diagnostics-20230309-0850.zip

Fix common problems yelled at me to post my diagnostics here tower-diagnostics-20230307-1420.zip