Forum Discussion

BackupMonkey50's avatar
5 years ago

Backup exex is unable to communicate with LTO autoloader.

Since my last post was marked as spam and any queries to get it unmarked as such are ignored I'll repost it.

Hi all.

Server 2019 OS (Updated)
HP P212 HBA (None Raid) Single MSL2024 connected via external connector, nothing via the internal.
HP LTO5 SAS Drive

I've hit a small issue in that Backup Exec can't communicate with my HP Autoloader. Fresh install of Windows and BE up to latest version shows this in the adamm.log

**************************** LOG FILE*************************

[05764] 01/12/20 16:47:39.276 [StorageManager::RemoveUnusedLocalDisksFromDB] Results:
0 non-present unconfigured local disks were deleted
0 local disk parent objects with no local disks were deleted
[07068] 01/12/20 16:47:46.228 DeviceIo: Discover: serialize mode_sense FAILED, lib=(0,5,0), serial="MXA050Z3WP"
[07068] 01/12/20 16:47:46.260 DeviceIo Discovery - end
[07068] 01/12/20 16:47:46.260 DeviceIo Devices:
Scsi Address
Prt :Bus :Tar :Lun Attributes
------------------- -------------------------------------------------------------------------------
0003:0000:0004:0000 DeviceIo[01]: "HP Ultrium 5-SCSI HUJ7439GCF", Cert=Y, "\\.\Tape2147483646"
0003:0000:0005:0000 DeviceIo[02]: "HP MSL G3 Series MXA050Z3WP", Cert=N, "\\.\Changer0"
------------------- -------------------------------------------------------------------------------
[07068] 01/12/20 16:47:46.260 PnP Device Paths:
Scsi Address
Prt :Bus :Tar :Lun Device Path
----------------------------------- ---------------------------------------------------------------
00000003:00000000:00000004:00000000 \\?\scsi#sequential&ven_hp&prod_ultrium_5-scsi#7&74514f4&0&000400#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
----------------------------------- ---------------------------------------------------------------
[07068] 01/12/20 16:47:46.260 Read Device Inquiries - start
[07068] 01/12/20 16:47:46.276 Backup Exec was unable to initialize and communicate with the device [HP MSL G3 Series 6.10] (The system cannot find the path specified.). Click the link below for more information on how to diagnose the problem.

**************************** LOG FILE END*************************

Windows can see the autoloader and tape drive just fine.
If I leave BE discovering services for long enough, I get this in the adamm.log and then it shows up as "online" but it doesn't work as an endpoint.

**************************** LOG FILE *************************

0003:0000:0004:0000 Device Name "\\.\Tape2147483646"
Secondary Name "\\?\scsi#sequential&ven_hp&prod_ultrium_5-scsi#7&74514f4&0&000400#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}"
Primary Inquiry "HP Ultrium 5-SCSI Z6MW"
Serial Number "HP Ultrium 5-SCSI HUJ7439GCF"
Device Flags UMD, SCSI, SN(TYPE 0)
Device State 3, Online
Device IDs 1050, {011D99CC-5C32-417E-9A50-8E951DD0CA8F}
Device Name "Tape drive 0001"
Device Type 134283265, "LTO 64K (64K,10,0,E,HU)"
Device Features 0x005BFA7F: PB,SFB,SRB,WFM,SFF,SRM,PEOD,EL,LU,E,SBS,DC,SDC,TA,HU,RR,W,EN
Device Element 0, 0
Device Block Limits 512 min, 65536 max
Device Hard Errors 0 write, 0 read
Device Soft Errors 0 write, 0 read
0003:0000:0005:0000 Device Name "\\.\Changer0"
Primary Inquiry "HP MSL G3 Series 6.10"
Serial Number "HP MSL G3 Series MXA050Z3WP"
Device Flags UMD, SN(TYPE 0)
Device State 3, Online
Device IDs 1052, {F0F6BDE3-5E47-4517-9E9D-57967B73A29E}
Device Name "Robotic library 0001"
Device Type 2131755008, "CHANGER FS=1"
Device Features 0x00026000: RMP,RRD,SMCE
1st Slot Number 1
Number Of Slots 0
Portal Slots 0
Import/Export Manual
Drives 0
0003:0000:0005:0000 Device Name "\\.\Changer0"
Primary Inquiry "HP MSL G3 Series 6.10"
Serial Number "HP MSL G3 Series MXA050Z3WP"
Device Flags UMD, SN(TYPE 0)
Device State 3, Online
Device IDs 1052, {F0F6BDE3-5E47-4517-9E9D-57967B73A29E}
Device Name "Robotic library 0001"
Device Type 2131755008, "CHANGER FS=1"
Device Features 0x00026000: RMP,RRD,SMCE
1st Slot Number 1
Number Of Slots 0
Portal Slots 0
Import/Export Manual
Drives 0

**************************** LOG FILE END*************************

Any advice?
  • Factoy reset everything now which didn't work. 

    However, I moved the drive from bay0 to bay1 on the silo, cleared everything out and now everything works.
    I can only think is that the connection is 'dirty' or damaged in that bay on the silo. 

    Erase tape job:

    Job started     : 15 January 2020 16:26:37
    Job ended : 15 January 2020 16:30:04
    Completed status: Completed with exceptions

     

    System Status

    View Legend
    Updated: Wednesday,1/15/2020 16:32:44
    Status Ready
    Drive 1 Status Ready
    Slots (Free/Total)0/24
    MailslotDisabled
    Library Time01/15/20 16:32

    Can you check over the attached adamm.log?

  • "Number Of Slots 0" and "Drives 0" definitly doesn't look right, so either the library is confused or theire is bad communication issues.

    Please make sure you are NOT using HP drivers for the robot OR the tape drive.

    Please make sure you are NOT using an unsupported RAID HBA.  Edit - now I see you are using the P212 which is supported https://www.veritas.com/content/support/en_US/article.100021088  But you might need to check with HPE to see if it is configured correctly for use with tape.

    Can you post your adamm.log file?

    • BackupMonkey50's avatar
      BackupMonkey50
      Level 3

      Hi Larry.

      The MSL is listed as a Unknown Medium Changer, driver provided by Microsoft.
      The LTO is listed as HP LTO Ultrium-5 Drive, driver provided by HP.

      I've been unable to locate a driver for this that isn't provided by HP.

      Adamm.log is attached.

      I'll keep looking for a driver. 
      Thanks for the help.