Hi there,
We're currently running a SQL server as a Hyper-V VM with iSCSI mounted volumes, using MPIO (two ports). We're getting occasional disconnects of our primary DB volume that is, understandably, causing SQL to be unhappy. The event chronology looks like this:
Event ID 32 iScsiPrt - Initiator received an asynchronous logout message. The Target name is given in the dump data.
Event ID 27 iScsiPrt - Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iSCSI header.
Event ID 27 iScsiPrt - Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iSCSI header.
Event ID 34 iScsiPrt - A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.
Event ID 23 mpio - All paths have failed. \Device\MPIODisk5 will be removed.
Event ID 16 mpio - A fail-over on \Device\MPIODisk5 occurred.
At this point, the logical DB drive disappears from Windows and the iSCSI initiator shows as Inactive. When we reconnect, it connects no problem but we usually need a reboot to get SQL happy again.
Back end storage is an EqualLogic SAN running the 3.4.2 HIT kit. We have recently installedKB978157, which didn't seem to help.
Has anyone run into anything like this before?
- Liam