ssjucrono

oooh, interesting. I had no idea. I am also talking to the creator of the PCIe adaptor

yes, I guess I am not sure what you are getting at?

Yeah I originally had it in slot 4 and that was worse. I moved it to slot 6 currently. I had this working fine with a more generic adapter however only 1 TPU was showing due to the weird layout of m2. The Google Coral is a dual TPU m2 with an adaptor from https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter to make it pcie

so the device is currently in the server and operating per the drivers it is when I start the Frigate docker that it will work for about an hour or less then crash the server. I previously didn't have a pcie bracket on it. I put one it and it started this behavior.

syslog Ok I have attached the syslog. I really do not see anything really telling in it. Thank you @JorgeB

oh ok I did enable before this most recent crash. Let me reboot and check it out

I added pci=noaer pcie_aspm=off to my unraid OS section. It seemed like it was working better but after about an hour or so the whole server just stops responding So now it works for a bit but then my whole server stops responding. I cannot SSH webgui nothing. I have to hard reboot it by holding the power button. I also don't think I can see logs as I have to reboot so I don't get the syslog. I thought I was on the right path but I guess not.

So now it works for a bit but then my whole server stops responding. I cannot SSH webgui nothing. I have to hard reboot it by holding the power button. I also don't think I can see logs as I have to reboot so I don't get the syslog. I thought I was on the right path but I guess not.

@JorgeB Thank you! I added it like so: kernel /bzimage append initrd=/bzroot pci=noaer pcie_aspm=off I will reboot and test today Thank you

Where exactly did you add the pcie_aspm=off Currently trying to get my pcie google coral to work in Google's GitHub they said this I had tried disabling it my bios and that didn't help This was google's Response: can you please share how did you turn off pcie_aspm. have you added pcie_aspm=off to the /boot/extlinux/extlinux.conf? $ cat /boot/extlinux/extlinux.conf TIMEOUT 30 DEFAULT primary MENU TITLE L4T boot options LABEL primary MENU LABEL primary kernel LINUX /boot/Image INITRD /boot/initrd APPEND ${cbootargs} quiet pcie_aspm=off Thank you for your help

Really? Temp doesn't rise past 49 degrees. It goes negative temp when it is shutdown. You think it is not accurately reporting the temperatures? I could get some heatsinks for them?

And it failed again! That did not fix the issue. very weird Temp is not the issue it seems Anyone have any insight?

I am having a similar issue to @AdvancedMobileRepairs Using the Dual TPU in Magic-Blue-smoke PCIe adapter. Prior to this I was using a single TPU with a different adapter that was working fine. I have been monitoring the Coral Temperatures at they have not been going above 48 Degrees. I have this error in my syslog: If anyone has any insight into this? I already asked in the Frigate github and we troubleshooted to a point but then they told me to ask in the unraid forum. Thank you EDIT EDIT: Per this thread: I disabled ASPM on PCIe in my BIOS. restarted server and running frigate to see how long it works before the coral shuts down.

Ok I updated bios. Reset bios settings to default. removing docker unraid-api was the issue. after that my server is much more stable. Thank you all for your help!

So my CPU usage has been fixed! however I have another problem now. If I need to open a new post I can. ALL my usb devices stop working after a time Currently struggling with my deconz zigbee controller USB stick. Keeps appearing and disappearing causing my zigbee docker to stop. here are my logs showing the USB errors also after rebooting I have machine check events as well. I have mcelog installed already raid-diagnostics-20220729-1329.zip raid-diagnostics-20220729-1153.zip

I think I find some of the issue. I had a docker container called unraid-api which was causing error messages in my Home Assistant VM. Also causing high CPU usage. Once I turned it off errors stopped and usage became more normal. VM Errors CPU usage after turning of unraid-api docker

I have about 4 days of uptime and then my server starts getting hammered again. I attached the latest htop and diagnostics bundle. In the syslog it was showing an error about not enough workers? I am still trying to track down what is my usage issue? I did edit the folder caching plugin to exclude more items. Any insight would be much appreciated. Thank you again Edit: I rebooted it which temporarily fixes the issue then it crops again in about 4 days or so Edit2: here is a graph of my cpu usage from yesterday to this morning. it ramps up at night for some reason raid-diagnostics-20220719-0811.zip

So it appears I have a really high load it seems? based on htop of I am reading it correctly? If anyone can provide some insight into this? Thank you Edit: is this an issue related to folder caching?

oh yeah that's very odd! I have 96GB of RAM. Must have been that new docker container, I hope. Still wondering why the webui is not loading again.

Thank you JorgeB! What is an OOM error? I did just install a new docker "checkmk" so I rebooted and uninstalled it.

So I was able to switch USB drives and I had decent uptime. Then my 48 core xeon server spiked to 100% on all cores randomly. I was bale to get a diagnostics off before I rebooted it : raid-diagnostics-20220706-1628.zip Now The webpage is not loading again. But all of my docker containers and VMs work fine and I can SSH. Here is a diagnostics now with the webui not loading: raid-diagnostics-20220708-0836.zip Thank you for all your help thus far it has been immensely helpful

ok I edited the VM form and removed the USB lines from the file. and then re-added the USB and the VM Started up again.

I had a usb stick passed through to a VM. and it was working fine before I tried swapping USB boot devices. now I cannot start this VM if I untick the usb device: I also have machine check events attached my diagnostics Thank you again @trurl I do have nerdpack and mcelog installed raid-diagnostics-20220627-1022.zip

okay! that worked I switched USB drives and unraid is starting properly. However I am having issues starting my VM. even if I a remove the usb from the VM still will not start see log attached. now I will wait to see if I get longer than 4 days of uptime before the GUI stop working. Thank you again for all your help! This community is GREAT!

duh, ok I see that now. Thank you