Replaced drive appears as "MISSING_DRIVE" in device monitor

[Flappyhead]

Hello Gaggle of Guru's

We have a Quantum P4000 library with 8 drives installed. We have 6 media servers, 5 being Windows 2K3, and one being Unix. Our Master Server is Windows 2K3 as well. We are running NetBackup 6 MP4 on all servers.

One of our drives died the other day. An engineer came and replaced it. I updated the firmware successfully so it is the same as all other drives. I restarted the drive. I restarted the P4000 library. I even restarted the drive AGAIN. I rebooted all media servers and master server.

The Operating System on all of the servers can see all drives perfectly. The drive comes up as "MISSING_DRIVE" in NetBackups Device Manager.

In Windows Event Viewer (Application) on the Master server, the following error appears....

Source: NetBackup AVR Daemo
Event ID: 2747
Description: "could not get drive path for drive QUANTUM.SDLT600.005 (device 1, SCSI coordinates MISSING_DRIVE:.......)"

Can someone please reveal the obvious solution to this problem?? Thanks :)

-Richard

[Flappyhead]

... oh and BTW, the output for tpconfig -d is...

Id  DriveName           Type   Residence
      SCSI coordinates/Path                                            Status
****************************************************************************
0   QUANTUM.SDLT600.007  dlt    TLD(0)  DRIVE=1
      {3,0,0,1}                                                        UP
      {5,0,3,1}                                                        UP
1   QUANTUM.SDLT600.005  dlt    TLD(0)  DRIVE=5
      MISSING_DRIVE:RB0504AMC05141                                     DOWN
2   QUANTUM.SDLT600.006  dlt    TLD(0)  DRIVE=6
      {3,0,1,1}                                                        UP
      {5,0,2,1}                                                        UP
3   QUANTUM.SDLT600.002  dlt    TLD(0)  DRIVE=2
      {5,0,0,0}                                                        UP
      {3,0,3,0}                                                        UP
4   QUANTUM.SDLT600.003  dlt    TLD(0)  DRIVE=3
      {5,0,0,1}                                                        UP
      {3,0,3,1}                                                        UP
5   QUANTUM.SDLT600.004  dlt    TLD(0)  DRIVE=4
      {5,0,0,2}                                                        UP
      {3,0,3,2}                                                        UP
6   QUANTUM.SDLT600.000  dlt    TLD(0)  DRIVE=7
      {5,0,1,0}                                                        UP
      {3,0,2,0}                                                        UP
7   QUANTUM.SDLT600.001  dlt    TLD(0)  DRIVE=8
      {5,0,1,1}                                                        UP
      {3,0,2,1}                                                        UP
8   QUANTUM.SDLT600.011  dlt    TLD(0)  DRIVE=5
      {3,0,1,0}                                                        UP
      {5,0,2,0}                                                        UP

Currently defined robotics are:
  TLD(0)     SCSI coordinates = {3,0,0,0},

EMM Server = dppbku1

Cheers!! :)


Message Edited by Flappyhead on 01-07-2008 07:08 PM

[Flappyhead]

Issue solved...

The new drive DID exist as a new drive, and the old drive still existed which was the "MISSING_DRIVE" (kinda makes sense, huh?).

I deleted the 2 drives and re-configured storage devices.

[Colin_North]

Good to see that you managed to fix this. All tape drives and robots have a serial number and you can see this by using the command - vmglob -listall -b, so your old drive was still listed. You can also use this command to delete old drives.

When adding new drives to Netbackup you can use the device configuration wizard. There's also lots of other posts on this forum relating to adding / deleting tape drives.

[Flappyhead]

Hi Colin

Yes, I skipped a very obvious step in the whole process. I feel stupid for this. At least maybe this post might help someone else... :-S

-Rich