nOerkH

I can be unlucky of course .. I was using a Lenovo P910 before - had issues (no longer booting - hard freezing) - exchanged the whole thing ... How are the odds the next Lenovo P910 has hardware issues again? I had frigate stopped for a while - did not encounter issues then ... as I got this USB device identitiy (the google coral adapter) switching all the time - could it be, that this also affects the usb stick Unraid is running on? Eventually some USB setting in the UEFI. Did you look into the diagnostics? I've searched with visual studio code through all files at once - there are alot of "usb" entries - nothing that shouts ERROR to my face - but as I said before - not sure what I'd be searching for

I found that unraid seems to have automatically created 3 diagnostics files yesterday at /boot/logs ? Maybe that's a trace Trying to dig into them by myself ... not sure what to look for tower-diagnostics-20240728-2017.zip tower-diagnostics-20240728-2021.zip tower-diagnostics-20240728-2047.zip syslog syslog-previous

it happened again - USB device is lost (see attached screenshot) /boot is empty as there is no USB device attached any longer after rebooting Unraid I've found this information in syslog - no clue what to do with it alot of mover entries like some HDD entries about Smart and energy saving nothing about any error - probably loglevel is set wrong or the entry is out of scope due to all those mover messages logged?

No, actually Frigate is the only thing using my GPU - I've also changed it (to the same model which I got here multiple times) .. Is there any guidance to mirror the syslog to flash? This could eventually be really helpful ..

so sad there is absolutely no replies here ... just replaced my USB Stick as it was also being disconnected/lost from time to time ... was hoping this fixes it - today I lost the Unraid USB stick again ... that's so frustrating ... The full Lenovo ThinkStation P910 which Unraid is running on has recently also been changed .. can't think it is the machine causing those problems?!

just happened again - cannot even SSH into the server - no idea how to get logs in such a state?

My Unraid server is freezing completely, and I believe the issue is related to the Nvidia GPU and the Frigate containers, which use the GPU. System Information: Server Model: Lenovo P910 (recently exchanged due to previous issues) GPU: Nvidia Quadro M2000 Unraid Version: 6.12.6 Timeline of Events: Hardware Exchange: Recently exchanged Lenovo P910 server due to previous issues. Everything worked fine initially after the exchange. Cache Drive Crash: Cache drive crashed, causing all Docker containers to be disorganized (The mover wasn't properly configured to move Appdata to the array) Reconfiguration: Set up all Docker containers again. Everything worked fine initially. Nvidia driver was auto-updated, which caused the Quadro M2000 not to be recognized. Downgraded the driver, and everything seemed to work fine again. Server Freezing: After a few days, the server started freezing completely (no more WebUI access). The server ran for about a week without issues when the Frigate container wasn't started. Now in the test starting the Frigate container, the server immediately froze. (Usually the server runs some days, before not being accessible) Sidenote: I need to start the container twice because the USB enumerator changes (this wasn't necessary before the cache drive failure). Issues: Complete server freeze after starting the Frigate container. Unable to access WebUI when the server freezes. Difficulty obtaining a proper diagnostics file as the device completely freezes, and after a hard shutdown, only logs from the current session are available in the diagnostics file. Request: Can you help me troubleshoot this issue? Any advice or guidance on how to resolve the freezing problem or obtain more useful diagnostic information would be greatly appreciated. Additional Information: Attached is a screenshot showing the need to start the Frigate container twice due to USB enumerator changes. Attached 2 diagnostics - one before the container was started - one after the system hang again and was hard shut down tower-diagnostics-20240728-2047.zip tower-diagnostics-20240728-2017.zip