VMware Cloud Community
ShaneCK
Contributor
Contributor
‎07-15-2016 07:11 PM

ESXi 5.5 FusionIO FW / Software Version 3.2.10 VIB install issues

Hello.  I am very new to this and have only done a few VIB installs.  I followed the directions in the PDF file that came with the driver install.   I am installing this older 320G card in an IBM  x3500M3 tower server.  I copy the ZIP files to the /TMP folder on the host and run the install command.  This is what i get.

/tmp # esxcli software vib install -d /tmp/scsi-iomemory-vsl-5X-3.2.10.1509-offline_bundle-2521850.zip

[DependencyError]

VIBs (Fusion-io_bootbank_scsi-iomemory-vsl_3.2.10.1509-1OEM.500.0.0.472560, VMware_bootbank_esx-base_5.5.0-0.0.1331820) are conflicting with each other

Please refer to the log file for more details.

I have tried googling this many time for answers no luck.  This usually tells me I am doing something wrong and I should know better.  But I cant seem to figure out what I could possibly be doing wrong.

I have tried this on IBM/Lenovo Custom Build ISO images for ESXi 5.5 U3b , U3a, U2 and just the base 5.5 build.   all the same error.

Any help ?     thanks!

0 Kudos
2 Replies
GNV_Javier
Contributor
Contributor
‎10-03-2016 06:25 AM

I am having same issues on NEW build 6.0 Update 2.

esxcli software vib install -d /vmfs/volumes/5429ab2d-12f0f7b3-0ac1-2c44fd96ea68/Fusion/scsi-iomemory-vsl-5X-3.2.8.1350-offline_bundle-1816341.zip

[DependencyError]

VIBs (Fusion-io_bootbank_scsi-iomemory-vsl_3.2.8.1350-1OEM.500.0.0.472560, VMware_bootbank_esx-base_6.0.0-2.43.4192238) are conflicting with each other

Please refer to the log file for more details.

All we are doing is swapping out hardware, HP DL560 G8 and moved to DL560 G9 fresh install.

Cannot remove the "esx-base vib", so any ideas on this would be greatly appreciated.

Thanks

Javier

0 Kudos
ShaneCK
Contributor
Contributor
‎10-23-2016 05:08 PM

hello.   JUST figured this out today.  Had put this on hold for a while. 

I had to use the --force option at the end of the esxcli.....  command.  for both the vsl and block VIBs..

then I reboot the box..

my adapter was "detached"   so from SSH command line i ran a few commands

fio-status   (gives you the status of the card and since mine was an older 640 DUO card it showed me both of the 320G devices. "fct0 and fct1" They were both showing as "detached"

next i ran. fio-format /dev/fct0

then the same for the second.   fio-format /dev/fct1

then i attached them both..

fio-attach /dev/fct0

fio-attach /dev/fct1

now they both show up in the hosts Config / storage adapters tab as "no name provided - vmhba36" and " no name provided -vmhba35"

then just went to storage screen and "add Storage" like normal.  

0 Kudos