Forum Discussion

Andy2345's avatar
Andy2345
Level 6
12 years ago

tpautoconf

  tpautoconf -report_disc     ======================= Missing Device (Drive) ======================  Inquiry = "IBM  Ultrium 3-SCSI   Serial Number =  HM74536FFS  Drive Path = /dev/rmt/0c...
7.1.x and Earlier
Backup and Recovery
NetBackup
  • mph999's avatar
    mph999
    12 years ago

    "why /dev/rmt/119cbn with QUANTUMDLT800014?"

    The drive in tld(6) at drive position 1 now has a different path, therefore the drive that did have path /dev/rmt/9cbn is not found by the operating system

    If you run mt -f /dev/rmt/9cbn you will get a message saying 'no such device' or similar.

    You say this :

     

    "Drive path should be /dev/rmt/9cbn ?

    Because drive QUANTUMDLT800014 has above path."

    Maybe it should be 9cbn, but can't you see that the output of the command is telling you that the device at this path is missing ?

    Look again

     

    tpautoconf -report_disc
    ======================= New Device (Tape) =======================
     Inquiry = "QUANTUM DLT8000         0250"
     Serial Number = PXB08P3242
     Drive Path = /dev/rmt/119cbn
     Found as TLD(6), Drive = 1
    ===================== Missing Device (Drive) =====================
     Drive Name = QUANTUMDLT800014
     Drive Path = /dev/rmt/9cbn
     Inquiry = "QUANTUM DLT8000         0250"
     Serial Number = PXB08P1345
     TLD(6) definition Drive = 1
     Hosts configured for this device:
      Host = plum
      Host = avocado
      
      
      Both drives show TLD(6) Drive - 1
      
      There can only physically be one drive at this position, and the serial number of the missing drive is different than the serial number of the new drive, therefore the drive must have been physically changed.
      
      When this was done the path changed.
      
      The fact that path is different doesn't really matter, once reconfigured it will work fine.
      
      So the final answer is that the drive has been swapped, some times the path changes when this happens, sometimes it doesn't - it is impossible for me to say exactly why it changed in this case , I wasn't there when it was done.  I wouldn't worry about the path - it doesn't matter what it is.
      
      

     

mph999's avatar
mph999
Level 6
12 years ago

"why /dev/rmt/119cbn with QUANTUMDLT800014?"

The drive in tld(6) at drive position 1 now has a different path, therefore the drive that did have path /dev/rmt/9cbn is not found by the operating system

If you run mt -f /dev/rmt/9cbn you will get a message saying 'no such device' or similar.

You say this :

 

"Drive path should be /dev/rmt/9cbn ?

Because drive QUANTUMDLT800014 has above path."

Maybe it should be 9cbn, but can't you see that the output of the command is telling you that the device at this path is missing ?

Look again

 

tpautoconf -report_disc
======================= New Device (Tape) =======================
 Inquiry = "QUANTUM DLT8000         0250"
 Serial Number = PXB08P3242
 Drive Path = /dev/rmt/119cbn
 Found as TLD(6), Drive = 1
===================== Missing Device (Drive) =====================
 Drive Name = QUANTUMDLT800014
 Drive Path = /dev/rmt/9cbn
 Inquiry = "QUANTUM DLT8000         0250"
 Serial Number = PXB08P1345
 TLD(6) definition Drive = 1
 Hosts configured for this device:
  Host = plum
  Host = avocado
  
  
  Both drives show TLD(6) Drive - 1
  
  There can only physically be one drive at this position, and the serial number of the missing drive is different than the serial number of the new drive, therefore the drive must have been physically changed.
  
  When this was done the path changed.
  
  The fact that path is different doesn't really matter, once reconfigured it will work fine.
  
  So the final answer is that the drive has been swapped, some times the path changes when this happens, sometimes it doesn't - it is impossible for me to say exactly why it changed in this case , I wasn't there when it was done.  I wouldn't worry about the path - it doesn't matter what it is.