Medium Changer drivers won't bind to Emulex HBAs (Host Bus Adapters) using STORport drivers

Details:

When using some Emulex HBA with the Emulex STORport drivers (elxstor.sys), the medium changers drivers won't bind. The following symptoms and errors will also show in the ADAMM (Advanced Device and Media Management) log. In this sample from the "Device Registry" section of the ADAMM.log, notice that the port driver is "elxstor" and the quotes are empty instead of "<\\.\MediumChanger0>"

0004:0000:0000:0000 "elxstor", (Port Driver)

0004:0000:0000:0000 "STK L700 2.21", (Changer Device), ""

0004:0000:0000:0001 "STK T10000A 127", (Tape Device), "<\\.\Tape0>"
0004:0000:0000:0002 "STK T10000A 127", (Tape Device), "<\\.\Tape1>"
0004:0000:0000:0003 "STK T10000A 127", (Tape Device), "<\\.\Tape2>"

In this sample from the "Device Discovery" section of the ADAMM.log, notice the empty quotes next to device name instead of "<\\.\MediumChanger0>" and note the "ERROR_INVALID_NAME" in the Device state.

0004:0000:0000:0000 Device Name ""

Primary Inquiry "STK L700 2.21"

Serial Number ""

Device Flags KMD, SCSI

Device State 1, Offline, ERROR = 0x0000007B (ERROR_INVALID_NAME)

Current Emulex drivers are dependent on newer releases of STORPort from Microsoft. At the time of publishing, Emulex requires the Hotfix from Microsoft be applied for the following issue:

Stop error that is related to the Storport.sys driver on a Windows Server 2003-based computer: "0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL" http://support.microsoft.com/kb/945119

If the library is a UMD (User Mode Driver) device, it will continue to function properly.
If the library is a KMD (Kernel Mode Driver) device, it will NOT function until this issue is resolved.
Affected Operating System: Windows 2003 only. Windows 2008 already has a new enough STORport driver. Windows 2000 doesn't use STORport drivers.
This affects all versions of Backup Exec for Windows Servers.

Note: Emulex is aware of this issue and researching the scope of the problem.

Related Documents:

http://support.veritas.com/docs/255501

http://support.veritas.com/docs/258336

http://support.veritas.com/docs/282249

http://support.veritas.com/docs/294294

http://support.veritas.com/docs/306831

Acknowledgements
Emulex and Microsoft

Products Applied:
Backup Exec for Windows Servers 11d (11.0), 11d (11.0) 6235, 11d (11.0) 7170, 12.0, 12.5

Last Updated: July 14 2009 03:13 PM GMT
Expires on: 10-07-2009

Subscribe to receive critical updates about this document

Subjects:
Backup Exec for Windows Servers
Application: Troubleshooting

Languages:
English (US)

Operating Systems:
Windows Server 2003

Enterprise Server

Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.