You are experiencing these issues:

• iSCSI initiator cannot find any targets presented to it
• ESX host cannot connect to iSCSI array
• iSCSI fails
• After issuing a rescan, /var/log/messages reports:
  
  iscsid[8034]: open of discovery file /var/lib/iscsi/vmkdiscovery failed: No such file or directory
  iscsid[8034]: init of discovery file failed: No such file or directory
  iscsid[8034]: config file line 527 too long
  iscsid[8034]: failed to load configuration from /etc/vmkiscsi.conf
  
  
• After issuing a rescan, /var/log/vmkernel reports:
  
  Sep 26 13:50:49 vmkernel: 0:00:00:22.904 cpu3:1249)Sched: vm 1379: 1031: name='vmkiscsid'
  Sep 26 13:50:49 vmkernel: 0:00:00:22.904 cpu3:1249)CpuSched: vm 1379: 13910: zombified unscheduled world: runState=NEW
  Sep 26 13:50:49 vmkernel: 0:00:00:22.904 cpu3:1249)World: vm 1379: 2483: deathPending set; world not running, scheduling reap

1. Edit /etc/vmkiscsi.conf to add a carriage return after the final line of the file (this should be the discovery target).
2. Disable and re-enable the Software iSCSI initiator:
   
   
   1. Disable using the command:
      
      esxcfg-swiscsi -d
      
      
   2. Enable using the command:
      
      esxcfg-swiscsi -e
      
      
   3. Verify the initiator is running using the command:
      
      esxcfg-swiscsi -q
      
      
   4. Scan for new targets using the command:
      
      esxcfg-swiscsi -s
      
      
3. Open the VMware Infrastructure Client and rescan SAN by clicking Configuration > Storage Adapters > Rescan SAN.