SSL1016 errors that are not posted in chart

[Stanley jenereski]

In the what to do before you call support on the SSL1016 library.

the following errors are not seen

0CE90110
11530208

So as per the chart we should look for "E9" and "53" as to what the problem relates to... but they are not listed. Could someone shed some light on these error messages?

my best as always

[David Ruska · Accepted solution]

I don't see those two errors in the most recent manual.

Can you confirm what drive type you have, and what version of firmware you are running? I'll then talk with the engineering team.

[Stanley jenereski]

Drive type Ultrium 460
FW for drive F59W
FW for the changer 0014

[David Ruska]

Thanks, we'll research these for you. Are these recurring errors, or are they present only once?

[Stanley jenereski]

they are recurring errors and they seem to have no effect "as yet" on the operations

What we are attempting to do is to isolate the media at present.

[David Ruska]

Ok, that helps.

You mentioned 0014 for firmware version, but the only two versions released for the SSL1016 LTO2 were V10 and V20. Can you double check (from the front panel: Status> Autoloader> Version)

Can you clarify if you are seeing these errors under "Hard errors" of "Soft errors"?

Most of the soft errors are not documented, since there is no user recovery or action necessary, and therefore can be ignored.

[Stanley jenereski]

Output from for code revs Survey..

Target Id 0
Logical Unit Id 0
Identifier .................(+) HP UHDL-LTO 0014
Type .......................(+) MediumChangerPeripheral
SerialNumber ...............(+) JG0424AAH00081
DeviceName2 ................(+) MediumChanger0
Target Id 5
Logical Unit Id 0
Identifier .................(+) HP Ultrium 2-SCSI F59W
Type .......................(+) TapePeripheral
SerialNumber ...............(+) HUL5B00356
DeviceName .................(+) Tape0

[Stanley jenereski]

see attachment for errorlog entries

[David Ruska]

> Output from for code revs Survey..

> Identifier .................(+) HP UHDL-LTO 0014

Thanks, that explains it. Apparently this is from a host based tool, and it's diplaying the raw revision field from SCSI inquiry command. For the SSL1016, this is a hex-based ASCII string. 14h = 20, which would be V20 in the front panel and in in LTT.

I'm not familar with the screen shot of error codes. Can I assume they are from a host based tool as well? If so, what tool?

I hope to have an answer back from engineering on the specific error codes you listed, but my guess is there are just internal soft errors.

[Stanley jenereski]

The errors are from the webbase tools..

see the following link on page 104:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00481216/c00481216.pdf

In looking at Quantum's Superloader 3 manual
it shows that an "E9" is a time change
and the "53" is an internal error and the we should recycle the loader??? We did not and it's still running so are these 2 units similar?


my thanks
Stan

[David Ruska]

Stanley,

I'll guess that your screen shot is from the "*** soft queue***" section of the "view errors and history logs" on the Web Admin interface.

As mentioned earlier, soft errors do not require any customer intervention, and the presence of soft errors is normal.

Regarding the Quantum manual, it's certainly possible that they use the same error code set, although the firmware for the HP products is customized to our requirements.

It's possible that the recovery you noted for one of the errors in the Quantum manual applies only if it appears as a hard error.

We'll see what engineering has to say on the particular errors you highlighted.

[Stanley jenereski]

I agree about the soft errors but if they do not mean anything then why alarm the end users?

My only concern is that they are not documented.

again my best/
stan

[Stanley jenereski]

David,

It now appears that we are seeing the errors on a completely different unit.

we tried new and old tapes and it appears that the errors might be logged when the media is loaded or unloaded..

have you heard from your friends in Engineering as yet??

Stan

[David Ruska]

Stanley, yes I did get some responses from engineering.

I'll summarize:

Soft errors (aka "soft queue" events in the web interface history logs) are normal. These are logged by the firmware as a means of providing history, should it be useful by engineering in analysis of unusual hard errors. These "soft queue" events could be something like "no tape detected in slot" or "could not read bar code" during an inventory, and these would be expected errors if the particular slot was empty or the particular tape did not have a bar code.

Because these events can be normal, they are not documented to the end user. Only hard errors should be a concern.

The two particular error codes you asked about have no specific meaning without providing the firmware team with the whole context of events, and unless you are getting a hard error, there is no value in looking at them.

Sorry the documentation doesn't make it clear on the purpose of the "soft queue" history entries.

[Stanley jenereski]

My many thanks.

It was a real pleasure working working with you.

stan