We have couple of Dell R630 with Dell 12Gbps SAS HBA connected to Compellent SCv2020. We use DELL-ESXi-6.0U3-5224934-A01 and mpt3sas driver instead of default lsi-msgpt3. I can see four "Sanity check failed for path vmhba2:C0:T[0,1]:L25[6,7]. The path is to a vVol PE, but it goes out of adapter vmhba2 which is not PE capable. Path dropped." messages every five minutes. I did not find any SAS I/O driver with Secondary LUNID (Enables VVols) feature in Compatibility Guide so I don't understand why this messages appear. Is it a side-effect that an iscsi_vmk driver (VVol PE capable) is used on this hosts?
Have you also had a chance to look at VMware Virtual Volumes (VVols) operation fails with the error: Sanity check failed for path vmhbaX:Y... ?
did you find a solution of this case?
I have the same problem with Dell Server with SAS HBA
Have anyone a solution for this case?
There are two solutions -
1) Upgrade the HBA driver to a version that is capable of identifying Second Level LUN ID (in turn understanding vVOL).
2) Since most of the local SAS controller drivers do not support Second Level LUN ID feature, there are three workarounds -
-----> Ignore the warnings, as these are harmless in a non-vVOL environment.
-----> Do not present any devices with a LUN ID greater than 255. This can be controlled/configured from the controller/storage front.
-----> Configure software LUN masking on the ESXi so that it does not see any LUN/device having a LUN ID higher than 255. However, this option is not at all recommended owing to obvious reasons.
Even i had the same issue with the upgraded 6.5 host, It solved by installing the latest SCSI drivers.
Description Type Date Time Task Target User
"Sanity check failed for path vmhba34:C0:T1:L256. The path is to a vVol PE, but it goes out of adapter vmhba34 which is not PE capable. Path dropped." Error 26/11/2018 15:45:51 ukXXXXXXXX
In my case it was scsi-bnx2fc 1.713.20.v55.4-1OEM.522.214.171.1241820 QLogic VMwareCertified --causing issue.
It got fixed after installing scsi-bnx2fc 1.713.20.v60.4-1OEM.600.0.0.2494585 QLogic VMwareCertified .
its solved and my kernel is free from errors.
check for your respective vendor and install the latest drivers.