Forum Discussion

HPeter's avatar
HPeter
Level 3
7 years ago
Solved

LTO-5 storage error

We have moved our BE16 from a W2k8r2 server to a WS16. All backups and setting are great expect the LTO-5 drive.
The LTO was moved from the old server to the new one, but with new SAS card and cable.
The device is an HP Ultrium 5-SCSI with ( Z6ED ) firmware. The SAS card docs prefer (Z6DW) firmware, so I ran "HPE Library and Tape Tools" for a test. All was passed, so the hardware looks good.

In BE I see a storage error message:
"
Backup Exec 58053
Backup Exec Alert: Storage Error
(Server: "S-XX-XXXX") The device state has been set to offline because of an I/O device error.
Ensure that the drive hardware is turned on and is properly cabled. After you correct the problem, right-click the device, and then click Offline to clear the check mark and bring the device online.
Check the event log for information about the SCSI sense data that caused the error. For more information about SCSI sense errors, see the device vendor's documentation.
"

We removed the device and add again, we deleted directly form the database and add again and so on but the issue is permanent.

My very last idea, I will try to move the old SAS card and cable form the old server to the new one, but before I will do this, I try to find solution in this forum.

- The Old card is a HP H221 HBA
- The new is Adaptec HBA 1000 8e
- The BE version is BE16FP2
- The drive is HP LTO-5 Ultrium 3000

Has anybody any idea what could be the problem or what could be the solution?

 

16
LTO-5
Storage error
Windows Server 2016
  • Larry_Fine's avatar
    Larry_Fine
    7 years ago

    The Adaptec HBA you mentioned appears to NOT be a RAID HBA, which is good.  That means it should be supported per http://www.veritas.com/docs/000038683

    But, the string of errors in your adamm.log and the fact that you believe the tape drive is healthy, sure make me suspect that SAS HBA or the HBA driver is cuasing trouble.  If you are already using the latest driver and firmware, I think you are on the right path to try a test with the old HBA.

  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    7 years ago

    Are you trying to run a newly created job when you see this error, or a migrated job that was created in the original installation?

    If it is a migrated job then it may be because we now identify the device as different (because of the OS and server hardware changes) and the migrated job may be trying to reference the old id and understandably is not able to communicate with it.

    If new jobs work then you will either have to edit and re-target all your old jobs, OR as a worse case scenario, delete and recreate them. Once no jobs target the old device, if it is visible as offline in storage then you may need to delete the reference to it.

     

    • HPeter's avatar
      HPeter
      Level 3
      7 years ago

      The problem appeared before any job. When I opened the surface the error was there.
      After that I triede to run a simple "inventory now" with a tape but it was not worked.
      Beside that we replaced a job's target to our DXI and later back, but nothing changed.

       

       

    • HPeter's avatar
      HPeter
      Level 3
      7 years ago

      I tried to copy spme lines which could be important and I encosed the relevant part of adamm.log
      I see PDDM erro and invalis SCSI functions. If the drive looks OK why I got this messages?

       

      [04060] 08/09/18 14:56:47.335 Waiting on PDDE service start (3600000 milliseconds)
      [04060] 08/09/18 14:56:47.335 Error waiting for PDDE service to start: 1060
      [04060] 08/09/18 14:56:47.335 PDDE service has not started; continuing...
      Treat all LTO devices as if they are in UMD certified device list: DioAllLto = 0x0001
      Use UMD certified device list: DioDrivers = 0x0002

      ..

      [10156] 08/09/18 15:14:56.657 DeviceIo: Discover: SwitchOver Adapter Info NULL for pathIde=1
      [10156] 08/09/18 15:14:56.657 DeviceIo: SwitchOver Logic Failed Pass 02
      [10156] 08/09/18 15:14:56.657 DeviceIo: No Handle In Shared Memory To Duplicate.
      [10156] 08/09/18 15:14:56.657 DeviceIo: 01:01:00:00 - Error Invalid Function on "\\.\Scsi1:", SCSI cmd 1a, 448 total errors

      • Colin_Weaver's avatar
        Colin_Weaver
        Moderator
        7 years ago

        The PDDE error can be ignored as it relates to attempting to find a deduplication device (and as  I suspect you are not using that feature the error is expected)

        This combination is you problem though

        [08012] 08/09/18 15:06:39.960 DeviceIo: 01:01:00:00 - Device error 1 on "\\.\Scsi1:", SCSI cmd 16, 1 total errors
        [08012] 08/09/18 15:06:39.960 DeviceIo: 01:01:00:00 - Error Invalid Function on "\\.\Scsi1:", SCSI cmd 16, 1 total errors
        [08012] 08/09/18 15:06:39.961 DeviceIo: Discover: SwitchOver Adapter Info NULL for pathIde=1
        [08012] 08/09/18 15:06:39.961 DeviceIo: SwitchOver Logic Failed Pass 02
        [08012] 08/09/18 15:06:39.961 DeviceIo: No Handle In Shared Memory To Duplicate.

        If you look in the Windows Event logs (System and Application) for the same times as these errors, do you see any issues with hardware being reported within the OS?