Closed tomhusband closed 9 months ago
It seems that your Coral device is running at USB 2 speed. USB 2 has limited bandwidth, and probably it can't keep up. Make sure it is connected to a USB 3 port.
Hmmm, I wondered about that and went with the one that had a blue tab thinking that was USB 3. Why can't they just mark it with a 2 or 3? Now I wonder if I even have a USB 3 port available.
Thanks for your reply.
lsusb gives me this:
root@pve:~# lsusb Bus 002 Device 003: ID 1058:2620 Western Digital Technologies, Inc. Elements 2620 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Do I even have a USB 3 available besides the one connected to my hard drive?
Based on the list I would say that bus 2 is USB 3, so that should be OK. When you ran lsusb
, the Coral was not connected? In that case I would rerun the command with the Coral detected.
I see that you have a connected a external HDD as well? In that case it might be power related, the Coral devices are very power hungry, especially high peak currents.
Yes, here's lsusb with the Coral connected:
root@pve:~# lsusb Bus 002 Device 003: ID 1058:2620 Western Digital Technologies, Inc. Elements 2620 Bus 002 Device 006: ID 18d1:9302 Google Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
If I don't have a spare USB 3 what happens if I just continue to let the Coral restart?
So the Coral and the HDD share the same USB bus. As long as you don't use the HDD intensively I don't expect too much problems on that. My first guess would be the USB power supply being insufficient.
If I don't have a spare USB 3 what happens if I just continue to let the Coral restart?
You mean to leave the situation as is now? I think you just miss detections in that case. Can you test without the HDD?
Can you test without the HDD? Yes, I guess so. The HDD is used just for backups. So just disconnect the HDD and see what happens?
Thanks, again, for your advice.
Describe the problem you are having
I have HA/Frigate running in a Proxmox VM on an Intel NUC. I recently installed a Coral Accelerator and have been getting "Detection appears to be stuck. Restarting detection process..." errors in the Frigate log. It starts again but a few hours later it happens again. I replaced the original USB cable hoping it might be the problem and it did run smoothly for a day but last night it restarted several times again.
The Frigate log is below but I also get the following in the Proxmox Syslog at the time the Coral shuts down and restarts:
Version
0.12.1-367D724
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
Operating system
Proxmox
Install method
HassOS Addon
Coral version
USB
Any other information that may be helpful
No response