Welcome! » Log In » Create A New Profile

Jukebox xxx failed: Hardware Error, Diagnostic Failure

Jukebox xxx failed: Hardware Error, Diagnostic Failure
March 07, 2009 09:50AM
Greetings,

I've recently started receiving this message when performing things that are
routine (deposit, eject, re-label). This list archives suggest that this
might be an upside-down tape, but we are using SL500 w/ LTO3; i don't think
it's physically possible to successfully insert a badly oriented tape.

I attempted to run jbverify but, despite that nsrwatch and nwadmin report
empty drives, it attempted to eject them, with the drive issueing an error
in response "No tape in device." Hence the drive failed the jbverify.

For fun, I loaded the drives with tapes, and attempted jbverify again, and I
received this exact message as described by the man page:

Unable to proceed to test drive <no>(<name>) in JB
<name> as device is still loaded!

(= jbverify failure)

Is there any obvious reason why jbverify would be so confused as to the
status of the drive's load state vs. nwadmin/nsrwatch's source of
information?

--
Regards,
Eugene Vilensky
evilensky < at > gmail.com

via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
Jukebox xxx failed: Hardware Error, Diagnostic Failure
March 08, 2009 05:06AM
[quote]From: Eugene Vilensky <evilensky < at > GMAIL.COM>
Reply-To: EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>, Eugene
Vilensky <evilensky < at > GMAIL.COM>
Date: Sat, 7 Mar 2009 11:49:37 -0600
To: <NETWORKER < at > LISTSERV.TEMPLE.EDU>
Subject: [Networker] "Jukebox 'xxx' failed: Hardware Error, Diagnostic Failure
on Component 0x01"

Greetings,

I've recently started receiving this message when performing things that are
routine (deposit, eject, re-label). This list archives suggest that this
might be an upside-down tape, but we are using SL500 w/ LTO3; i don't think
it's physically possible to successfully insert a badly oriented tape.

I attempted to run jbverify but, despite that nsrwatch and nwadmin report
empty drives, it attempted to eject them, with the drive issueing an error
in response "No tape in device." Hence the drive failed the jbverify.

For fun, I loaded the drives with tapes, and attempted jbverify again, and I
received this exact message as described by the man page:

Unable to proceed to test drive <no>(<name>) in JB
<name> as device is still loaded!

(= jbverify failure)

Is there any obvious reason why jbverify would be so confused as to the
status of the drive's load state vs. nwadmin/nsrwatch's source of
information?
[/quote]
You didn't provide any information on your server configuration or how your
tape library is connected to its server. Have you verified that the OS can
see the library and its tape devices?

via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
Jukebox xxx failed: Hardware Error, Diagnostic Failure
March 08, 2009 08:37AM
[quote]

You didn't provide any information on your server configuration or how your
tape library is connected to its server. Have you verified that the OS can
see the library and its tape devices?
[/quote]

Networker 7.2.2 on RHEL3. The tape library is fibre-connected along with
the drives. Yes the OS itself recognizes the tape drives fine, and I can
perform any nwadmin operations without trouble, and backups/restores are
working.

--
Regards,
Eugene Vilensky
evilensky < at > gmail.com

via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
Sorry, only registered users may post in this forum.

Click here to login