Windows VM shutting down when writing to USB disk

andrewhart

New Member
Jun 26, 2024
1
0
1
Hi

A few months ago I setup a Proxmox box on a Dell Optiplex 3080 SFF, to run HomeAssistant, Plex and a Windows VM backing up a seperate TrueNAS box.

It's been awesome, everything runs so much better then when I had the VMs on the TrueNAS system. The only issue has been recently the Windows VM has started shutting down when there is activity on the USB disks. I have 4x 6TB USB drives in a JBOD that back up the main share on my TrueNAS VM. There is a daily sync task (TrueNAS also replicated to Google Cloud, this is just to have a local backup).

I can see entrys in the logs about VM 103 stopping, can anyone please help me figure out what is going on?

Thanks!


Dell Optiplex SFF 3080
10th gen i3
32GB RAM
128GB NVME boot drive
512GB SSD for VMs

Log:
Jun 23 12:28:30 pve kernel: usb 2-1.1: Process 1370171 (CPU 0/KVM) called USBDEVFS_CLEAR_HALT for active endpoint 0x02
Jun 23 12:28:30 pve kernel: usb 2-1.1: Process 1370171 (CPU 0/KVM) called USBDEVFS_CLEAR_HALT for active endpoint 0x02
Jun 23 12:28:30 pve kernel: usb 2-1.1: Process 1370173 (CPU 2/KVM) called USBDEVFS_CLEAR_HALT for active endpoint 0x02
Jun 23 12:28:30 pve kernel: usb 2-4.1: Process 1370178 (CPU 7/KVM) called USBDEVFS_CLEAR_HALT for active endpoint 0x02
Jun 23 12:28:32 pve kernel: usb 2-2.1: reset SuperSpeed USB device number 5 using xhci_hcd
Jun 23 12:28:38 pve kernel: usb 2-1.1: reset SuperSpeed USB device number 3 using xhci_hcd
Jun 23 12:28:38 pve QEMU[1370117]: kvm: ../hw/usb/core.c:563: usb_packet_check_state: Assertion `!"usb packet state check failed"' failed.
Jun 23 12:28:38 pve pvedaemon[1569591]: <root@pam> end task UPID: pve:0018166F:028B5DC8:667803BC:vncproxy:103:root@pam: OK
Jun 23 12:28:38 pve kernel: fwbr103i0: port 2(tap103i0) entered disabled state
Jun 23 12:28:38 pve kernel: tap103i0 (unregistering): left allmulticast mode
Jun 23 12:28:38 pve kernel: fwbr103i0: port 2(tap103i0) entered disabled state
Jun 23 12:28:39 pve pveproxy[1580178]: worker exit
Jun 23 12:28:39 pve qmeventd[1581929]: Starting cleanup for 103
Jun 23 12:28:39 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
Jun 23 12:28:39 pve kernel: vmbr0: port 5(fwpr103p0) entered disabled state
Jun 23 12:28:39 pve kernel: fwln103i0 (unregistering): left allmulticast mode
Jun 23 12:28:39 pve kernel: fwln103i0 (unregistering): left promiscuous mode
Jun 23 12:28:39 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
Jun 23 12:28:39 pve kernel: fwpr103p0 (unregistering): left allmulticast mode
Jun 23 12:28:39 pve kernel: fwpr103p0 (unregistering): left promiscuous mode
Jun 23 12:28:39 pve kernel: vmbr0: port 5(fwpr103p0) entered disabled state
Jun 23 12:28:39 pve qmeventd[1581929]: Finished cleanup for 103
Jun 23 12:28:39 pve systemd[1]: 103.scope: Deactivated successfully.
Jun 23 12:28:39 pve systemd[1]: 103.scope: Consumed 1h 46min 48.588s CPU time.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!