Can you confirm are you using ISO image for upgrade or offline bundle?Nawals
Nawals how are you determining that the smartpqi driver is actually unused by OP? Unless you know this isn't needed by the existing hardware, it's not a good idea to recommend to someone that they blindly remove a driver from a system.
Yeah, I get that, but just because you weren't using that driver and could remove it doesn't mean someone else isn't using it. The error message means the signing can't be verified. Removing it is like taking a sledgehammer to it and not addressing the real issue.
The image I'm using is: HPE-ESXi-6.7.0-Update3-iso-Gen9plus-670.U22.214.171.124.48.iso
The smartpqi driver is at least loaded currently
~] esxcli software vib get -n smartpqi MSCC_bootbank_smartpqi_126.96.36.1990-1OEM.6188.8.131.5298673 Name: smartpqi Version: 184.108.40.2060-1OEM.6220.127.116.1198673 Type: bootbank Vendor: MSCC Acceptance Level: VMwareCertified Summary: SmartPqi Native driver Description: VMware native driver module for Microsemi SmartPqi controllers ...
Okay. So you upgraded ESXi successfully or still facing same issue? Is still facing issue I would suggest to use offline bundle.zip file for upgrade instead of ISO.Nawals
I have not upgraded, as the remediation process fails.
Thanks for the suggestion. i just wonder if the driver is not signed, as I suspect in the ISO, how would an offline bundle be any different? Ofc my experience with this kind of issues is limitedm and I would like to hear your opinion.
Okay. Offline bundle is zip file which you can download from VMware portal based on vendor hardware. This is very easy way to upgrade using single command and reboot.
1. First download customized offline bundle based on hardware model which you are using.
2. Upload to datastore
3. SSH to target ESXi Host
4. Browse datastore using cd /vmfs/volumes
Below given example command for upgrade ESXi using offline bundle.
# esxcli software sources profile list -d "/vmfs/volumes/5b48662e-e1e205e8-92b7-0017a477240c/Mware-ESXi-6.5.0-Update2-9298722-HPE-preGen9-650.U18.104.22.168.3-Sep2018-depot.zip"
Name Vendor Acceptance Level
--------------------------------------------- -------------------------- ----------------
HPE-ESXi-6.5.0-Update2-preGen9-650.U22.214.171.124.3 Hewlett Packard Enterprise PartnerSupported
#esxcli software profile update -d /vmfs/volumes/5b48662e-e1e205e8-92b7-0017a477240c/ISO/VMware-ESXi-6.5.0-Update2-9298722-HPE-preGen9-650.U126.96.36.199.3-Sep2018-depot.zip -p aboveProfilenameNawals
Thanks. I'll try that and see what happens.
I had the same issue with an upgrade on a Dell server. This worked for me. The offline bundle was slighly a version less. Upgrade with original baseline completed after applying this.