RastaCongo Posted September 23, 2017 #1 Posted September 23, 2017 Im running ESXi 6.5 on a HP Proliant MicroServer G8. I managed successfully to run the latest XPEnology on a new VM and I attached a couple of virtual disk on it for testing before I transfer my data. Everything looks fine until I tried to mount my USB Disk which will store my MacBook's Time Machine Backups. The same disk can be mounted on my Win Server VM but, not on the XPEnology one. I even tried to hard mount it via SSH without any luck. I installed vmware tools but nothing again. I tried both USB2 and USB3 ports. What else would you advised me to try in order to mount that disk? Quote
IG-88 Posted September 23, 2017 #2 Posted September 23, 2017 when handing the usb device to the vm does not work you might try to give the whole pci usb contoller to the vm (i expect the hp gen8 supports vt-d) Quote
RastaCongo Posted September 23, 2017 Author #3 Posted September 23, 2017 Thanks for your reply. This is how i set up my vm: If i try to add another USB Controller it gives me an error of exceeding the USB Controller limit Quote
IG-88 Posted September 23, 2017 #4 Posted September 23, 2017 1st option (what you tryed) https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.hostclient.doc/GUID-3E6E58AA-2AD4-4370-9955-07E5FBDE800D.html as alternative a was talking about this https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010789 so not a virtual usb controller, its about giving over the whole pci/pcie device to the vm Quote
RastaCongo Posted September 23, 2017 Author #5 Posted September 23, 2017 I dont think thats possible either. Quote
IG-88 Posted September 23, 2017 #6 Posted September 23, 2017 whats in the log (dsm) when you (hot) add the usb devie to the dsm vm? you can try to restart the dsm vm with the usb device present at boot Quote
RastaCongo Posted September 23, 2017 Author #7 Posted September 23, 2017 Nothing...Is like never attached a usb disk on it Quote
IG-88 Posted September 23, 2017 #8 Posted September 23, 2017 did you check all the steps in the first link? https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.hostclient.doc/GUID-3E6E58AA-2AD4-4370-9955-07E5FBDE800D.html maybe try to boot a ubuntu iso in the vm instead of the jun loader and see what happens there if you attache the usb drive to the vm Quote
RastaCongo Posted September 23, 2017 Author #9 Posted September 23, 2017 i can attach drives on my win server machine Quote
IG-88 Posted September 23, 2017 #10 Posted September 23, 2017 you already wrote that and the conclusion is that the usb hdd is basicly worlking as it should (no hardware problem) booting ubuntu is about to check if the usb passtrough of the hdd is working under "normal" conditions in the vm (is it configured correctly in esxi) that is to rule out that it is a esxi/vm problem, if it work in ubuntu its a dsm problem Quote
RastaCongo Posted September 23, 2017 Author #11 Posted September 23, 2017 (edited) linux mint was able to mount the hdd. I also delete and re-created the VM in order to fix that, so i guess is a dsm issue. Edited September 23, 2017 by RastaCongo Quote
IG-88 Posted September 23, 2017 #12 Posted September 23, 2017 (edited) when trying a usb flashdrive with win + virtual box dsm vm it does work as expected would suggest the usb emulation of vmware needs a special driver in dsm that is missing? then there should be a device without driver what output you get with lspci -k in virtualbox it looks like this 0000:00:00.0 Class 0600: Device 8086:1237 (rev 02) 0000:00:01.0 Class 0601: Device 8086:7000 0000:00:01.1 Class 0101: Device 8086:7010 Kernel driver in use: ata_piix 0000:00:02.0 Class 0300: Device 80ee:beef 0000:00:03.0 Class 0200: Device 8086:100e (rev 02) Subsystem: Device 8086:001e Kernel driver in use: e1000 0000:00:04.0 Class 0880: Device 80ee:cafe 0000:00:05.0 Class 0401: Device 8086:2415 (rev 01) Subsystem: Device 1028:0177 0000:00:07.0 Class 0680: Device 8086:7113 (rev 08) 0000:00:0c.0 Class 0c03: Device 8086:1e31 Kernel driver in use: xhci_hcd 0000:00:14.0 Class 0100: Device 1000:0030 Subsystem: Device 1000:8000 Kernel driver in use: mptspi 0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff) is there a /proc/bus/usb? if present what output for cat /proc/bus/usb/devices Edited September 23, 2017 by IG-88 Quote
RastaCongo Posted September 23, 2017 Author #13 Posted September 23, 2017 $ lspci -k 0000:00:00.0 Class 0600: Device 8086:7190 (rev 01) Subsystem: Device 15ad:1976 0000:00:01.0 Class 0604: Device 8086:7191 (rev 01) 0000:00:07.0 Class 0601: Device 8086:7110 (rev 08) Subsystem: Device 15ad:1976 0000:00:07.1 Class 0101: Device 8086:7111 (rev 01) Subsystem: Device 15ad:1976 Kernel driver in use: ata_piix 0000:00:07.3 Class 0680: Device 8086:7113 (rev 08) Subsystem: Device 15ad:1976 0000:00:07.7 Class 0880: Device 15ad:0740 (rev 10) Subsystem: Device 15ad:0740 0000:00:0f.0 Class 0300: Device 15ad:0405 Subsystem: Device 15ad:0405 0000:00:10.0 Class 0100: Device 1000:0030 (rev 01) Subsystem: Device 15ad:1976 Kernel driver in use: mptspi 0000:00:11.0 Class 0604: Device 15ad:0790 (rev 02) 0000:00:15.0 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:15.1 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:15.2 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:15.3 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:15.4 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:15.5 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:15.6 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:15.7 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:16.0 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:16.1 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:16.2 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:16.3 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:16.4 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:16.5 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:16.6 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:16.7 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:17.0 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:17.1 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:17.2 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:17.3 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:17.4 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:17.5 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:17.6 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:17.7 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:18.0 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:18.1 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:18.2 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:18.3 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:18.4 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:18.5 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:18.6 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:00:18.7 Class 0604: Device 15ad:07a0 (rev 01) Kernel driver in use: pcieport 0000:02:00.0 Class 0c03: Device 15ad:0774 Subsystem: Device 15ad:1976 Kernel driver in use: uhci_hcd 0000:02:01.0 Class 0200: Device 8086:100f (rev 01) Subsystem: Device 15ad:0750 Kernel driver in use: e1000 0000:02:02.0 Class 0c03: Device 15ad:0770 Subsystem: Device 15ad:0770 Kernel driver in use: ehci-pci 0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff) Hide $ sudo cat /proc/bus/usb/devices T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 1, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.10 S: Manufacturer=Linux 3.10.77 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=0000:02:00.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0e0f ProdID=0003 Rev= 1.03 S: Manufacturer=VMware S: Product=VMware Virtual USB Mouse S: SerialNumber=ffffffd1ffffffa2ffffffd7ffffffb8 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=1ms T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 7 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0e0f ProdID=0002 Rev= 1.00 S: Product=VMware Virtual USB Hub S: SerialNumber=ffffffd6ffffffa3ffffffebffffffcb C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.10 S: Manufacturer=Linux 3.10.77 ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=0000:02:02.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1058 ProdID=07a8 Rev=10.49 S: Manufacturer=Western Digital S: Product=My Passport 07A8 S: SerialNumber=5758483145343344574B5438 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=8b(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=0a(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms Hide S: Product=My Passport 07A8 - This is something in the usb devices, right? Quote
IG-88 Posted September 23, 2017 #14 Posted September 23, 2017 uhci_hcd and ehci-pci are usb drivers and the device list has your hdd so its no usb problem, its there not shure if this can be the problem http://www.virten.net/2015/10/usb-3-0-devices-detected-as-usb-2-in-esxi-6-0-and-5-5/ try "fdisk -l" to find out if there is already a device for the disk Quote
RastaCongo Posted September 24, 2017 Author #15 Posted September 24, 2017 I dont know how and why but now I'm able to see the usb disk in the dsm enviroment. Is quite strange because the only thing I did is to run a Live DVD of the The Linux Mind and run via SSH the commands you posted. For now the issue I guess is solved, I dont knoe if it will happen again in the future. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.