cancel
Showing results for 
Search instead for 
Did you mean: 

drive is going down on mounting tape

symsonu
Level 6

 

whenever we attempt a backup , drive goes down during mounting of tape.. we tried many tapes.

 

Below are the logs in message file :-->

 

 

Jan 18 13:34:28 ombs bpjava-msvc[28024]: [ID 427199 user.error] pam_dial_auth: terminal-device not specifiedby login, returning Error in underlying service module.
Jan 18 13:35:12 ombs ltid[11955]: [ID 274169 daemon.notice] Operator/EMM server has UP'ed drive HP.ULTRIUM4-SCSI.000 (device 0)
Jan 18 13:36:14 ombs tldcd[12071]: [ID 318210 daemon.notice] inquiry() function processing library HP       MSL G3 Series    C.30:
Jan 18 13:36:14 ombs tldcd[28632]: [ID 925075 daemon.notice] TLD(0) opening robotic path /dev/sg/c0t4l1
Jan 18 13:36:14 ombs tldcd[28632]: [ID 318210 daemon.notice] inquiry() function processing library HP       MSL G3 Series    C.30:
Jan 18 13:36:14 ombs tldcd[28632]: [ID 559680 daemon.notice] TLD(0) closing/unlocking robotic path
Jan 18 13:36:14 ombs tldcd[12071]: [ID 318210 daemon.notice] inquiry() function processing library HP       MSL G3 Series    C.30:
Jan 18 13:36:53 ombs ltid[11955]: [ID 527589 daemon.notice] LTID - Sent ROBOTIC request, Type=1, Param2=0
Jan 18 13:36:53 ombs tldd[12021]: [ID 145055 daemon.notice] TLD(0) MountTape T106L3 on drive 1, from slot 7
Jan 18 13:36:53 ombs tldcd[12071]: [ID 318210 daemon.notice] inquiry() function processing library HP       MSL G3 Series    C.30:
Jan 18 13:36:53 ombs tldcd[12071]: [ID 817356 daemon.notice] Processing MOUNT, TLD(0) drive 1, slot 7, barcode BHT106L3        , vsn T106L3
Jan 18 13:36:53 ombs tldcd[28795]: [ID 925075 daemon.notice] TLD(0) opening robotic path /dev/sg/c0t4l1
Jan 18 13:36:53 ombs tldcd[28795]: [ID 318210 daemon.notice] inquiry() function processing library HP       MSL G3 Series    C.30:
Jan 18 13:36:53 ombs tldcd[28795]: [ID 559376 daemon.notice] TLD(0) initiating MOVE_MEDIUM from addr 1007 to addr 1
Jan 18 13:42:43 ombs tldcd[28795]: [ID 131361 daemon.error] TLD(0) key = 0x3, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED
Jan 18 13:42:43 ombs tldcd[28795]: [ID 719803 daemon.error] TLD(0) Move_medium error
Jan 18 13:42:43 ombs tldcd[28795]: [ID 559680 daemon.notice] TLD(0) closing/unlocking robotic path
Jan 18 13:42:43 ombs tldcd[12071]: [ID 318210 daemon.notice] inquiry() function processing library HP       MSL G3 Series    C.30:
Jan 18 13:42:43 ombs tldd[12021]: [ID 400727 daemon.notice] DecodeMount: TLD(0) drive 1, Actual status: Robotic mount failure
Jan 18 13:42:44 ombs ltid[11955]: [ID 412853 daemon.notice] LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=0
Jan 18 13:42:45 ombs ltid[11955]: [ID 560357 daemon.notice] LTID - Sent ROBOTIC request, Type=3, Param2=0
Jan 18 13:42:45 ombs tldd[12021]: [ID 404684 daemon.notice] TLD(0) DismountTape ****** from drive 1
Jan 18 13:43:00 ombs tldcd[12071]: [ID 318210 daemon.notice] inquiry() function processing library HP       MSL G3 Series    C.30:
Jan 18 13:43:00 ombs tldcd[12071]: [ID 169665 daemon.notice] Processing UNMOUNT, TLD(0) drive 1, slot -1, barcode  <NONE> , vsn ******
Jan 18 13:43:00 ombs tldcd[29431]: [ID 925075 daemon.notice] TLD(0) opening robotic path /dev/sg/c0t4l1
Jan 18 13:43:00 ombs tldcd[29431]: [ID 318210 daemon.notice] inquiry() function processing library HP       MSL G3 Series    C.30:
Jan 18 13:43:00 ombs tldcd[29431]: [ID 559680 daemon.notice] TLD(0) closing/unlocking robotic path
Jan 18 13:43:00 ombs tldcd[12071]: [ID 318210 daemon.notice] inquiry() function processing library HP       MSL G3 Series    C.30:
Jan 18 13:43:00 ombs tldd[12021]: [ID 858878 daemon.notice] DecodeDismount: TLD(0) drive 1, Actual status: STATUS_SUCCESS
Jan 18 13:43:03 ombs ltid[11955]: [ID 434987 daemon.error] Operator/EMM server has DOWN'ed drive HP.ULTRIUM4-SCSI.000 (device 0)

 

 

After making drive up , I ran robtest as below

 

 

# robtest
Configured robots with local control supporting test utilities:
  TLD(0)     robotic path = /dev/sg/c0t4l1

Robot Selection
---------------
  1)  TLD 0
  2)  none/quit
Enter choice: 1

Robot selected: TLD(0)   robotic path = /dev/sg/c0t4l1

Invoking robotic test utility:
/usr/openv/volmgr/bin/tldtest -rn 0 -r /dev/sg/c0t4l1

Opening /dev/sg/c0t4l1
MODE_SENSE complete
Enter tld commands (? returns help information)
s d
drive 1 (addr 1) access = 1 Contains Cartridge = no
SCSI ID from drive 1 is 4


READ_ELEMENT_STATUS complete
s s
slot 1 (addr 1001) contains Cartridge = no
slot 2 (addr 1002) contains Cartridge = yes

Source address = 1002
Barcode = BHT101L3
slot 3 (addr 1003) contains Cartridge = yes
Source address = 1003
Barcode = BHT102L3
slot 4 (addr 1004) contains Cartridge = yes
Source address = 1004
Barcode = BHT103L3
slot 5 (addr 1005) contains Cartridge = yes
Source address = 1005
Barcode = BHT104L3
slot 6 (addr 1006) contains Cartridge = yes
Source address = 1006
Barcode = BHT105L3
slot 7 (addr 1007) contains Cartridge = yes
Source address = 1007
Barcode = BHT106L3
slot 8 (addr 1008) contains Cartridge = yes
Source address = 1008
Barcode = BHT107L3
<< Press return to continue, or q and return to stop >>

slot 9 (addr 1009) contains Cartridge = yes
Source address = 1009
Barcode = BHT108L3
slot 10 (addr 1010) contains Cartridge = yes
Source address = 1010
Barcode = BHT109L3
slot 11 (addr 1011) contains Cartridge = yes
Source address = 1011
Barcode = BHT110L3
slot 12 (addr 1012) contains Cartridge = yes
Source address = 1012
Barcode = BHT111L3
slot 13 (addr 1013) contains Cartridge = yes
Source address = 1013
Barcode = BHT112L3
slot 14 (addr 1014) contains Cartridge = yes
Source address = 1014
Barcode = BHT113L3
slot 15 (addr 1015) contains Cartridge = yes
Source address = 1015
Barcode = BHT114L3
<< Press return to continue, or q and return to stop >>

slot 16 (addr 1016) contains Cartridge = yes
Source address = 1016
Barcode = BHT115L3
slot 17 (addr 1017) contains Cartridge = yes
Source address = 1017
Barcode = BHT116L3
slot 18 (addr 1018) contains Cartridge = yes
Source address = 1018
Barcode = BHT117L3
slot 19 (addr 1019) contains Cartridge = yes
Source address = 1019
Barcode = BHT118L3
slot 20 (addr 1020) contains Cartridge = yes
Source address = 1020
Barcode = BHT119L3
slot 21 (addr 1021) contains Cartridge = yes
Source address = 1021
Barcode = BHT120L3
slot 22 (addr 1022) contains Cartridge = no
slot 23 (addr 1023) contains Cartridge = no
slot 24 (addr 1024) contains Cartridge = no
READ_ELEMENT_STATUS complete
m s21 d
Initiating MOVE_MEDIUM from address 1021 to 1
move_medium failed
sense key = 0x3, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED

Invalid command

 

# tpconfig -l
Device Robot Drive       Robot                    Drive                 Device         Second
Type     Num Index  Type DrNum Status  Comment    Name                  Path           Device Path
robot      0    -    TLD    -       -  -          -                     /dev/sg/c0t4l1
  drive    -    0  hcart    1      UP  -          HP.ULTRIUM4-SCSI.000  /dev/rmt/0cbn
#

 

 

Please suggest what could be the mismatch , i donot have h/w support for TL

 

 

Regards

S.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Have a look at Nicolai's post over here in reply to similar issue: https://www.veritas.com/community/forums/storagetek-sl500#comment-10821971 

The issue in the end was caused by 'home made' labels.

View solution in original post

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

INCOMPATIBLE MEDIUM INSTALLED

This is a robot error - not NBU.

The robot believes that this media type or media label is not compatibile with the drive type.

Nothing that we can do from NBU to fix this.

Have you printed your own labels or purchased from a media vendor?

You need to find out from the vendor (or their web site) which labels are compatibile with the drive type.

SujayDesai
Level 3
Employee

Marianne is correct.

You will need to check with your Hardware vendor for above issue because it clearly states that its "INCOMPATIBLE MEDIUM INSTALLED"

As per barcode its seems that media could be hcart3 and drive is hcart.

So hcart drive is not compatible with hcart3 tapes.

This is robot error not NBU related.

You will need to have compatible tapes so that they could be able to load and unload without any issues.

 

mph999
Level 6
Employee Accredited

For hcart etc, it's confusing.

 

What type of drives do you have , LTO3? LTO4, LTO5 etc ... ???  It seems to be LTO4  ( HP.ULTRIUM4-SCSI.000 )

What types of tapes do you have LTO3? LTO4 ? LTO5 etc.. ???

What colour are these tapes, although not a standard, the tape cartridge colour can give an indication as to what type of tapes they are.

 

The barcode suggests they are LTO3 

slot 21 (addr 1021) contains Cartridge = yes
Source address = 1021
Barcode = BHT120L3

LTO3 tapes are complatible with LTO4 drives, so they 'should' work - but are they really LTO3 ????  (Hence why I ask what colour they are)

Did this ever work, or is this a new setup, Have these tapes come across from another environment ?

Either way, this is not a NetBackup issue, the hardware is complaining that the media is incompatible with the drives, nothing in NBU can fix this, you would get the same issue if you tring to load the media in to the drive by hand, it would eject it immediately.  However, if you accurately answer the above, we might be able to tell you why.

 

 

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Have a look at Nicolai's post over here in reply to similar issue: https://www.veritas.com/community/forums/storagetek-sl500#comment-10821971 

The issue in the end was caused by 'home made' labels.

Nicolai
Moderator
Moderator
Partner    VIP   

Same recommendation again I guess - please provide a photo of the tapes bar code.