Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem Accessing EML103e from Windows 2003

Phillip Thayer
Esteemed Contributor

Problem Accessing EML103e from Windows 2003

I have a Windows 2003 Standard Edition SP2 server with two tape libraries connected to it.
1. VLS1000
2. EML103e

The Windows server is running as a VMWare instance.

When I do the hardware scan on the Windows 2003 server it finds both the libraries and tape drives.

When I try to run the L&TT utility it is able to access the VLS Identity information with no problem. I can see the library and the one tape drive that I have configured on it.

When I try to access the EML103e Identity information the L&TT utility will go through and read the information from the library but when it tries to access the tape drives it gives me an error that goes something like this:

The diagnostic functions are operating in restricted mode. Some functions may be disabled or limited while operating in restricted mode.

The restricted mode is entered if the Product ID is not properly recognized, or if the device operates in 'boot code' and requires a firmware update.

When I click on the "OK" button then the L&TT goes to a status report window and tries to send the file that I have attached.

Can anybody help me figure out what is wrong with the EML103e?

Thanks,
Phil
Once it's in production it's all bugs after that.
7 REPLIES
Phillip Thayer
Esteemed Contributor

Re: Problem Accessing EML103e from Windows 2003

More information:

In the file C:\Program Files\HP StorageWorks Library and Tape Tools\logs\Eventlog.ltt are the following error entries:

10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.2.1.0:enu
10:4:4:40:3:3:42:1:1:PlainText:SCSI Error Status = 2126:1252:0
10:1:4:67:0:0:0x88040001:1182466081:1182466081:0:1:8:0:0
(repeated 10 times. then)
10:3:4:40:2:3:41:1:1:s_system:4.2.1.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Write Back data read failure for device at path :1252:0
10:1:4:76:42:0:0x28001012:1182466082:1182466082:0:1:8:0:0
10:3:4:40:2:3:41:1:1:s_system:4.2.1.0:enu
10:4:4:40:3:3:42:1:1:PlainText:SCSI Write Buffer command may not reach to a device:1252:0
10:1:4:79:0:0:0x88040001:1182466144:1182466144:0:4:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.2.1.0:enu
10:4:4:40:3:3:42:1:1:PlainText:SCSI Write Buffer command may not reach to a device:1252:0
10:1:5:80:0:0:0x28040001:1182466144:1182466144:0:4:8:0:6
10:2:5:40:1:3:120:50:0:0
10:3:5:40:2:3:41:1:1:s_system:4.2.1.0:enu
10:4:5:40:3:3:42:1:1:PlainText:Write Back data write failure for device at path 3/0.2.0:1252:0
10:5:5:1:1:1:0:6:00 01 46 7B 00 60
10:1:4:81:77:0:0x28001016:1182466144:1182466144:0:1:8:0:0

Not sure if this will help at all but figured since I found it I would put it here. I am attaching the Eventlog.ltt file here.

Phil
Once it's in production it's all bugs after that.
Curtis Ballard
Honored Contributor

Re: Problem Accessing EML103e from Windows 2003

The error code being returned by the OS for the drive reports that it is reserved by another HBA (I/O error 2126) so apparently something in your system has opened the drive for exclusive access.

The error message on restricted mode isn't as clear as it should be. L&TT was able to identify the device but can't communicate with it is what the message really means. In this case the OS will allow an inquiry and probably never even sends that command on to the drive so L&TT can identify the drive but the OS won't allow any commands that try to access the device.
Phillip Thayer
Esteemed Contributor

Re: Problem Accessing EML103e from Windows 2003

The only other software I have installed on this sytem is FSE and FMA but they are not configured yet. Is it possible that these are grabbing the tape drives? Also, is it possible that VMWare might not be handling the tape drives correctly?

Phil
Once it's in production it's all bugs after that.
Curtis Ballard
Honored Contributor

Re: Problem Accessing EML103e from Windows 2003

I haven't worked with VMWare or the other software you mention enough to say whether they could be reserving the device but it's always possible.

I hate to ask since it's become second nature but have all the Windows storage services been disabled?
Phillip Thayer
Esteemed Contributor

Re: Problem Accessing EML103e from Windows 2003

I disabled the Removable Storage manager. is there any other Windows services that should be disabled?
Once it's in production it's all bugs after that.
Curtis Ballard
Honored Contributor

Re: Problem Accessing EML103e from Windows 2003

Server 2003 also needs test unit ready polling disabled but RSM is the only service that should be reserving the devices.
Phillip Thayer
Esteemed Contributor

Re: Problem Accessing EML103e from Windows 2003

Still unresolved but got pulled off this to work on some other projects.
Once it's in production it's all bugs after that.