What libraries & drives?

Tandberg Superloader with a Quantum SDLT drive in it. The other libraries are two Dell Autoloaders with DLT drives and a Quantum Superloader 3 with a SDLT2 drive in it.

Backupexec has worked fine with it  for the last 3 years, the Quantum library for the last year and the Dell libraries for at least 8 years.

I'm convinced this is NOT hardware related - as I said, SP3 crashed on install, then supposedly installed fine, but has left us with this phantom drive on an impossible SCSI ID.

Stephen Miller wrote:

As soon as the we restart the backupexec services, the drive moves back to being standalone and Missing 1 re-appears.

 

I've gone through disabling and deleting both the real drive and the phantom one (and the loader), removing the drivers and then letting it all re-install, but still we have this phantom drive.

I don't understand why the steps you have tried haven't resolved this.  Lets make sure we agree on what is being done.  Please disable and delete the Tandberg SuperLoader robot, the "stand-alone" appearing SDLT drive, and the "missing" drive.  At this point, everything that is visible in the BE GUI works fine, right?  Now stop and restart the BE services. Does the Tandberg SupLoader and the the SDLT drive appear together? If not, can you post your adamm.log here?

I've carried out those steps over and over - you remove the robot, the drive and the phantom missing drive and restart the services, and all three come back, the missing drive a child of the robot.

I've since uninstalled completely (taking a copy of the Data and Catalogs folders) and reinstalled a plain vanilla copy of v12. This can't see ANY robots or drives - the adamm.log shows nothing discovered at all. I then installed SP2, and it could suddenly see all 4 robots and all 4 drives. The Tandberg superloader works fine.\nHowever, the Quantum Superloader 3 does not - it reports as having 0 slots and 0 drives - the drive is listed as Standalone. Deleting the drive and loader and restarting the services doesn't help - it still detects as having no slots or drive.

So, we took the SCSI apart and took the Superloader 3 off the system completely.\n \nNow the Tandberg Superloader appears no problem, will run cleaning jobs, but then fails to inventory with "element not found". Aaaaarggh.

The adamm.log does show the medium changer discovered twice (see below), which makes me think the SCSI card is the cause. I'm looking for a replacement right now, but would appreciate any comments on the (partial) log file:


[2584] 02/10/09 16:00:13.717 Read Device Inquiries - start

[2584] 02/10/09 16:00:14.413 Device: \\.\MediumChanger0
[2584] 02/10/09 16:00:14.753 Device: \\.\Tape1
[2584] 02/10/09 16:00:15.563 Device: \\.\MediumChanger1
[2584] 02/10/09 16:00:15.847 Device: \\.\Tape2
[2584] 02/10/09 16:00:15.889 Device: \\.\Tape0
[2584] 02/10/09 16:00:16.230 ReadDeviceScsiInquiryInfo for "\\.\MediumChanger2" - failed - ERROR = 0x00000006 (ERROR_INVALID_HANDLE)

[2584] 02/10/09 16:00:16.230 Device: \\.\Bkup2Dsk
[2584] 02/10/09 16:00:17.395 Device: \\.\MediumChanger2

[2584] 02/10/09 16:00:22.195 Read Device Inquiries - end

[2584] 02/10/09 16:00:22.195 Serialize Devices:

[2584] 02/10/09 16:00:23.728 Device Discovery:

Scsi Address
Prt :Bus :Tar :Lun Attributes
------------------- -------------------------------------------------------------------------------

0001:0000:0002:0000 Device Name "\\.\MediumChanger0"
Secondary Name "\\.\Changer0"
Primary Inquiry "DELL PV-120T-DLTAL D116"
Secondary Inquiry "ADIC FastStor DLT D116"
Serial Number "DELL PV-120T-DLTAL ADIC313401212040"
Device Flags KSCSI, SN(TYPE 0), SN(ELEMENT)
Device State 3, Online

Device IDs 1009, {15E36E2E-2B58-47B1-8BC8-B2F07EE4B28B}
Device Name "Powervault 120T 1"
Device Type 2131755008, "CHANGER FS=1"
Device Features 0x00037867: EMBI,EMBM,IBE,MDTD,MSTS,PT,PMA,RMP,RRD,SMCAE,SMCE
1st Slot Number 1
Number Of Slots 7
Portal Slots 0
Import/Export Manual

Drive Element 0 1010, "PXB02S0459"

0001:0000:0003:0000 Device Name "\\.\Tape1"
Secondary Name "\\?\scsi#sequential&ven_quantum&prod_dlt7000&rev_2561#5&2fdd57bd&0&030#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}"
Primary Inquiry "QUANTUM DLT7000 2561"
Serial Number "QUANTUM DLT7000 PXB02S0459"
Device Flags KSCSI, SN(TYPE 0)
Device State 3, Online

Device IDs 1010, {29F192D0-8BD5-4BCD-B840-C7F43743F108}
Device Name "Restore 1"
Device Type 67141633, "DLT 32K (32K,10,0,HU)"
Device Features 0x000BFA7F: PB,SFB,SRB,WFM,SFF,SRM,PEOD,EL,LU,E,SBS,DC,SDC,TA,HU,RR
Device Element 1009, 0
Device Block Limits [512, 65536]

------------------- -------------------------------------------------------------------------------

0002:0000:0004:0000 Device Name "\\.\MediumChanger1"
Secondary Name "\\.\Changer1"
Primary Inquiry "DELL PV-120T-DLTAL D116"
Secondary Inquiry "ADIC FastStor DLT D116"
Serial Number "DELL PV-120T-DLTAL ADIC313400BL2061"
Device Flags KSCSI, SN(TYPE 0), SN(ELEMENT)
Device State 3, Online

Device IDs 1011, {305B135C-2332-4EEB-BECD-A387032EB6D7}
Device Name "Powervault 120T 2"
Device Type 2131755008, "CHANGER FS=1"
Device Features 0x00037867: EMBI,EMBM,IBE,MDTD,MSTS,PT,PMA,RMP,RRD,SMCAE,SMCE
1st Slot Number 1
Number Of Slots 7
Portal Slots 0
Import/Export Manual

Drive Element 0 1012, "PXB15S0721"

0002:0000:0005:0000 Device Name "\\.\Tape2"
Secondary Name "\\?\scsi#sequential&ven_quantum&prod_dlt7000&rev_2561#5&270cbc46&0&050#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}"
Primary Inquiry "QUANTUM DLT7000 2561"
Serial Number "QUANTUM DLT7000 PXB15S0721"
Device Flags KSCSI, SN(TYPE 0)
Device State 3, Online

Device IDs 1012, {4CDA8EA2-5800-4DBD-B5C7-D057C03EF1D4}
Device Name "Restore 2"
Device Type 67141633, "DLT 32K (32K,10,0,HU)"
Device Features 0x000BEA7F: PB,SFB,SRB,WFM,SFF,SRM,PEOD,EL,LU,SBS,DC,SDC,TA,HU,RR
Device Element 1011, 0
Device Block Limits [512, 65536]

------------------- -------------------------------------------------------------------------------

0004:0000:0003:0000 Device Name "\\.\Tape0"
Secondary Name "\\?\scsi#sequential&ven_tandberg&prod_superdlt1&rev_3737#6&29ce90a7&0&030#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}"
Primary Inquiry "TANDBERGSuperDLT1 3737"
Serial Number "TANDBERGSuperDLT1 PMC42H0098"
Device Flags KSCSI, SN(TYPE 1)
Device State 3, Online

Device IDs 1026, {CF57F627-18E3-4C3B-955C-0CC53DE85673}
Device Name "TANDBERG 1"
Device Type 67174401, "DLT 64K (64K,10,0,HU)"
Device Features 0x000BEA7F: PB,SFB,SRB,WFM,SFF,SRM,PEOD,EL,LU,SBS,DC,SDC,TA,HU,RR
Device Element 0, 0
Device Block Limits [512, 65536]

0004:0000:0003:0001 Device Name "\\.\MediumChanger2"
Primary Inquiry "QUANTUM UHDL 0028"
Serial Number "QUANTUM UHDL RB0250AAB00001"
Device Flags USCSI, SN(TYPE 0)
Device State 3, Online

Device IDs 1027, {B7F939D6-0491-459A-9A51-A854D2C9EE0F}
Device Name "QUANTUM 1"
Device Type 2131755008, "CHANGER FS=1"
Device Features 0x00026000: RMP,RRD,SMCE
1st Slot Number 1
Number Of Slots 16
Portal Slots 0
Import/Export Manual


------------------- -------------------------------------------------------------------------------

9999:0016:0001:0001 Device Name ""
Primary Inquiry "VERITAS Backup To Disk 1.00"
Serial Number "VERITAS Backup To Disk {4FB8A06F-B1F9-4CB5-A693-38C027A3DD61}"
Device Flags SN(TYPE 0), B2D
Device State 3, Online

Device IDs 1005, {4FB8A06F-B1F9-4CB5-A693-38C027A3DD61}
Device Name "BackupExec Program Files"
Folder Path "X:\BEBackup"

------------------- -------------------------------------------------------------------------------

0004:0000:0003:0001 Device Name "\\.\MediumChanger2"
Primary Inquiry "QUANTUM UHDL 0028"
Serial Number "QUANTUM UHDL RB0250AAB00001"
Device Flags USCSI, SN(TYPE 0)
Device State 3, Online

Device IDs 1027, {B7F939D6-0491-459A-9A51-A854D2C9EE0F}
Device Name "QUANTUM 1"
Device Type 2131755008, "CHANGER FS=1"
Device Features 0x00026000: RMP,RRD,SMCE
1st Slot Number 1
Number Of Slots 16
Portal Slots 0
Import/Export Manual


------------------- -------------------------------------------------------------------------------

[2584] 02/10/09 16:00:24.197 Start Rsm Support:

[2584] 02/10/09 16:00:25.219 Device Discovery End:

hi,
 

i am facing the same issue with a quantum robotic library , may i know which is the registry key and what are the steps taken to troubleshoot the issue?

my drive also show missing 1