I\u2019ve just spent 3 hours troubleshooting an ESXi 5 host that had the problem with VERY slow boot when using software iSCSI connections to the SAN.\u00a0 VMware has released a patch that supposedly fixed the problem.\u00a0 Well, I\u2019m here to tell you that it has made ZERO difference to the machine in question; in fact, it may have actually made things worse but that is still being determined.<\/p>\n
I have read some other blog posts that indicate the patch has helped on or two other users but in all cases the patch was applied via the vCenter Update Manager and not via the manual process.\u00a0 In my case, it\u2019s all manual as the customer does not have a vCenter.\u00a0 Whatever the case may be, the patch has not resolved the issue of slow boot when software iSCSI is used.\u00a0 I have also seen the oft-mentioned problem of connections to datastores over software iSCSI being \u201cforgotten\u201d or lost after reboot and\/or after the application of the patch.\u00a0 I have definitely seen it in this instance and it was before the patch was applied.\u00a0 I will post an update if I find a solution to the problem but, at this point, I\u2019m really beginning to rue the day I installed ESXi 5.<\/p>\n
VMware has made updated installation ISO\u2019s available to eliminate the problem on new installs but be aware that there are actually 2 ISO\u2019s on offer \u2013 the original \u201cdumb\u201d install and the install that supposedly fixes the iSCSI problem.\u00a0 I\u2019d be interested in knowing if anyone has actually tried a re-installation with the \u201cfixed\u201d ISO and, if so, did it fix the problem?<\/p>\n
UPDATE 1: <\/strong>I’m trying the reinstall myself. \u00a0One nice thing: \u00a0the installer recognizes a pre-exisitng ESXi installation and gives you options to upgrade, install fresh AND maintain the current datastore(s) on the machine. \u00a0This is a welcome change from previous ESXi installers so we’ll see how it goes. \u00a0I have a relatively large locally hoated VM that I had copied off using Veeam SCP, I’ll be happy if I don;t have to copy back on. \u00a0Stay tuned.<\/p>\n UPDATE 2:<\/strong>\u00a0Re-installing ESXi 5 using the patched ISO (ESXi500-201111001, build 504890) has, indeed, solved the problem. \u00a0As mentioned in the Update 1 note, the installer recognized the existing installation and offered to upgrade or install over the original AND keep the datastore intact. \u00a0I elected to install over top of the original install and kept the datastore. \u00a0After the installation completed I rebooted the system and then installed the follow-on patch (ESXi500-201112001, build 515841) and rebooted once more. \u00a0I then reconnected all of the iSCSI datastores and brought up the VM’s without a problem. \u00a0A final shutdown and reboot of the system confirmed a return to normal boot times with iSCSI connections left intact. \u00a0All of this, BTW, was from a Dell R510 connecting to an HP MSA2000i via software iSCSI from Broadcom NIC’s on the R510.<\/p>\n","protected":false},"excerpt":{"rendered":"