http://blogs.technet.com/b/askcore/archive/2007/11/09/symptom-based-cluster-disk-failure-troubleshooting.aspxOne of the most common issues with Windows Failover clustering deals with the storage attached to the cluster. This post is meant to give a very high-level overview to disk troubleshooting methodologies and how to narrow down the source of problems evenen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/askcore/archive/2007/11/09/symptom-based-cluster-disk-failure-troubleshooting.aspx#3214180Tue, 17 Mar 2009 21:45:49 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3214180KateBorisov<p>- Disk resource fails on one node but works on the other node(s) - another possible reason: </p> <p>For Microsoft iSCSI architecture if there are no network connectivity problems and SAN integrity is checked, verify if iSCSI Initiator is up-to-date in Device Manger -&gt; SCSI and RAID Controllers. If not, install the latest applicable version.</p> <p>The installation packet includes </p> <p>- iSCSI Port Driver (iscsiprt) </p> <p>- Initiator Service (iscsiexe.exe)</p> <p>- Software Initiator &nbsp;(msiscsi.exe) </p> <p> This is the kernel mode iSCSI software initiator driver and is used to connect to iSCSI devices via the Windows TCP/IP stack using NICs.</p> <p>- Microsoft MPIO Multipathing Support for iSCSI</p> <p>Reference: uGuide.doc </p> <p><a rel="nofollow" target="_new" href="http://www.microsoft.com/downloads/details.aspx?familyid=12CB3C1A-15D6-4585-B385-BEFD1319F825&amp;displaylang=en">http://www.microsoft.com/downloads/details.aspx?familyid=12CB3C1A-15D6-4585-B385-BEFD1319F825&amp;displaylang=en</a> </p><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3214180" width="1" height="1">