Proxmox suddenly stopped working

[Kozze]

Hi there,

I run Proxmox VE9.0.9 on a NUC 8 I7 BEH

This contains a VM with Home Assistant and a container with Paperless-ngx installed on it

Turns out Proxmox started failing last night around 04:47:48 and was no longer reachable.
Around 6:18 AM I did a manual reboot (power interrupted) of the NUC after which everything worked normally again

Does anyone have any ideas what could be wrong and what I can do to avoid this?


Sep 26 02:17:01 proxmox CRON[3486539]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 26 02:17:01 proxmox CRON[3486537]: pam_unix(cron:session): session closed for user root
Sep 26 03:10:01 proxmox CRON[3499172]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Sep 26 03:10:01 proxmox CRON[3499174]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
Sep 26 03:10:01 proxmox CRON[3499172]: pam_unix(cron:session): session closed for user root
Sep 26 03:17:01 proxmox CRON[3500842]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Sep 26 03:17:01 proxmox CRON[3500844]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 26 03:17:01 proxmox CRON[3500842]: pam_unix(cron:session): session closed for user root
Sep 26 04:16:01 proxmox smartd[839]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 23 to 24
Sep 26 04:17:01 proxmox CRON[3515362]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Sep 26 04:17:01 proxmox CRON[3515364]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 26 04:17:01 proxmox CRON[3515362]: pam_unix(cron:session): session closed for user root
Sep 26 04:29:06 proxmox systemd[1]: Starting man-db.service - Daily man-db regeneration...
Sep 26 04:29:06 proxmox systemd[1]: man-db.service: Deactivated successfully.
Sep 26 04:29:06 proxmox systemd[1]: Finished man-db.service - Daily man-db regeneration.
Sep 26 04:32:06 proxmox systemd[1]: Starting pve-daily-update.service - Daily PVE download activities...
Sep 26 04:32:07 proxmox pveupdate[3518962]: <root@pam> starting task UPIDroxmox:0035B201:05A0B60B:68D5FB27:aptupdate::root@pam:
Sep 26 04:32:08 proxmox pveupdate[3518977]: update new package list: /var/lib/pve-manager/pkgupdates
Sep 26 04:32:10 proxmox pveupdate[3518962]: <root@pam> end task UPIDroxmox:0035B201:05A0B60B:68D5FB27:aptupdate::root@pam: OK
Sep 26 04:32:10 proxmox systemd[1]: pve-daily-update.service: Deactivated successfully.
Sep 26 04:32:10 proxmox systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
Sep 26 04:32:10 proxmox systemd[1]: pve-daily-update.service: Consumed 3.169s CPU time, 235M memory peak.
Sep 26 04:46:01 proxmox smartd[839]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 24 to 23
Sep 26 04:47:48 proxmox QEMU[1249]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Sep 26 04:47:48 proxmox QEMU[1249]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Sep 26 04:47:48 proxmox kernel: usb 1-3: USB disconnect, device number 8
Sep 26 04:47:48 proxmox kernel: usb 1-3: new full-speed USB device number 10 using xhci_hcd
Sep 26 04:47:48 proxmox kernel: usb 1-3: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Sep 26 04:47:48 proxmox kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 26 04:47:48 proxmox kernel: usb 1-3: Product: ConBee II
Sep 26 04:47:48 proxmox kernel: usb 1-3: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Sep 26 04:47:48 proxmox kernel: usb 1-3: SerialNumber: DE2433299
Sep 26 04:47:48 proxmox kernel: cdc_acm 1-3:1.0: ttyACM0: USB ACM device
Sep 26 04:47:51 proxmox kernel: usb 1-3: USB disconnect, device number 10
Sep 26 04:47:52 proxmox kernel: usb 1-2: reset full-speed USB device number 3 using xhci_hcd
Sep 26 04:47:52 proxmox kernel: hid-generic 0003:16D6:0008.0003: hiddev0,hidraw0: USB HID v1.11 Device [Jablotron ltd JA-100 Flexi] on usb-0000:00:14.0-2/input0
Sep 26 04:47:52 proxmox kernel: usb-storage 1-2:1.1: USB Mass Storage device detected
Sep 26 04:47:52 proxmox kernel: scsi host3: usb-storage 1-2:1.1
Sep 26 04:47:52 proxmox kernel: usb 1-3: new full-speed USB device number 11 using xhci_hcd
Sep 26 04:47:52 proxmox kernel: usb 1-3: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Sep 26 04:47:52 proxmox kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 26 04:47:52 proxmox kernel: usb 1-3: Product: ConBee II
Sep 26 04:47:52 proxmox kernel: usb 1-3: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Sep 26 04:47:52 proxmox kernel: usb 1-3: SerialNumber: DE2433299
Sep 26 04:47:52 proxmox kernel: cdc_acm 1-3:1.0: ttyACM0: USB ACM device
Sep 26 04:47:52 proxmox kernel: usb 1-1: reset full-speed USB device number 9 using xhci_hcd
Sep 26 04:47:52 proxmox kernel: Bluetooth: hci0: unexpected event for opcode 0x5453
Sep 26 04:47:52 proxmox systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
Sep 26 04:48:03 proxmox kernel: Bluetooth: hci0: CSR: Local version failed (-110)
Sep 26 04:48:03 proxmox systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Sep 26 04:48:03 proxmox kernel: usb 1-4: reset full-speed USB device number 5 using xhci_hcd
Sep 26 04:48:03 proxmox kernel: ftdi_sio 1-4:1.0: FTDI USB Serial Device converter detected
Sep 26 04:48:03 proxmox kernel: usb 1-4: Detected FT232R
Sep 26 04:48:03 proxmox kernel: usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB0
Sep 26 04:48:03 proxmox kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Sep 26 04:48:03 proxmox kernel: ftdi_sio 1-4:1.0: device disconnected
Sep 26 04:48:03 proxmox pvestatd[1162]: status update time (6.569 seconds)
Sep 26 04:48:08 proxmox systemd[1]: systemd-rfkill.service: Deactivated successfully.
-- Reboot --
Sep 26 06:18:25 proxmox kernel: Linux version 6.14.11-2-pve (build@proxmox) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC PMX 6.14.11-2 (2025-09-12T09:46Z) ()

Thank you in advance for your response
Benny

 

[Antrill]

Hi Benny,

it looks like a USB device or hub had a problem:
Sep 26 04:47:51 proxmox kernel: usb 1-3: USB disconnect, device number 10
a second later:
Sep 26 04:47:52 proxmox kernel: usb-storage 1-2:1.1: USB Mass Storage device detected

If this device was connected before the the outage and it held a mounted file system (or even something needed by the running system) it can lead to a really bad mood of the kernel.
I guess at that time nobody touched anything, so it probably is a faulty connection or a bad switch.

 

[Kozze]

Hi Benny,

it looks like a USB device or hub had a problem:
Sep 26 04:47:51 proxmox kernel: usb 1-3: USB disconnect, device number 10
a second later:
Sep 26 04:47:52 proxmox kernel: usb-storage 1-2:1.1: USB Mass Storage device detected

If this device was connected before the the outage and it held a mounted file system (or even something needed by the running system) it can lead to a really bad mood of the kernel.
I guess at that time nobody touched anything, so it probably is a faulty connection or a bad switch.

Hi Antril,

Thank you for sharing your idea on the problem

It does indeed look like one of the USB ports has failed, for whatever reason.
I probably can't see which USB port anymore, since the NUC has rebooted and most likely got a different device number.

In the USB list, I only see six USB devices with ID references, but the log already mentions device number 10.
What could be the reason for this?

 

[Antrill]

What could be the reason for this?

Hard to say from over here. Maybe the kernel renumbered after the reboot because a hub is completely absent now?
If a number of devices is missing now, I would start by looking at "what's not there" in lsusb or other tools. It could be a faulty cable, USB speed mismatch, firmware bug... (I have seen this in USB-C docking stations a lot. After being on standby for weeks, they tend to forget half of their ports until power-cycled.)

 

[Kozze]

Hard to say from over here. Maybe the kernel renumbered after the reboot because a hub is completely absent now?
If a number of devices is missing now, I would start by looking at "what's not there" in lsusb or other tools. It could be a faulty cable, USB speed mismatch, firmware bug... (I have seen this in USB-C docking stations a lot. After being on standby for weeks, they tend to forget half of their ports until power-cycled.)

Okay, thanks for your help.
None of the USB devices or hubs were physically disconnected.
After the reboot, everything functioned normally again, including all connected USB devices.
I'll continue to monitor this, and if it happens again, I'll have to dig deeper to find the cause, if that's even possible.