Invalid Drive Type/Density

[Zailar]

Anyone knows why invalid drive type/density usually tape?.

AAAAA:/ # vmoprcmd -crawlreleasebyname IBMULTRIUM-TD34

Host AAAAA returned: Invalid Drive Type/Density

Host BBBBB returned: RELEASED

Host CCCCC returned: RELEASED

Host DDDDD returned: RELEASED

Host EEEEE returned: RELEASED

Host FFFFF returned: RELEASED

Host GGGGG returned: RELEASED

Host HHHHH returned: RELEASED

Host IIIII returned: RELEASED

Host JJJJJ returned: RELEASED

Host LLLLL returned: RELEASED

Host KKKKK returned: RELEASED

Host NNNNN returned: RELEASED

Host OOOOO returned: RELEASED

Host MMMMM returned: RELEASED

AAAAA:/ # tpconfig -l

Device Robot Drive       Robot                    Drive                   

Type     Num Index  Type DrNum Status  Comment    Name                            

robot      4    -    ACS    -       -  -          -                 

  drive    -    0 hcart3    -      UP  -          IBMULTRIUM-TD30

  drive    -    1 hcart3    -      UP  -          IBMULTRIUM-TD31

  drive    -    2 hcart3    -      UP  -          IBMULTRIUM-TD32

  drive    -    3 hcart3    -      UP  -          IBMULTRIUM-TD33

  drive    -    4 hcart3    -    DOWN  -          IBMULTRIUM-TD34

  drive    -    4 hcart3    -    DOWN  -          IBMULTRIUM-TD34

  drive    -    5 hcart3    -      UP  -          IBMULTRIUM-TD35 

  drive    -    6 hcart3    -      UP  -          IBMULTRIUM-TD36

  drive    -    7 hcart3    -      UP  -          IBMULTRIUM-TD37

  drive    -    8 hcart3    -      UP  -          IBMULTRIUM-TD38

Log in bptm

09:36:50.393 [13284] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1313493389 -jm 

09:36:50.405 [13284] <2> drivename_open: Called with Create 0, file IBMULTRIUM-TD34

09:36:50.405 [13284] <2> drivename_checklock: Called

09:36:50.405 [13284] <2> report_drives: MODE = 2

09:36:50.405 [13284] <2> report_drives: TIME = 1315912674

09:36:50.405 [13284] <2> report_drives: MASTER = AAAAA

09:36:50.406 [13284] <2> report_drives: PATH = c640t0l0

09:36:50.406 [13284] <2> report_drives: MEDIA = K02529

09:36:50.406 [13284] <2> report_drives: REQID = -1313483301

09:36:50.406 [13284] <2> report_drives: ALOCID = 318235

09:36:50.406 [13284] <2> report_drives: RBID = {05BF1232-1DD2-11B2-A010-00306E5D8B2B

09:36:50.406 [13284] <2> report_drives: NDMP_HOST = ndmpserver

09:36:50.406 [13284] <2> report_drives: PID = 21379

09:36:50.406 [13284] <2> report_drives: FILE = /usr/openv/netbackup/db/media/tpreq/drive_IBMULTRIUM-TD34

Regards

[Marianne]

'tpconfig -l' usually displays more info that that - it also includes the devices paths on the media server as well as the NAS server, e.g:

  drive    -    6 hcart2   18      UP  -          Drive18_L700          /dev/rmt/27cbn
  drive    -    6 hcart2   18      UP  -          Drive18_L700          c752t0l0

Verify that device access is healthy at OS level.

Wat does 'vmdareq' output on master look like?
And 'vmoprcmd -d' ?

The extract from bptm contains no errors.

Which OS on media server AAAAA? Which NBU version? Which NAS device?

[Zailar]

Marianne,

I was cut the output tpconfig -l

  drive    -    4 hcart3    -    DOWN  -          IBMULTRIUM-TD34   /dev/rmt/c62t6d0BESTnb  ACS=0, LSM=0, PANEL=1, DRIVE=13

  drive    -    4 hcart3    -      UP  -          IBMULTRIUM-TD34   c640t0l0                ACS=0, LSM=0, PANEL=1, DRIVE=13

AAAAA:/ # vmoprcmd -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId

  0 hcart3   ACS                -                     No       -         0  

  1 hcart3   ACS                -                     No       -         0  

  2 hcart3   ACS                -                     No       -         0  

  3 hcart3   ACS                -                     No       -         0  

  4 hcart3 DOWN-ACS             -                     No       -         0  

  4 hcart3   ACS                -                     No       -         0  

  5 hcart3   ACS               Yes   K03508  K03508   Yes     Yes        0  

  6 hcart3   ACS                -                     No       -         0  

  7 hcart3   ACS                -                     No       -         0  

  8 hcart3   ACS                -                     No       -         0  

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment                   

  0 IBMULTRIUM-TD30       Yes      -                                         

  1 IBMULTRIUM-TD31       Yes      -                                         

  2 IBMULTRIUM-TD32       Yes      -                                         

  3 IBMULTRIUM-TD33       Yes      -                                         

  4 IBMULTRIUM-TD34       Yes      -                                         

  4 IBMULTRIUM-TD34       Yes      -                                         

  5 IBMULTRIUM-TD35       Yes      AAAAA.dc.of                           

  6 IBMULTRIUM-TD36       Yes      -                                         

  7 IBMULTRIUM-TD37       Yes      -                                         

  8 IBMULTRIUM-TD38       Yes      -            

Output vmdareq (just only drive problem)

IBMULTRIUM-TD34 - AVAILABLE

     AAAAA SCAN_HOST UP 

     BBBBB DOWN 

     CCCCC DOWN 

     DDDDD DOWN 

     EEEEE DOWN 

     FFFFF UP 

     GGGGG DOWN 

     HHHHH DOWN 

     IIIII UP 

     JJJJJ DOWN 

     LLLLL UP 

     KKKKK DOWN 

     NNNNN DOWN 

     OOOOO DOWN 

     MMMMM UP 

The OS HP-UX B.11.11 NBU Version 6.0 MP7

Yes in btptm no error, the first configuration is ok, but suddenly in vmoprcmd -crawlreleasebyname the output  Invalid Drive Type/Density

I was over tpconfig but no configuration changes 

[Marianne]

I wouldn't spend too much energy on the 'invalid drive type...' message. NBU needs to issue a reset/release at OS level. Because the NDMP drive is configured on the media server, the 'crawlrelease' is probably getting its 'knickers in a knot' when it gets to the NDMP drive.

From your last output, it seems that the problem is on the HP-UX server since the drive is now UP on NDMP but DOWN on the media server. For increased logging as far as device management is concerned, add VERBOSE entry in /usr/openv/volmgr/vm.conf and restart NBU. Device type errors will now be logged to syslog (/var/adm/syslog/syslog.log).

[Zailar]

Thanks Marianne,

Ya I will trace message from OS.

[Marianne]

Any feedback/progress on this?

[Zailar · Accepted solution]

Yesterday I was applied device mapping http://www.symantec.com/business/support/index?page=content&id=TECH170162&cat=PATCHES&key=15143&base...

then restart the netbackup service.  

AAAAA:/ # vmoprcmd -crawlreleasebyname IBMULTRIUM-TD34

Host AAAAA returned: RELEASED

Host BBBBB returned: RELEASED

Host CCCCC returned: RELEASED

Host DDDDD returned: RELEASED

Host EEEEE returned: RELEASED

Host FFFFF returned: RELEASED

Host GGGGG returned: RELEASED

Host HHHHH returned: RELEASED

Host IIIII returned: RELEASED

Host JJJJJ returned: RELEASED

Host LLLLL returned: RELEASED

Host KKKKK returned: RELEASED

Host NNNNN returned: RELEASED

Host OOOOO returned: RELEASED

Host MMMMM returned: RELEASED

Thanks for help

[Marianne]

Since you found the solution yourself, I am happy to mark your post as Solution.