I have a power Edge R520 server installed with Dell-ESXi-5.5U2-2068190-A00
I have uploaded the ESX 6.5U1 ISO image (not the custom Dell one)
Update manager returns:
The upgrade contains the following set of conflicting VIBs:
LSI_bootbank_scsi-mpt3sas_04.00.00.00.1vmw-1OEM.500.0.0.472560
LSI_bootbank_scsi-mpt3sas_04.00.00.00.1vmw-1OEM.500.0.0.472560
Remove the conflicting VIBs or use Image Builder to create a custom upgrade ISO image that contains the newer versions of the conflicting VIBs, and try to upgrade again.
After checking VMWare documentation I found the following article:
Scsi-mpt3sas This is a driver VIB provides ‘mpt3sas’ driver which enables support for AVAGO MPT Fusion based SAS3 (SAS 12.0 Gb/s) Controller(s). Dell don’t support this device and hence this driver can be safely removed.
I try to remove it but cannot find the correct VIB name
~ # esxcli software vib list|grep LSI
scsi-megaraid-perc9 6.901.55.00-1OEM.550.0.0.1331820 LSI VMwareCertified 2014-08-27
scsi-mpt2sas 18.00.00.00.1vmw-1OEM.550.0.0.1198610 LSI VMwareCertified 2014-08-27
scsi-mpt3sas 04.00.00.00.1vmw-1OEM.500.0.0.472560 LSI VMwareCertified 2014-08-27
~ # esxcli software vib remove --vibname scsi-mpt3sas
[NoMatchError]
No VIB matching VIB search specification 'scsi-mpt3sas'. Please refer to the log file for more details.
Hi Sangoka,
Can you please try with -f option. It should be removed.
esxcli software vib remove -f --vibname scsi-mpt3sas
Regards
Amol
Just out of curiosity, why are you trying to use a non-Dell image on a Dell server? I would highly recommend otherwise, as Dell image contains up-to-date drives required for stable hypervisor operation.
Hi, did you find any solutions for your problem?
i got the same problem, but when i try to delete the vib it says - cannot delete vib online.
I got an dell image, the host is in maint mode
i think that a 5.0 driver creates an unresolved dependency. So search for
esxcli software vib list | grep -i 500
What ever it lists..... remove it, reboot and try upgrading again.
Regards,
Joerg
Thank you so much Joerg, this was exactly my issue!!!
-joel
This was also exactly my problem. Thanks so much for the fix!!!