no USBs are currently working on our server. We want connect USB3 HDD to ESXi and then to VM, which will be for backups. It’s working fine and fast, as we want – but.
Problem is, that if USB device is attached to particular VM. I’m not 100 % sure with following steps, so far I got this problem only for the third time, but I’m trying to fix it without rebooting whole server.
One steps, how I “killed” USBs on Windows 8 virtual machine:
At first, it looks fine, but then I can’t connect to Console, Windows is not responding on ping and Remote Desktop is not working too.
After some time (a few minutes), I get an error, which is logged in VM Events:
Description: Warning message on <VM name> on <server name> in ha-datacenter: USB device "Western Digital My Book 1230" is no longer connected to the virtual machine.
Time: 23.1.2015 11:30:28
USB device "Western Digital My Book 1230" is no longer connected to the virtual machine.
After this error, VM is working fine again, without any problems, except USB and sometimes COM.
Since this happens, no USB 3 and no USB 2 are working on server. I can connect above mentioned USB HDD to any port or I can connect USB Memory Stick and nothing is detected. Also lsusb doesn’t detect these USB devices and listing takes a few minutes. I also have suspicion, that serial port COM1 stopped working because of this or at least, there is some connection.
When this happened for the first time, I fixed it by many reboots of whole ESXi server.
When this happened for the second time, I fixed it with only reboot of whole ESXi server. I didn’t touch cables at all, so it shouldn’t be caused by malfunctioning cable (I also tried different one before with no success and I also tried USB HDD on different computer and works perfectly fine.) By the way, also COM1 port in VM started to work again (is mapped to real COM1).
I was trying to simulate this problem, but I can’t do it right, I don’t know how. There are too many things, which might be related…
When USBs weren’t working, I tried executing /sbin/services.sh restart, but it didn’t fix the issue – lsusb wasn’t still able to printout my USB HDD.
Both cases happened only during powering off, so it is not so big issue if it happens if I know quick fix for it. I need to find some way, how to restart whole USB subsystem on ESXi server, to get USB working without affecting running VMs.
As I mentioned, that there might be some connection between USB and COM1 – once even happened, that whole ESXi server boot halted, while serial cable was connected to the port. (Other end of the cable is connected to old Sun server.)
Supermicro X10DRi motherboard with integrated USB 2 and USB 3 and serial port
WD My Book USB 3.0 (WDBFJK0040HBK-EESN)
VMware ESXi 5.5 2302651 (installed 5.5 U2 + 2 patches)
Windows 8.1 64b with VMware Tools installed
Windows Server 2012 R2 64b with VMware Tools installed
What I found on the internet:
Rebooting ESXi from a USB drive fails with error: URB timed out - USB device may not respond (1010940)
This is very similar, but I’m not booting from that device, so I don’t know, whether it’s related and anyway, I don’t know, what should I do with is. From my point of view, it should work with any USB HDD.
ESX host get "URB timed out - USB device may not respond" during reboot ?
This is a little bit old post and it’s also while booting from USB.
USB hard drive stops responding
This is most likely my problem, but there is no solution – only the link to my first link found on the internet.
I would really appreciate any tip, help or suggestions.
Thank you in advance.
I still don't know, what is causing this issue and we will go different way, so we don't need USB HDD.
If somebody need, these are the steps, that fix USB:
You asked the same question on 2 old threads, each thread being about an entirely different product (ESXi and Workstation) - you might wish to search for a resolved thread which matches whichever of those products you are experiencing the same issue with...
I agree with Bernds answer.
The issue posted in 2015 apparently was so obscure or unimportant that nobody looked into it or followed it up.
Only new bit we have is the attribute: painful
Lets assume that the problem in 2015 was trivial and OP solved it and never came back