I figured out a way to see both my USB sticks in the ESXi busybox shell. If you read my previous post you will know that the system enables passthrough of the non-boot USB devices for use by guests by default.<\/p>\n
Whether or not there is a “right” way to do this I don’t know (vmware kb or google don’t turn up much of use).<\/p>\n
So, going back to that mine of information, the messages file, I notice that \/sbin\/chkconfig is run immediately before it states that usb passthrough is enabled. Running \/sbin\/chkconfig –list shows:<\/p>\n
So as a guess I changed usbarbitrator to off with the following command:<\/p>\n I will try more dd experiments at the next free slot.<\/p>\n At least I made some progress!<\/p>\n","protected":false},"excerpt":{"rendered":" I figured out a way to see both my USB sticks in the ESXi busybox shell. If you read my previous post you will know that the system enables passthrough of the non-boot USB devices for use by guests by … Continue reading ~ # \/sbin\/chkconfig --list
\nDCUI on
\nTSM-SSH on
\nTSM on
\nusbarbitrator on
\nlbtd on
\nstorageRM on
\nsensord on
\nvprobed on
\nvobd on
\nwsman on
\nslpd on
\nsfcbd-watchdog on
\nsfcbd off
\nntpd on
\nhostd on
\niked off
\nlwiod off
\nnetlogond off
\nlsassd off
\n~ #<\/code><\/p>\n~ # \/sbin\/chkconfig usbarbitrator off
\n<\/code>
\nRebooting the system and looking again, I can now see both the devices: mpx.vmhba33<\/code> (the boot USB) and mpx.vmhba32<\/code> (my target datastore). The later appears as a FAT partition, despite my trying to dd my vmfs3 filesystem over the top of it.<\/p>\n