Hi Hi , As you are using iSCSI for SAN connection, please apply the following hotifxes. Msiscsi.sys http://support.microsoft.com/kb/2614956 Storport.sys http://support.microsoft.com/kb/2654363 Msdsm.sys http://support.microsoft.com/kb/2460971 MPIO.SYS http://support.microsoft.com/kb/2661794 For the event id 39, please see: In Windows Server 2008 or Windows Server 2008 R2 environment, if the network environment is set to enable Delay ACK and storage is connected with iSCSI, an iScsiPrt error is output to the System Event Log when a general operation is executed http://support.microsoft.com/kb/981482 Please also try to update the NIC driver, use dedicated NIC for iscsi connection. For more infomration about Iscsi network best practice, please see: http://download.microsoft.com/download/a/e/9/ae91dea1-66d9-417c-ade4-92d824b871af/uguide.doc Also disable TCP offload and RSS on the NIC for iscsi connection. For more information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008, please see: http://support.microsoft.com/kb/951037/en-us For Event ID 15, Event ID 15 indicates that the device is not ready. This can be the result of SCSI host adapter configuration issues or other problems. Check with the manufacturer for updated firmware, drivers, or known issues. This could also indicate a malfunctioning device. This error occurs at the device level. In almost all cases, these messages are being posted due to hardware problems with either the controller or, more likely, a device that is attached to the controller in question. The hardware problems can be associated with poor cabling, incorrect termination or transfer rate settings, lazy or slow device responses to relinquish the SCSI bus, a faulty device, or, in very rare cases, a poorly written device driver. For more information, please see: How to troubleshoot event ID 9, event ID 11, and event ID 15 error messages http://support.microsoft.com/kb/154690 In summary, we should check the network for the 39 and 9 event. Check with the storage vendor for event ID 15. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I have a client who reached out to us yesterday. They recently purchased and installed a new DELL R610 front end server along with an Equalogic 6500 SAN. They have installed Windows Server 2008 R2 SP1 64 bit and SQL Server 2008 R2 SP1 64 bit on the front end server and are configuring the SAN for the database files. The SAN is connected via iSCSI with 4 HBA ports configured for MPIO. Before doing any further setup they thought they would test some of the IO and configuration to make sure it was performing with error and optimized. They installed Microsoft Baseline Configuration Analyzer 2.0. They are going to contact Dell to make sure that they truly do have all of the latest firmware loaded. Based on our discussion yesterday they felt they already did but would double check. We also pointed them to following hotfix based on a previous incident regarding this which this corrected although it was an EMC SAN. http://support.microsoft.com/kb/2522766 They are seeing the following errors when they run MBCA2.0... "I/O request related events were detected on this system. This could be due to a faulty storage device, improper configuration or problems with the device drivers and firmware that interact with the devices. (EventId: 15 Occurrences: 28)" In reviewing the Windows Event Viewer we do not see any EventID errors. We do however see the following errors being reported. EventID: 39EventID: 9 1. Where are the EventID 15 coming from or being stored/written to if they do not show up in the Windows Event Log? 2. Any thoughts on what this issue might from or next steps in troubleshooting as the configuration appears to be correct based on our initial review? 3. Thoughts and comments on the EventID 39 and EventID 9 errors? The one item of concern for me and I am trying to get some additional information for their setup is that the DELL R610 had an onboard Broadcom 4 port NIC and a SCSI Intel 4 port NIC. They appeared to both be configured and active.

Hi, Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support. Best Regards, AidenAiden Cao TechNet Community Support

Hi Hi , As you are using iSCSI for SAN connection, please apply the following hotifxes. Msiscsi.sys http://support.microsoft.com/kb/2614956 Storport.sys http://support.microsoft.com/kb/2654363 Msdsm.sys http://support.microsoft.com/kb/2460971 MPIO.SYS http://support.microsoft.com/kb/2661794 For the event id 39, please see: In Windows Server 2008 or Windows Server 2008 R2 environment, if the network environment is set to enable Delay ACK and storage is connected with iSCSI, an iScsiPrt error is output to the System Event Log when a general operation is executed http://support.microsoft.com/kb/981482 Please also try to update the NIC driver, use dedicated NIC for iscsi connection. For more infomration about Iscsi network best practice, please see: http://download.microsoft.com/download/a/e/9/ae91dea1-66d9-417c-ade4-92d824b871af/uguide.doc Also disable TCP offload and RSS on the NIC for iscsi connection. For more information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008, please see: http://support.microsoft.com/kb/951037/en-us For Event ID 15, Event ID 15 indicates that the device is not ready. This can be the result of SCSI host adapter configuration issues or other problems. Check with the manufacturer for updated firmware, drivers, or known issues. This could also indicate a malfunctioning device. This error occurs at the device level. In almost all cases, these messages are being posted due to hardware problems with either the controller or, more likely, a device that is attached to the controller in question. The hardware problems can be associated with poor cabling, incorrect termination or transfer rate settings, lazy or slow device responses to relinquish the SCSI bus, a faulty device, or, in very rare cases, a poorly written device driver. For more information, please see: How to troubleshoot event ID 9, event ID 11, and event ID 15 error messages http://support.microsoft.com/kb/154690 In summary, we should check the network for the 39 and 9 event. Check with the storage vendor for event ID 15. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.