Leandres

Since I don't need the PCIe USB card I removed it. Somehow I can now do ls -l on /dev/serial/by-id. So that probleem seems solved for now. But a new weird problem appeared: An USB device which worked perfectly and super stable and plugged in one of the standard USB ports now show up twice. This problem leads to not beeing able to passthrough the USB device into a VM: And if I want to select one, after updating the template both checkboxes are marked which prevents the VM to start..... Never seen this behavior before.

@SimonF It is an USB PCIe card (extender). root@Pasithea:~# lsusb -vvs 001:006 Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 Single TT bMaxPacketSize0 64 idVendor 0x05e3 Genesys Logic, Inc. idProduct 0x0608 Hub bcdDevice 60.90 iManufacturer 0 iProduct 1 USB2.0 Hub iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0019 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 4 wHubCharacteristic 0x00e9 Per-port power switching Per-port overcurrent protection TT think time 32 FS bits Port indicators bPwrOn2PwrGood 50 * 2 milli seconds bHubContrCurrent 100 milli Ampere DeviceRemovable 0x00 PortPwrCtrlMask 0xff Hub Port Status: Port 1: 0000.0100 power Port 2: 0000.0100 power Port 3: 0000.0100 power Port 4: 0000.0100 power Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 bNumConfigurations 1 can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0001 Self Powered

I just checked whether Legacy USB is enabled in the BIOS, in case that could be the issue but it isn't since it's enabled:

I'm trying to forward an USB device into my docker. But somehow I do not have /dev/ttyUSB* devices. Neither /dev/ttyACM*. Trying to passthrough by-serial like others in the support threads suggests but: Passing through the USB device into VM's is no problem. So the devices are available and can be used. What is going on here?

I have the same problem

Is this fixed yet? I'm experiencing this also.

I've upgraded my server hardware, after that I booted and I was able to start the array without any problems. Which I had expected since I'm a happy unRAID user for 8 years now. But I wanted to tweak some power optimization settings into the BIOS so I shut down the server and tweaked some settings. After I restarted my server my 2nd parity disk was disabled and also an other disk in the array. The log giving a lot of errors and starting the array to rebuild disks isn't possible also. The data of my other shares aren't available also. Can someone help me out what to do? unraid-diagnostics-20230416-1721.zip

Yes. I did a roll back to 6.8.3. My CentOS VM's are working again.

Yes I made a backup, the config is back and my cache pool is working again. My heart almost stopped working... Now I will wait untill the CentOS bug is fixed before I upgrade my OS again. Tnx Simon!

Just VNC. I just gets better: after downgrade my OS, my complete cachepool (4 disks SSD) is not configged anymore. Which means all my VM's and dockers are gone / not accessable How to make those 4 disks get back into the cache pool so I can access my data?

I'm going to downgrade unRAID since this is real problem for me.

The error above disappears when I don't choose 2.0 (EHCI). After selecting one of the others I'm able to update te template. But the VM still doesn't boot up.... After Grub:

How can I figure that out? Can you guide me?

Not hijacking this topic, but I have the same problem. After updating the VM template I got this error. My Ubuntu VM's still working after the upgrade to 6.9.1 But all the CentOS VM's showing this error after updating:

I have the exact same problem after updating to. 6.9.1. My Ubuntu VMs start but all the CentOS VMs stuck with a blank screen after grub. This is an issue.