2200MX with Legato DiskXtender system SCSI Errors

[Donald Hollander]

IBM x350 Server NT4 OS. 2 adaptec 2944UW diff scsi cards. 10 drive 2200mx.
The error is reported by the Legato software using a message box containing many error details, some of which are Legato specific. Much of the information however looks generic. The SCSI errors are always the same basic error with the drive number usually being different.
Here is a typical error:

ERR 1/24 19:16:04 (0234) [Ms_Iss.cpp, 4295] Drive device error
encountered (16042)
...Library: 233, HP_2200, SCSI.1.0.6.0
...Description: HP C1107
...Drive: 234, Drive 01, SCSI.1.0.5.0
...Description: HP C1113
...Media: 0,
...Serial number:
...Bar code:
...Media shelf: 0
...Label time:
...SCSI error: 16748, XERR_SCSI_DEV_HARDWARE
...Error code: 16042, XERR_DRIVE_HARDWARE
...Command: DRIVE SPIN UP
...SCSI Command: START/STOP UNIT
...CDB: 1b 00 00 00 01 00
...Sector number: N/A
...Sense data: 70 00 04 00 00 00 00 0e
... 00 00 00 00 09 03 00 00
... 00 00 07 02 01 e3 ed 00
... 28 f8 f6 80 c8 1d ed 80
...Bus status: 4h
...Target status: 2h, CHECK CONDITION
...Sense key: 4h, HARDWARE ERROR
...Sense code: 9h/3h

The error seems to happen when the Legato software causes the HP 2200mx to attempt to load a piece of media into a drive. It does *NOT* always happen and the pattern of when is does happen is not clear.

[Steve Kadin]

Donald,

I was wondering if you ever got a solution to your problem listed above. I am having a similar issue however it is during the write proceee rather than the load.

ERR 08/23 11:04:46 (25476) [Ms_Iss.cpp, 3246] Drive device error encountered (16042)
...Library: 992, hp StrorageWorks 2200mx, SCSI.2.0.6.0
...Description: HP C1107
...Drive: 993, Drive 1, SCSI.2.0.5.0
...Description: HP C1113
...Media: 504, ...Serial number:
...Bar code:
...Media shelf: 1
...Label time: Thursday, February 19, 2004 6:51:57 PM
...SCSI error: 16748, XERR_SCSI_DEV_HARDWARE
...Error code: 16042, XERR_DRIVE_HARDWARE
...Command: FILE WRITE
...SCSI Command: WRITE/VERIFY
...CDB: 2e 00 00 00 80 f9 00 00 10 00
...Sector number: 33017
...Sense data: 70 00 04 00 00 00 00 0e
... 00 00 00 00 1b 00 00 00
... 00 00 01 34 00 03 00 00
... 00 00 00 00 00 00 00 00
...Bus status: 4h
...Target status: 2h, CHECK CONDITION
...Sense key: 4h, HARDWARE ERROR
...Sense code: 1bh/0h

[Marino Meloni_1]

It looks like these are two differents error conditions, the first is refered to a disk or media not spinning up, the second one is an error in a write attempt.
For the second one I would suggest to check it there is dust on the media and eventualy clean them with the cleaming media kit. You can also use L&TT to run some test on the media, media validation test ( it is not destructive) read/write test on a scratch or new media, this will let you identify the source of the problem

Fot the first post, I would suggest to record the media which is causing this error, and see if the error is always araising with that or these media, and not with others.

[MattL_1]

We recently had a critical issue with our 4-drive 2200, but it was releated to the DiskXtender drivers and ended up not being anything wrong with the 2200.

We has random blue-screens in Windows and only when we stopped the Legato services in the control panel and set the DiskXtender devices in Device Manager (under View Menu --> Show Hidden Devices). We had to set all 4 items to disabled and rebooted. Once we did that, we were able to run HP's Tape and Library tools against the juke and everything came back OK.

We had to totally reload our DX server and start from scratch.

Might be helpful. Good luck.

Matt

[Gifford]

I get the same error (disk not spinning up) on all four of our drives occasionally. Would the right procedure be to identify the media that is not "spinning up" and then removing it from the library? On our drive number 1 the problem seems to persist. Could it be the drive itself or would this be a case of just the media?

[Marino Meloni_1 · Accepted solution]

Hi Gifford.

From my experience, if you are facing the problem of disk not spinning up, and this clear from the sense code reported, then then problem is comming from the disk, I never see one drive as the cause of this behavior.
I would suggest to isolate all the media that are involved when the error is reported.

Marino

[Donald Hollander]

This issue has been resolved. The problem was with the media. It turns out that we had a bad batch of media. The platters would seize within the cartridge, hence not allowing them to spin and causing the error. As a short-term fix, we were able to manually free the platter by accessing the platter through the sleeve and gently moving the platter. As a long-term fix, HP coordinated with SONY to come to our site and move the platters into new cartridges.

[Donald Hollander]

This issue has been resolved. The problem was with the media. It turns out that we had a bad batch of media. The platters would seize within the cartridge, hence not allowing them to spin and causing the error. As a short-term fix, we were able to manually free the platter by accessing the platter through the sleeve and gently moving the platter. As a long-term fix, HP coordinated with SONY to come to our site and move the platters into new cartridges.