Does anyone have any ideas?
Try getting the device IDs as mentioned in this KB article: VMware Knowledge Base
Then check those against the HCL (link in the KB) - it may be that your particular derivative of the card is not supported.
Thanks for the reply.
Yep, it is supported according to the HCL. Here is the output of vmkchdev -l
0000:01:00.0 1000:0073 1000:9240 vmkernel vmhba0
Here is the HCL page
I've just tried installing ESXi 6.7U3 with the custom Lenovo ISO (which includes the Megaraid driver by default) and it picks up the card with no problems.
Have you been able to upgrade the system to 7.0?
I purchased a 9240-8i in hopes of being able to upgrade to 7.0 but am running into the same issue where it's "Unsupported" although the ID's match the HCL entry for 7.0
No, I haven't tried since I got 6.7u3 running.
Are you using a Lenovo server?
I Hope you got the Drivers from VMware Site which meets the Firmware of your Controller and after installing the required Drivers do check if the module is loaded or not
esxcfg-module -q check if Required Module is loaded or not. At times there would be different Module could be loaded you might need to disable to run the correct module.
you can use esxcfg-module -e or esxcfg-module -d . After Enabling/disabling module you need to restart the Server.
Well I did a bit of digging, and it's not detecting because there aren't actually entries in LSI_MR3 for the 9240-8i
According to the KB page, it should be a "VMware Inbox, Native" driver and come bundled with 7.0
My test install of 7.0b reported the version that's supposedly required "7.712.50.00-1vmw.700.1.0.15843807"
Digging through LSI_MR3.map and lsi_mr3.ids I do not see it listed, The only thing remotely close is the Perc H310
I'd expect to see 1000007310009240 in there.
I wonder what would happen if I forcefully added the HWids into the LSI_MR3 tables, using the following guide as a reference....
I tried adding it to the LSI_MR3 and no dice.
I'm going to go out on a limb and say that it's either falsely marked as compatible or there was some sort of retraction from lsi_mr3 at some point?