Good Day,
Does anyone know when the update for 7.0.2 to fix the SDCard is going to be released?
Thanks
I applied the u2c patch to one of my R840's suffering this problem. Patch applied on 8/26. as of today, the host is still running as it should. the vmkwarning log, and the storage devices view have been the key for me. With the usb/sd problem (any host running 7.01 - 7.02) the vmkwarning log tells exactly if there is a problem, and the storage devices view, when the apd condition occurs, will not even show the sd os device.
So far, even though the kernel log is logging two failures to the usb/sd, it is not recurring over and over, and so far, the vmkwarning log is clean. and the dell idrac is good, showing no failure of either of the two sd mirrored modules.
fwiw, i installed the patch via ssh and esxcli.
Hi @JM010101 ,
what failures are you referring to? Can you post an excerpt/a few lines of the messages you refer to?
Regards,
Patrik
Sure. And btw- i have now done one other Host up to u2c. It has the same failures.....i have to retype, but they are:
(in the vmkernel.log)
....cpu2:2097339) ScsiDeviceIO: 4325: Cmd(ox45b98154d340) 0x85, CmdSN 0x<number> from world 2100645 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0valid sense data: 0x5 0x0 0x0
i get two of these, I believe when the host starts... there is also one more entry , right after the above, that is "....throttlefordevice:3813 last error status from device mpx.vmhba32:C0:T0:L0 repeated one time...."
I have seen this error before on other posts, and it may be related to booting...i am keeping an eye on it.....but the important thing is the vmwarning log....CLEAN!!!
Hi @JM010101,
ah, I see. This error is completely normal and was always there. The SCSI opcode 0x85 is "ATA PASS-THROUGH(16)", which is used to query SMART values from the storage device. As sdcards/USB controllers don't understand this SCSI code, the SCSI command fails with "ILLEGAL REQUEST" what ESXi simply reports with this message. (To parse SCSI codes the site at https://www.virten.net/vmware/vmware-esxi-scsi-sense-code-decoder-v2/?scsiCode=failed+H%3A0x0+D%3A0x... is quite handy)
These are just periodic attempts where ESXI queries SMART data from devices which don't support SMART. Nothing to worry about at all.
Regards,
Patrik
FANTASTIC!!!! This is very welcome news indeed!
I am right now patching to u2c !
Thank you for the helpful info!!
JM
Sorry, what i meant to say is that I am patching one more Host to u2c. This makes three.
Anybody else unable to find the U2c patch on vmware's site? All I can view are 7.01 patches and nothing newer. Did VMware pull the patch?
@vmrulz Confirmed - I also can no longer see it in the dropdown on https://customerconnect.vmware.com/patch/ . Curious, but I will withhold further comment until the reason is known.
At this point I am unsure why it does not show up. I have opened a case with GSS seeking more information, and I reached out to some VMware notables on Twitter for comment. Perhaps @LucianoPatrão knows something?
Hi all
You need to select ESXi and version 7.0 only, then you can see the latest patch from 24/08
Do we know if VMware and/or Dell will be making a custom ISO for this ? When you go to the product download page, you can see that they have a new ISO for vCenter 7.0.2 U2c, however the ISO for ESXi is still 7.0.2 U2a.
Ideally i'd like to get the Dell EMC customized ISO for U2c. I know the patches are available in Lifecycle Manager but my concern is potentially having out of date Dell customized add-ons for the image.
I keep checking every day and am surprised that have not released an ESXi ISO for U2c
Agreed. select patches for v 7.0 and its there.
Thanks for the tip, @LucianoPatrão . Duncan pointed out the same via Twitter. I agree that the ESXi 7.0U2c patch shows shows up under ESXi 7.0 (not 7.0.0) dropdown, but this is COMPLETELY inconsistent with the rest of the patch site for 7.x. For example, for vCenter patches, the upgrade for VC-7.0U2c (along with VC-7.0u2, VC-7.0u2a, VC-7.0u2b) is clearly shown in its own 7.0.2 dropdown selection, NOT as links under the VC 7.0.0 selection.
Now you may say, fine, but VC is a different product altogether. Sure, but now lets look at ESXi (Embedded and Installable) on the patch site. The five patch links for version 7.0.1 (VMware-ESXi-7.0U1, VMware-ESXi-7.0U1a, VMware-ESXi-7.0U1b, VMware-ESXi-7.0U1c,and VMware-ESXi-7.0U1d) all appear under a dedicated dropdown selection of the same name 7.0.1 - NOT under the 7.0.0 dropdown and certainly not under the 7.0 dropdown.
Why do 7.0U1a/b/c/d patches appear under a distinct 7.0.1 dropdown, but 7.0U2a/c patches do NOT appear under a distinct 7.0.2 dropdown? It is inconsistent and confusing. IMO. the 7.0 Update2 "c" patch release is a modified version of the 7.0. Update2 release, it is NOT a modified version of the 7.0 release and as such it should follow the convention established by the 7.0.1 patch downloads by having it's own specific 7.0.2 dropdown selection. VMware should either create a separate 7.0.2 selection in the dropdown for the 7.0U2a/c patches, or go back to the method used for 6.7 and prior releases where ALL patches and updates show up under the major revision number selection from the dropdown.
Agreed this is hap hazard versioning at best.. perhaps they were in a hurry to get it out? 😉 I did find it so thanks for the tips on navigating to it all.
Did most of you do the u2c VC patch then ESXi which is the long standing best practice? I'm kind of surprised they did a full 7+ gig ISO release of VC for what is essentially a dot release.
The divergent paths for product upgrades vs patches that VMware has created over the years is just silly. I mistakenly downloaded the VC 7.02c ISO to the tune of 7+ gig and uploaded and attached to a vcenter.. invalid iso. You must download the patch ISO with patch-FP.iso from their other site.. This patch is only 5.5gig. Why on earth don't both ISO's work?
VMware lets start using the KISS principle with your software.
I'm new to ESXi and never patched a host manually.
My environment is 3 hosts with shared storage, one showing as disconnected in vCSA.
I found the patch and I'm ready to do it. Do I have to put the host in Maintenance Mode? Does it need a reboot? Is this the commands to do the update:
esxcli software vib update -d "/vmfs/volumes/DS/patches/VMware-ESXi-7.0U2c-18426014-depot.zip"
Any help is highly appreciated.
@MirceaG wrote:I'm new to ESXi and never patched a host manually.
My environment is 3 hosts with shared storage, one showing as disconnected in vCSA.
I found the patch and I'm ready to do it. Do I have to put the host in Maintenance Mode? Does it need a reboot? Is this the commands to do the update:
esxcli software vib update -d "/vmfs/volumes/DS/patches/VMware-ESXi-7.0U2c-18426014-depot.zip"
Any help is highly appreciated.
Noy, you are not installing a vib, but a patch.
Check my blog post for how to apply the patch manually.
https://www.provirtualzone.com/vmware-finally-launched-esxi-7-0-update-2c/
you can certainly patch that way using an offline bundle
please refer --> https://kb.vmware.com/s/article/2008939
a reboot is needed for the change of build to be effective
you can also patch with LCM
you may refer --> https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-70-vsphere-lifecycle-manag...
or use @LucianoPatrão blog too
@Srijithk wrote:you can certainly patch that way using an offline bundle
please refer --> https://kb.vmware.com/s/article/2008939
a reboot is needed for the change of build to be effective
you can also patch with LCM
you may refer --> https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-70-vsphere-lifecycle-manag...
or use @LucianoPatrão blog too
Sorry @MirceaG my mistake, I did read that you were planning to use the option -v (that is for vibs). Using -d yes you can use to install offline bundle (zip file).
I will also update the blog post to use that option.
I'm running a small home lab. Used a relatively new USB3 stick and reinstalled ESXi 7.0 (it killed the previous USB stick 🙂 ) and applied u2c. After a few days I have experienced the same issue with hostd being unresponsive and recovered with esxcfg-rescan and restarting hostd.
I've consolidated all my VMs on a single datastore (m.2 SSD) and will use the other SATA SSD to install/boot ESXi... Looks like it uses ~138Gb when installing on disks (above a certain size).
I am somewhat tempted to reinstall 6.7...
Please see https://kb.vmware.com/s/article/81166 for how to redue the ESXi 7.0 disk space requirements.
That shouldn't cause any issues in a lab environment.
André