I found [a|the?] solution: downgrade to the Intel e1000e 2.5.4-6vmw drivers from 6.0 U1. See VMware KB 2124715 for the file name.
Steps:
- Log into https://my.vmware.com/group/vmware/patch#search
- Select "ESXi (Embedded and Installable)" and "6.0.0". Select the Search button.
- Scroll down and look for the Release Name update-from-esxi6.0-6.0_update01 (released 9/10/2015) . Put a check mark next to it and then Download button to the right.
- Save the file somewhere locally. Open the ZIP archive after it downloads.
- Navigate to the "vib20" directory. Extract the net-e1000e folder. Contained within is the Intel e1000e drivers from ESXi 6.0 U1: VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585.vib
- Transfer this to your ESXi server (either via SCP or even the file browser within the vSphere Thick Client). Save it somewhere you'll remember (i.e. /tmp).
- Login via SSH to the ESXi 6.0 host.
- Issue the command to install it: esxcli software vib install -v /tmp/VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585.vib
- Reboot the ESXi host. Once it comes back online your iSCSI datastore(s)/volumes should return. You can verify by issuing df -h or esxcli storage core device list at the CLI prompt. vSphere Client also works
It took some time to find the right file(s), steps and the commands to use. I hope someone else can benefit from this. I like what VMware can provide for virtualization, but lately it seems their QA department has been out to lunch.
Still do not have a definitive explanation as to why the Intel e1000e drivers from ESXi 5.5 U3 were used when upgrading from ESXi 6.0 U1 to U2. Perhaps someone with more insight or VMware Support person can.
&out
-- G