Recent content by FaySmash

The LINDY 43119 USB 3.0 to SATA and Silverstone SST-EP02B USB 3.0 to SATA Adapter don't have this problem, it's isolated to the CSL one using the ASM1153E chipset. I'll consider this case as solved, because it just seems to affect a very specific hardware combination.

Thanks, I'll try

also happens with the 6.2 Kernel

I had to use this adapter because I had no more SATA ports or PCI-E slots left on my board. Everything works fine, except the HDD disconnect. Setup:

(where usb0: host=4-4 is the pass-through USB device)

This does only happen when I physically remove the HDD from the HotSwap bay with the USB-to-SATA Adapter attached, not when it's hot-unplugged in the webui. This doesn't happen with any other device I tried (an USB Stick, keyboard and an USB-to-SATA adapter without auxiliary 12V power). I...

Hi there, as the title says my VMs (tested with a TrueNAS SCALE and Win 10 VM) are crashing when I disconnect my USB-to-SATA Adapter connected HDD. Logs: Windows 10 Jun 18 12:33:59 pve kernel: usb 4-4: USB disconnect, device number 8 Jun 18 12:34:01 pve QEMU[4046718]: kvm...

I only had to recreate the log file and the GUI was available immediately afterwards... My Web GUI just randomly stopped working and that fixed it. Thanks!, but something as minor as a missing log shouldn't keep the Web GUI from starting...

+1 for lxc + docker + fuse causing deadlocks of the host. I'll migrate to a VM now

2nd update: it still didn't crash since I removed the swap allocations. Seems like extensive swap usage causes this behavior in 7.1. Thanks again for the tip!

Quick update: at least until now it didn't crash anymore after removing the swap allocations for the LXCs. Lets see if it stays this way.

I'll try to remove swap allocations too, thanks!

I do have scheduled backups but at 4am. I also thought of backups as the cause because on the monitor directly attached to the server there is sometimes this line after a crash: \\Backup-PC has not responded in 180 seconds. Reconnecting... I run my server at CET +0100 so even if proxmox would...

I got the exactly same issue! Any updates on this? I still couldn't nail down the root cause, but the update to 7.1 could be the culprit. My month so far.. Additional information: 5.15.19-1-pve Kernel, promox 7.1-10 running 2 LXCs and 3 VMs Seems to always crash around the same time, 2 AM...