cancel
Showing results for 
Search instead for 
Did you mean: 

Invalid drive index when delete the tape drive

Home_224
Level 6

i find the problem when drive to remove the drive , it shows that the invalid drive index when delete the drive. 

root@devuarbak01 # tpconfig -l
Device Robot Drive Robot Drive Device Second
Type Num Index Type DrNum Status Comment Name Path Device Path

But I can see the tape information when run the  scan.  

root@devuarbak01 # scan-tape
scan-tape: not found
root@devuarbak01 # scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c0tw2002000e111639dbl0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULT3580-HH6 H991"
Vendor ID : "IBM "
Product ID : "ULT3580-HH6 "
Product Rev: "H991"
Serial Number: "10WT130808"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULT3580-HH6 10WT130808"
Device Type : SDT_TAPE
NetBackup Drive Type: Not Found(5)
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/sg/c0tw2002000e111639dbl1"
Passthru Name: "/dev/sg/c0tw2002000e111639dbl1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM 3573-TL E.60"
Vendor ID : "IBM "
Product ID : "3573-TL "
Product Rev: "E.60"
Serial Number: "00L2U78CF388_LL0"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM 3573-TL 00L2U78CF388_LL0"
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-5
Number of Drives : 2
Number of Slots : 24
Number of Media Access Ports: 0
Drive 1 Serial Number : "10WT130808"
Drive 2 Serial Number : "10WT127994"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/rmt/1cbn"
Passthru Name: "/dev/sg/c0tw2005000e111639dbl0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULT3580-HH6 H991"
Vendor ID : "IBM "
Product ID : "ULT3580-HH6 "
Product Rev: "H991"
Serial Number: "10WT127994"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULT3580-HH6 10WT127994"
Device Type : SDT_TAPE
NetBackup Drive Type: Not Found(5)
Removable : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0

I try to run robot inventory, it cannot connect to robotic software daemon

41 REPLIES 41

mph999
Level 6
Employee Accredited

In the output you show,  I see the heading - but no config ...

Your output:

root@devuarbak01 # tpconfig -l
Device Robot Drive Robot Drive Device Second
Type Num Index Type DrNum Status Comment Name Path Device Path

Example output from myserver

root@gpk630r2f-18 mph $ tpconfig -l
Device Robot Drive Robot Drive Device Second
Type Num Index Type DrNum Status Comment Name Path Device Path
robot 0 - TLD - - - - /dev/sg7
drive - 0 hcart3 1 UP - IBM.ULTRIUM-HH6.000 /dev/tape/by-path/pci-0000:04:00
drive - 1 hcart3 2 UP - IBM.ULTRIUM-HH6.001 /dev/tape/by-path/pci-0000:04:00

So, unless you accidently missed copy/ paste the config, I do not see any drives configured.

Presuming you didn;t copy/ paste all the details, and you have some issue with eth drive index and cannot delete a drive, the only way to resolve this is to delete everything, and reconfigure.

You can specify a media server, or just delete all devices from all servers

nbemmcmd -deletealldevices -allrecords  (everything)

or

nbemmcmd -deletealldevices -machinename <media server name> -machinetype media  (specific server)

... then , reconfigure.

The scan output is useless here, it has no relation to index values of the drives.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Home_224 

tpconfig shows NetBackup configuration. 
Your output shows nothing. In other words, nothing is configured in NBU.

scan shows what the OS sees. 
When scan shows devices correctly (robot and tape drives), you can run Device Config wizard to add the devices to NBU config. 

But.... before you do that - all is not well with scan output:

NetBackup Drive Type: Not Found(5)

You need to download and install NBU Device Mappings that supports this drive type.
Links to Device Mappings download in NBU HCL. 

Thank you for all of your.

I try to use the commnd delete command but not work on my old version of NBU, so I try to do that and no idea how to find the string. 

My current version is 6.0 MP4 

Usage:
nbemmcmd -deletemedia -mediaid <string> -originhost <string>
Command did not complete successfully.
root@devuarbak01 # nbemmcmd -deletemedia devuarbak01
NBEMMCMD, Version:6.0MP4(20060530)
There is no value associated with the command option
Usage:
nbemmcmd -deletemedia -mediaid <string> -originhost <string>

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Home_224 

Did you read through our previous posts?

Why are you trying to run a command to delete media (tapes)? 
nbemmcmd -deletemedia

I think you won't be able to use 'nbemmcmd -deletealldevices' as this option was added in a newer NBU version. 

But, once again - your tpconfig command shows that you DON'T have any devices configured in NBU.
Please read my previous post again?

Yes, I try to delete the tape drive and robot, it returns message the device not to existing, but I have no idea why I can see the device on the ADM console.  I try to delete the tape drive it shows the invaild index.  

In this situation, can you please advice how to delete the drive and re-scan the device to configure it again? 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Try to restart NBU. 
Close the GUI, stop NBU. Wait for all processes to stop (monitor with bpps)
Start NBU.

If devices have been deleted before without restarting NBU Device Management (ltid), then the devices remain in the database.

If the devices still show up in the GUI, please share a screenshot. 

 

drive.PNGRobot.PNG

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Thanks for the screenshots.

Have you restarted NBU on this server yet?

 

Yes, I restart NBU and GUI, the configuration still keep in the database 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Something seems to be wrong - tpconfig should show the same devices that you see in the GUI. 

You will need the Commands Manual for your NBU version to see what options is available with nbemmcmd to delete devices.
It does not help if we give you options that is not available with your NBU version. 

Maybe @mph999 has more ideas? 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I found this TN that MIGHT help : https://www.veritas.com/support/en_US/article.100019354

Just ignore 'mediaserver no longer exists'. 

I think that this refers to NBU 6.0 :
"  Upgrade to MP7 (Starting in MP7 a script was created to delete all of the devices) 

So, if you can upgrade to MP7 then the 'deletealldevices' option will be available. 

The other option will be to use the vmglob command to delete the devices. 
You will need to run 'vmglob -listall' to ge a list of devices in the global device database
or
tpconfig -emm_dev_list  

I also found this post that looks like the same issue:
https://vox.veritas.com/t5/NetBackup/Cannot-delete-erroneous-missing-drive-path/td-p/354779

There was a reference to a TN that no longer exists: 
GENERAL ERROR: "Invalid drive index (14)" observed when attempting to delete a drive via the GUI.
http://www.symantec.com/business/support/index?page=content&id=TECH55575

I am hoping that @mph999 could possibly locate the contents? 

The article you are asking about is now marked restricted internal only - I have no idea why. The article number is now article.100029870 (not that this helps).

I think you are right on the mark using the "tpconfig -emm_dev_list" to determine what devices are configured.
Then use the 'tpconfig -delete ..." with appropriate options on the media server that EMM indicates owns the devices.

A "tpconfig" on the media server (devuarbak01) would also go a long way to solving your problem.

==============================================================================
Robot: ROBOT0
Robot Number: 0
Robot Type: TLD(8)
Media Server: devuarbak01
Port: -1
Bus: -1
Target: -1
Lun: -1
PartiallyConfigured: 0
Pird: 0
Host: -
Apath: /dev/sg/c0tw2002000e111639dbl1
NDMP Attach Host: -
VMhost: devuarbak01
DAhost: devuarbak01
SN: 00L2U78CF388_LL0
Inquiry: IBM 3573-TL E.60
WorldWideId: -
Old DAhost: devuarbak01
RSM GUID: 00000000-0000-0000-0000-000000000000
==============================================================================
==============================================================================
Drive: IBM.ULT3580-HH6.000
Index: 0
Drive Type: hcart3(16)
Media Server: devuarbak01
Occupy Index: 0
Opr Count: 0
Status: 4
Saved Mode Bits: 0
Access Mode: 0
Robot Type: NONE(0)
Robot Number: -1
Loc1: -1
Loc2: -1
Loc3: -1
Loc4: -1
Loc5: 0
Port: -1
Bus: -1
Target: -1
Lun: -1
VH Saved Mode Bits: 0
Flags: 1073741824
Time Mounted: 0
Total Time Mounted: 168
Cleaning Frequency: 0
Last Time Cleaned: 0
Vendor Device Num: 0
Tape Alert 1: 0
Tape Alert 2: 0
Last DA Call Time: 0
Application Type: 0
Drive Path: MISSING_DRIVE:10WT130808
Volume Header Drive Path: -
Vendor Drive Name: -
Current RVSN: -
Current EVSN: -
Current User: -
Operator Comment: -
SN: 10WT127936
Inquiry Info: IBM ULT3580-HH6 H991
World Wide Id: -
NDMP Host: -
Scan Host: -
Assign Host: -
RSM GUID: 00000000-0000-0000-0000-000000000000
APPL_GUID: 00000000-0000-0000-0000-000000000000
==============================================================================
==============================================================================
Drive: IBM.ULT3580-HH6.001
Index: 1
Drive Type: hcart3(16)
Media Server: devuarbak01
Occupy Index: 0
Opr Count: 0
Status: 4
Saved Mode Bits: 0
Access Mode: 0
Robot Type: NONE(0)
Robot Number: -1
Loc1: -1
Loc2: -1
Loc3: -1
Loc4: -1
Loc5: 0
Port: -1
Bus: -1
Target: -1
Lun: -1
VH Saved Mode Bits: 0
Flags: 1073741824
Time Mounted: 0
Total Time Mounted: 115
Cleaning Frequency: 0
Last Time Cleaned: 0
Vendor Device Num: 0
Tape Alert 1: 0
Tape Alert 2: 0
Last DA Call Time: 0
Application Type: 0
Drive Path: MISSING_DRIVE:10WT127994
Volume Header Drive Path: -
Vendor Drive Name: -
Current RVSN: -
Current EVSN: -
Current User: -
Operator Comment: -
SN: 10WT127938
Inquiry Info: IBM ULT3580-HH6 H991
World Wide Id: -
NDMP Host: -
Scan Host: -
Assign Host: -
RSM GUID: 00000000-0000-0000-0000-000000000000
APPL_GUID: 00000000-0000-0000-0000-000000000000
==============================================================================
==============================================================================
Drive: IBM.ULT3580-HH6.002
Index: 2
Drive Type: pcd(5)
Media Server: devuarbak01
Occupy Index: 0
Opr Count: 0
Status: 4
Saved Mode Bits: 0
Access Mode: 0
Robot Type: TLD(8)
Robot Number: 0
Loc1: 1
Loc2: -1
Loc3: -1
Loc4: -1
Loc5: 0
Port: -1
Bus: -1
Target: -1
Lun: -1
VH Saved Mode Bits: 0
Flags: 1073741824
Time Mounted: 0
Total Time Mounted: 0
Cleaning Frequency: 0
Last Time Cleaned: 0
Vendor Device Num: 0
Tape Alert 1: 0
Tape Alert 2: 0
Last DA Call Time: 0
Application Type: 0
Drive Path: /dev/rmt/0cbn
Volume Header Drive Path: -
Vendor Drive Name: -
Current RVSN: -
Current EVSN: -
Current User: -
Operator Comment: -
SN: 10WT130808
Inquiry Info: IBM ULT3580-HH6 H991
World Wide Id: -
NDMP Host: -
Scan Host: -
Assign Host: -
RSM GUID: 00000000-0000-0000-0000-000000000000
APPL_GUID: 00000000-0000-0000-0000-000000000000
==============================================================================
==============================================================================
Drive: IBM.ULT3580-HH6.003
Index: 3
Drive Type: pcd(5)
Media Server: devuarbak01
Occupy Index: 0
Opr Count: 0
Status: 4
Saved Mode Bits: 0
Access Mode: 0
Robot Type: TLD(8)
Robot Number: 0
Loc1: 2
Loc2: -1
Loc3: -1
Loc4: -1
Loc5: 0
Port: -1
Bus: -1
Target: -1
Lun: -1
VH Saved Mode Bits: 0
Flags: 1073741824
Time Mounted: 0
Total Time Mounted: 0
Cleaning Frequency: 0
Last Time Cleaned: 0
Vendor Device Num: 0
Tape Alert 1: 0
Tape Alert 2: 0
Last DA Call Time: 0
Application Type: 0
Drive Path: /dev/rmt/1cbn
Volume Header Drive Path: -
Vendor Drive Name: -
Current RVSN: -
Current EVSN: -
Current User: -
Operator Comment: -
SN: 10WT127994
Inquiry Info: IBM ULT3580-HH6 H991
World Wide Id: -
NDMP Host: -
Scan Host: -
Assign Host: -
RSM GUID: 00000000-0000-0000-0000-000000000000
APPL_GUID: 00000000-0000-0000-0000-000000000000
==============================================================================
==============================================================================
Master Server: devuarbak01
NetBackup Version: 6.0(600000)
Host OperatingSystem: 2
MachineState: ACTIVE-DI
==============================================================================
Media Server: imduarbak01
NetBackup Version: 6.0(600000)
Host OperatingSystem: 2
MachineState: OFFLINE
==============================================================================
EMM Server: devuarbak01

May I know which device configured from the output

mph999
Level 6
Employee Accredited

OK, I would just delete all devices - the command to do this:

nbemmcmd -deletealldevices -allrecords

This will delete all robots and drives ...  I have never known this command to fail

tpconfig -d or tpconfig -emm_dev_list should then show no devices.

If there is any doubt after this, I would get nbdb_unload <some dir> and look directly in the database tables the relate to devices.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@mph999 

I think the -deletealldevices switch was added in a version later than @Home_224 's 6.0 MP4 version... 

Hi ,

I use with your command that is no work on the current 6.0 version. 

mph999
Level 6
Employee Accredited

NetBackup 6.0 - seriously - that is what, 11 odd years old now.

Can you upgrade ?

Without the -deletealldevices command there is not really anyway to delete everything, if there is some doubt as to if things are left behind in the database (once you have used normal methods to delete devices).

It can be done via 'manual' sql commands directly on NBDB, but that is not an activity for a forum.

Due to our project is support to Government, the system is running over 10 yrs , upgrade the NBU to latest one , the client not support the lastest version as it running the solaris 9 and window 2003 SP2 . Impossible to do upgrade the current system .