05-09-2012 03:40 PM
I have a drive in my ADIC i2K that I can't get to stay up. I almost want to say it's a hardware issue, but the library seems to think the drive is fine. I have turned on the VERBOSE for the logging and see a couple of cryptic errors that i'm not sure are normal or not.
When I try to do a cleaning I get this:
16 2 2144775 0 srvlcnbs01 *NULL* nbjm NBU status: 98, EMM status: The media server reported a system error
This error really worries me....
Unknown robot number 1, from host srvlcnbs01
With my errors, I would expect this one:
TLD(0) [9988] GetTapeParameters for drive 1 (device 3) returned: The device is not ready.
THis is what I think the problem is caused by:
TLD(0) [9988] Unload requested, but no unload, drive 1 (device 3)
I have physically looked and confirmed that there is nothing in the drive.
If I use Robtest to move a cleaning tape to the drive for testing I get this:
TLD(0) key = 0x5, asc = 0x3b, ascq = 0xd, MEDIUM DESTINATION ELEMENT FULL
Any suggestions? I have physically power cycled the drive, the media server, and the Master server.
Running NBU 7.01 on W2K3
.
Solved! Go to Solution.
05-10-2012 06:25 AM
Hi Dan,
What you see in Robtest is 100% for certain sent from the library.
Therefore, it is the drive/ library that is having the issue not NetBackup. No amount of poking, prodding or tickling NetBackup will clear this.
NetBackup does not 'look' in a library, it actually asks the library, show me what is in the slots/ drives etc ...
So, to resolve this issue, forget NBU and look at library / drive issues.
I would recommend a powercycle of the drive (a proper on/ off, not a reset from the library console). If this does not resolve, power cycle the whole library, if this doesn't work, I afraid it is time to log a hardware call.
From this link http://www.symantec.com/docs/TECH169477
Although this isn't quite an invemtory, this description from the TN is close enough to be valid.
I hope this helps,
Martin
PS.
Also, ASc/ ASCQ errors as seen (sense key = 0x5, asc = 0x3b, ascq = 0xd) are also sent from the hardware and are only displayed by NBU. The technote also covers these.
05-09-2012 03:51 PM
Just found this error...I think I need to delete the device and re-add it....
Fatal open error on HG_LTO_1 (device 3, \\.\Tape3): The system cannot find the file specified. DOWN'ing it
05-09-2012 04:27 PM
It's possible it's a bad drive, seeing as it seems like it thinks it has media in it. I would try removing it and re-adding it via the wizard to see if it rediscovers/resets the state to EMPTY. Are you seeing any problems within your event log or the device manager/tree?
05-09-2012 05:43 PM
Those errors are from the Event log.
05-09-2012 10:45 PM
i need this info plz:
master OS, Media OS, this error where you get from master or media server, Are you have seen tape deive down in GUI, are there any frozen media tapes.
05-10-2012 01:59 AM
05-10-2012 03:45 AM
Hi Dan
That can be caused by the driver not being loaded for that tape in the windows system
Some times a Update Driver Software can fix the isssue
Regards
Michael
05-10-2012 05:35 AM
Here is the s d output.
s d
drive 1 (addr 256) access = 1 Contains Cartridge = yes
Sense code = 0x83, Code qualifier = 0x0
Barcode =
drive 2 (addr 257) access = 0 Contains Cartridge = yes
Source address = 4483 (slot 388)
Barcode = 005320
drive 3 (addr 258) access = 0 Contains Cartridge = yes
Source address = 4260 (slot 165)
Barcode = 005500
drive 4 (addr 259) access = 0 Contains Cartridge = yes
Source address = 4467 (slot 372)
Barcode = 005321
drive 5 (addr 260) access = 0 Contains Cartridge = yes
Source address = 4466 (slot 371)
Barcode = 005322
drive 6 (addr 261) access = 0 Contains Cartridge = yes
Source address = 4389 (slot 294)
Barcode = 005474
READ_ELEMENT_STATUS complete
You can see that it thinks there is a tape in the drive (Drive 1) even though there physically isn't.
I can't provide the s s command as I have a 400 slot library and that will take a while.
Here is the move error:
m s291 d1
Initiating MOVE_MEDIUM from address 4386 to 256
move_medium failed
sense key = 0x5, asc = 0x3b, ascq = 0xd, MEDIUM DESTINATION ELEMENT FULL
Here is the scan out put.
Scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 2; Bus: 0; Target: 0; LUN: 3
Inquiry : "IBM ULTRIUM-TD2 A4N0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "A4N0"
Serial Number: "F00187B007"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 F00187B007"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape1"
Passthru Name: "Tape1"
Volume Header: ""
Port: 2; Bus: 0; Target: 0; LUN: 5
Inquiry : "IBM ULTRIUM-TD2 A4N0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "A4N0"
Serial Number: "F00187B013"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 F00187B013"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape2"
Passthru Name: "Tape2"
Volume Header: ""
Port: 2; Bus: 0; Target: 1; LUN: 3
Inquiry : "IBM ULTRIUM-TD2 A4N0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "A4N0"
Serial Number: "F00187B01F"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 F00187B01F"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : ""
Passthru Name: ""
Volume Header: ""
Port: 4; Bus: 0; Target: 2; LUN: 1
Inquiry : "ADIC Scalar i2000 607A"
Vendor ID : "ADIC "
Product ID : "Scalar i2000 "
Product Rev: "607A"
Serial Number: "ADIC203101167_LL0"
WWN : ""
WWN Id Type : 0
Device Identifier: "ADIC 203101167_LL0 "
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 6
Number of Slots : 402
Number of Media Access Ports: 24
Drive 1 Serial Number : "F00187B001"
Drive 2 Serial Number : "F00187B007"
Drive 3 Serial Number : "F00187B00D"
Drive 4 Serial Number : "F00187B013"
Drive 5 Serial Number : "F00187B019"
Drive 6 Serial Number : "F00187B01F"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 4; Bus: 0; Target: 2; LUN: 2
Inquiry : "IBM ULTRIUM-TD2 A4N0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "A4N0"
Serial Number: "F00187B001"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 F00187B001"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape4"
Passthru Name: "Tape4"
Volume Header: ""
Port: 4; Bus: 0; Target: 2; LUN: 4
Inquiry : "IBM ULTRIUM-TD2 A4N0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "A4N0"
Serial Number: "F00187B00D"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 F00187B00D"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape5"
Passthru Name: "Tape5"
Volume Header: ""
Port: 4; Bus: 0; Target: 3; LUN: 2
Inquiry : "IBM ULTRIUM-TD2 A4N0"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "A4N0"
Serial Number: "F00187B019"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 F00187B019"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
05-10-2012 05:46 AM
Do you recommend the Symantec driver or the Quantum driver?
05-10-2012 06:25 AM
Hi Dan,
What you see in Robtest is 100% for certain sent from the library.
Therefore, it is the drive/ library that is having the issue not NetBackup. No amount of poking, prodding or tickling NetBackup will clear this.
NetBackup does not 'look' in a library, it actually asks the library, show me what is in the slots/ drives etc ...
So, to resolve this issue, forget NBU and look at library / drive issues.
I would recommend a powercycle of the drive (a proper on/ off, not a reset from the library console). If this does not resolve, power cycle the whole library, if this doesn't work, I afraid it is time to log a hardware call.
From this link http://www.symantec.com/docs/TECH169477
Although this isn't quite an invemtory, this description from the TN is close enough to be valid.
I hope this helps,
Martin
PS.
Also, ASc/ ASCQ errors as seen (sense key = 0x5, asc = 0x3b, ascq = 0xd) are also sent from the hardware and are only displayed by NBU. The technote also covers these.
05-10-2012 10:58 PM
Can you try to move this ghost tape in the drive to some empty slot? Try and check if physical tape is moved to destination slot.
As Martin wrote, robtest just displays info/code provided by your library. If the drive is really empty, there are something wrong with i2000.
05-11-2012 12:34 AM
No amount of poking, prodding or tickling NetBackup will clear this.
LOL! Really enjoyed your EXCELLENT post, Martin!
05-11-2012 12:50 AM
Thanks Marianne ;o)
M
05-18-2012 06:36 AM
Swapped out the drive. All good now.