Note: Before proceeding, ensure that there is sufficient free ramdisk space on the ESXi host.
For more/related information, see:
To resolve this issue, you must reinitialize the iSCSI configuration.
To reinitialize the iSCSI configuration:
- Log in to the ESX/ESXi host as the root user.
- Run this command to disable the Software iSCSI initiator:
# esxcfg-swiscsi -d
- In the ESX/ESXi host, rename all files in the /etc/vmware/vmkiscsid folder . This folder contains these files:
- initiatorname.iscsi
- iscsid.conf
- vmkiscsid.db
To rename the files, run these commands:
# mv initiatorname.iscsi initiatorname.iscsi.old
# mv iscsid.conf iscsid.conf.old
# mv vmkiscsid.db vmkiscsid.db.old
Additional files, such as vmkiscsid.db-journal, if present, must also be renamed.
- Reboot the ESX/ESXi host.
- After rebooting the host, run this command to re-enable the Software iSCSI initiator:
# esxcfg-swiscsi -e
Note: A new software iSCSI initiator ID is generated. This IQN needs to be added to the SAN.
- Run this command to scan for disks that are available through the Software iSCSI interface:
# esxcfg-swiscsi -s
Notes:
- If iSCSI re-initialization still does not allow the host to detect presented LUNs, try rebooting the physical network switch.
- Any virtual machines housed on temporarily disconnected LUNs may have to be re-added to inventory.