- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
These are the steps i performed before the patch.
stop the vpxa and hostd these must be stopped before.
/etc/init.d/hostd stop
/etc/init.d/vpxa stop
Check for dead paths esxcfg-mpath -L
ID the sd card device and check for anything dead
esxcli storage core device world list
mine is vmhba32 so i run
esxcfg-rescan -d vmhba32
Check again
esxcli storage core device world list
if still exist esxcfg-rescan -d vmhba32
esxcfg-rescan -u vmhba32
wait at least 5 mins because of the rescan etc etc.
then
/etc/init.d/hostd start
/etc/init.d/vpxa start
the trick is to clear it all, wait for a duration then start the services. If you do not wait enough or if they are not cleared you need to do it all again
That's assuming you have the sd card bug and there are a spam of entries with local6.info: vmkernel: cpu24:2097581)ScsiVmas: 1057: Inquiry for VPD page 00 to device mpx.vmhba32:C0:T0:L0 failed with error Timeout
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have an identical situation right now.
Did all the same tricks/commands and rescanning leads to: Connection failed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HCBV,
1. Where are the ESXi installed , in USB ?. ESXi 7.0.2 has issues with USB.
2. Could you please share errors from log file.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My ESXi is installed on a dual SD card that uses the USB bus.
I believe I had posted the logfiles before but I will try to get a new one.
I didn't check for dead paths before rebooting the machine, currently it is working:
vmhba33:C0:T0:L0 state:active mpx.vmhba33:C0:T0:L0 vmhba33 0 0 0 NMP active local usb.vmhba33 usb.0:0
EDIT:
vmkernel.log is full of vmhba33 errors and faults, like this:
2021-06-08T08:43:56.206Z cpu11:2097365)WARNING: NMP: nmpUnclaimPath:1732: NMP device "mpx.vmhba33:C0:T0:L0" quiesce state change failed: Busy
2021-06-08T08:44:17.878Z cpu16:2451749)Vol3: 3711: Could not open device 'mpx.vmhba33:C0:T0:L0:7' for probing: No connection
2021-06-08T08:44:17.878Z cpu10:2451751)Vol3: 3711: Could not open device 'mpx.vmhba33:C0:T0:L0:5' for probing: No connection
2021-06-08T08:44:17.878Z cpu16:2451749)Vol3: 3711: Could not open device 'mpx.vmhba33:C0:T0:L0:7' for probing: No connection
2021-06-08T08:44:17.878Z cpu10:2451751)Vol3: 3711: Could not open device 'mpx.vmhba33:C0:T0:L0:5' for probing: No connection
2021-06-08T08:44:17.878Z cpu16:2451749)Vol3: 3711: Could not open device 'mpx.vmhba33:C0:T0:L0:7' for probing: No connection
2021-06-08T08:44:17.878Z cpu10:2451751)Vol3: 3711: Could not open device 'mpx.vmhba33:C0:T0:L0:5' for probing: No connection
2021-06-08T08:44:17.878Z cpu16:2451749)Vol3: 3711: Could not open device 'mpx.vmhba33:C0:T0:L0:7' for probing: No connection
2021-06-08T08:44:17.878Z cpu10:2451751)Vol3: 3711: Could not open device 'mpx.vmhba33:C0:T0:L0:5' for probing: No connection
I am running with:
vmkusb 0.1-1vmw.702.0.0.17867351 VMW VMwareCertified 2021-05-02
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HCBV,
You should move boot off from USB if you are planning to use it in production environment.If USB is the only boot device possible, wait for upgrade.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I currently only have a USB device as bootable option.
Is there a resource or page to follow regarding the driver and upcoming update? Is the beta usb driver perhaps available?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is unreal. I have this problem too, spent hours of my life reloading ESXi and removing VIBs I thought may be the root cause. Completely unacceptable that VMware still distributes this broken build of ESXi. I'm on VMware ESXi, 7.0.2, 17867351 ..
Regards,
Adam Tyler
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So get this, I opened a case with VMware to get a copy of this updated VIB (VMW_bootbank_vmkusb_0.1-2vmw.702.0.20.45179358.vib) and they won't do it. They want to waste my time and collect logs while my hosts are going offline. No, I just need the fixed VIB thanks, I'll let you know if it solves my problem. So frustrating.
Regards,
Adam Tyler
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
They accepted our #PR within minutes without want to see any logs.... and closed it one second later because its a known issue and will be "corrected" with the upcomming U3.
Regards,
Joerg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ya, I've had this poor support experience a few times now with VMware support. They want logs and it takes forever to collect, then they sit on it for a few days. They don't know how to read them, and by then you've solved your own problem. Wondering why we maintain a support agreement at all...
Sounds like you won the lottery and had someone actually help you when you reached out. Good for you.
Regards,
Adam Tyler
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
just get the updated one with secure boot supported.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not sure I follow. there's been a fix posted somewhere or?
Regards,
Adam Tyler
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I still have not been able to grab the new driver that should fix this issue. Am I missing something here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The U3 which contains the fixed driver is not public available yet.
Gruss
Joerg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same POOR VMWARE SUPPORT experience here as well. Scratching my head with the direction that VMWare is going regarding support. From a customers perspective, it definitely the wrong way.
I can understand that the USB vib that is/was available to address the problem may not be ready for prime time, but if it addresses the problem for the masses with little side affects, that is better than nothing at all. Sounds like a vaccine no?
Regardless, unable to get a support technician on the phone, having to wait next to my phone to hear back from them.. If you miss the call, oh because you are actually working, then the whole thing starts all over. Not very productive from a customers standpoint. May work great for VMWare but who pays VMWare for support? We do.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When ever possible you should create the #SR via my.vmware.com portal and not over the phone in first place.
Years a go it was a human which picks up the phone and today its some kind of computer voice recognition with bad qualitiy. I have one special case where iam unable to open a support call ![]()
Regards
Joerg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wow, just had this happen in my environment (UCS blade farm, all SD cards). Not a fun evening.
This has to be one of the worst bugs ever. Seems like every troubleshooting step in the book made the situation worse. Especially when you run a ls /vmfs/volumes and it freezes up both the SSH AND the DCUI indefinitely.
Unbelievable that support wont hand out the fixed vib without going through all sorts of hassle. Very displeasing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I hear ya. We ended up rolling back to U1 because of just that. most of the time we are able to recover but those few times when u can't are the ones where your boss comes to you asking what the explicit is going on and what are you doing to prevent this from happening again. You can say its the VMWare SD card bug only so many times before it becomes old.
Also since the release of the fix kept being pushed out, we had no other choice.
Larry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
what i find more annoying is when they as you, when will this be fixed. Something like this should have been fixed much sooner. instead they release a unsigned patch which does work but then prevents you from using secure boot.
Roll back for us was not an option, too hosts and work.
Getting the patch from VMware was not an issue, provided them with all the info bundles, logs and snippets. Proved it was the same error and got patch straight away. It is possible to use a script as a workaround to bypass this but its not something you would do in a prod environment.
Still not as bad as a few years back when there were VMware bugs and issues with each release.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's absolutely inexcusable on VMware's part. The fact that this build shipped with the USB/SD card bug is bad enough, but to drag feet for months with no official fix leaves me speechless. Mounting evidence that VMware is no longer the go to product when it comes to virtualization platforms. There are many other options out there.
For now, I've downgraded to 6.x and will stay there until the bitter end. Hopefully VMware will piss off enough people that version 7 is actually something you can comfortably deploy in a production environment at some point.
Regards,
Adam Tyler