ssjucrono

now I am wondering how long it takes to adopt my unifi devices? IT just keeps trying over and over? sorry for all the newbie questions.

yes you are right it is not Plex. It is something else using port 1900 but I have no idea what or how to figure it out Found this command and figured out it was my docker container airconnect once I turned that off it worked. and again ports are not listed in that docker template

I am using the official PMS Docker? Here is the Unifi Reborn error

yes it is set to bridge. Plex is set to host.

trying out this container now. I am having a conflict with port 1900. Plex is also using that port and I do not see an option in the Plex Template to change it. I changed on the unifi reborn but then it wasn't adopting my unifi devices. So I turned plex off and tried using port 1900 on Unifi Reborn and it is still saying it can't bind to 1900 as plex is using it though it is powered off.

ok good to know. So this one will be updated going forward and maintained? I'll make the switch!

sorry, trying to figure out how this is better than the other docker containers? Very curious to give it a try but I want to understand the difference first? thank you

I think the same thing happened to me. Grocy just broke

Does anyone have an updated URL for Samsung Magician trying to upgrade my 980 pro firmware as there is an issue on an older firmware. This link http://www.samsung.com/global/business/semiconductor/minisite/SSD/downloads/software/ Does not work anymore. Thank you

I am having the same issue and it is a huge problem as it is my zigbee usb stick so all my zigbee devices stop working. looking for a fix: May 11 12:48:04 RAID kernel: usb 3-3: new full-speed USB device number 88 using xhci_hcd May 11 12:48:04 RAID kernel: usb 3-3: device descriptor read/64, error -71 May 11 12:48:04 RAID kernel: usb 3-3: device descriptor read/64, error -71 May 11 12:48:05 RAID kernel: usb 3-3: new full-speed USB device number 89 using xhci_hcd May 11 12:48:05 RAID kernel: usb 3-3: device descriptor read/64, error -71 May 11 12:48:05 RAID kernel: usb 3-3: device descriptor read/64, error -71 May 11 12:48:05 RAID kernel: usb usb3-port3: attempt power cycle May 11 12:48:05 RAID kernel: usb 3-3: new full-speed USB device number 90 using xhci_hcd May 11 12:48:05 RAID kernel: usb 3-3: Device not responding to setup address. May 11 12:48:06 RAID kernel: usb 3-3: Device not responding to setup address. May 11 12:48:06 RAID kernel: usb 3-3: device not accepting address 90, error -71 May 11 12:48:06 RAID kernel: usb 3-3: new full-speed USB device number 91 using xhci_hcd May 11 12:48:06 RAID kernel: usb 3-3: Device not responding to setup address. May 11 12:48:06 RAID kernel: usb 3-3: Device not responding to setup address. May 11 12:48:06 RAID kernel: usb 3-3: device not accepting address 91, error -71 May 11 12:48:06 RAID kernel: usb usb3-port3: unable to enumerate USB device

Same for Z2M on latest version 1.29.2

@JorgeB I did find this jumper on my motherboard. Not sure if that is of any help?

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.