And you have noticed that usually it hangs at:
- Loading VMkernel ‘HBA driver name’ i.e. Loading VMkernel qla2300_707_vmw.0 (options: ”) or
- Loading lvmdriver or eventually
- Loading vmfs3
If you look at the vmkernel log, you will see something similar to this:
SCSI: vm 1043: 5522: Sync CR at 64
SCSI: vm 1043: 5522: Sync CR at 48
SCSI: vm 1043: 5522: Sync CR at 32
SCSI: vm 1043: 5522: Sync CR at 16
SCSI: vm 1043: 5522: Sync CR at 0
WARNING: SCSI: 5532: Failing I/O due to too many reservation conflicts
WARNING: SCSI: 5628: status SCSI reservation conflict, rstatus 0xc0de01 for vmhba1:0:7. residual R 919, CR 0, ER 3
WARNING: J3: 1970: Error committing txn to slot 0: SCSI reservation conflict
Here is a tweak to speed up the boot process, but also the HBAs scans!
In the host configuration -> Advance Setting -> Scsi -> SsciRetries.
Default value is 80, recommended value is 10.
Or putty in and use this command: esxcfg-advcfg -s 10 /Scsi/ConflictRetries
After the change, do a scan HBAs and you’ll see an immediate improvement.
Obviously you will have to reboot the host to see the effect at boot time.
One recommendation though, if you have many many guests on your VMFS volumes, you may need to increase that number and eventually set it back to the default value of 80.
Source: VMware Communities