DP 9 - Cannot format LTO6 Tapes

Hi all,

We have just upgraded all of our LTO4 tapes to LTO6 tapes. We have an HPE MSL 4048 Tape Library (firmware up to date) with a LTO6 Tape drive.

Successfully added to Data Protector 9, and also scan tapes normally. But when trying to format tapes we are getting an error.

Here is full session output

[Normal] From: MSM@s1ntitdp01.nuevatel.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 5:47:29 PM
    Media session 2018/09/27-6 started.

[Normal] From: MMA@s1ntitdp01.nuevatel.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 5:47:29 PM
    STARTING Media Agent "HP:Ultrium 6-SCSI_1_s1ntitdp01"

[Normal] From: MMA@s1ntitdp01.nuevatel.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 5:47:35 PM
    => UMA@s1ntitdp01.xXx.net@Changer0:0:0:1
    Loading medium from slot 1 to device Tape0:0:0:0C

[Normal] From: MSM@s1ntitdp01.xXx.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 5:50:03 PM
    Blank medium found.
    Initialization allowed.

[Normal] From: MMA@s1ntitdp01.xXx.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 5:50:03 PM
    Tape0:0:0:0C
    Initializing new medium: "[OP0121L6] Default LTO-Ultrium_18"

[Major] From: MMA@s1ntitdp01.xXx.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 6:00:07 PM
[90:51]      Tape0:0:0:0C
    Cannot write to device ([1117] The request could not be performed because of an I/O device error. )

[Major] From: MMA@s1ntitdp01.xXx.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 6:00:07 PM
[90:159]     Apparently SCSI Unit Attention.

[Major] From: MMA@s1ntitdp01.xXx.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 6:00:18 PM
    Initialization of medium failed.

[Normal] From: MMA@s1ntitdp01.xXx.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 6:00:39 PM
    Ejecting medium '1'.

[Normal] From: MMA@s1ntitdp01.xXx.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 6:00:39 PM
    => UMA@s1ntitdp01.xXx.net@Changer0:0:0:1
    Unloading medium to slot 1 from device Tape0:0:0:0C

[Normal] From: MMA@s1ntitdp01.xXx.net "HP:Ultrium 6-SCSI_1_s1ntitdp01" Time: 9/27/2018 6:01:16 PM
    ABORTED Media Agent "HP:Ultrium 6-SCSI_1_s1ntitdp01"

devbra -dev output:

Exch    HP:MSL G3 Series  Path: "Changer0:0:0:1"  SN: "MXA623Z0DD"
        Description: CLAIMED:HP StorageWorks MSL 2024 G3 Series
        Revision: 8.90  Flags: 0x0016  Slots: 48  Drives: 1
        Drive(s) SN:
                "HUJ62368M6"

Tape    HP:Ultrium 6-SCSI  Path: "Tape0:0:0:0C"  SN: "HUJ62368M6"
        Description: CLAIMED:HP LTO6 Drive
        Revision: 25GW  Device type: lto [13]  Flags: 0x0111

Exch    HP:MSL G3 Series  Path: "Changer2:0:1:1"  SN: "MXA94110F7"
        Description: CLAIMED:HP StorageWorks MSL 2024 G3 Series
        Revision: 9.40  Flags: 0x0016  Slots: 45  Drives: 2
        Drive(s) SN:
                "HU1052EALG"
                "HU1052EALY"

Tape    HP:Ultrium 4-SCSI  Path: "Tape2:0:1:0C"  SN: "HU1052EALY"
        Description: CLAIMED:HP LTO4 Drive
        Revision: H6FW  Device type: lto [13]  Flags: 0x0111

(We have two libraries added to Data Protector, MSL2024 and MSL4048)

(note that both appears as MSL2024 G3 Series)

Data Protector Installed patch output

Patch level         Patch description
===========================================
DPWIN_20234 (A.09.09_115) Core Component
DPWIN_20234 (A.09.09_115) Core of Integrations component
DPWIN_20235 (A.09.09_115) Cell Manager Component
DPWIN_20236 (A.09.09_115) Disk Agent
DPWIN_20237 (A.09.09_115) General Media Agent
DPWIN_20238 (A.09.09_115) User Interface
DPWIN_20239 (A.09.09_115) Virtual Environment Integration
DPWIN_20205 (A.09.09) English Documentation (Guides, Help)
DPWIN_20234 (A.09.09_115) Pegasus Libraries
DPWIN_20234 (A.09.09_115) Core Technology Stack
DPWIN_20235 (A.09.09_115) Cell Server Technology Stack
DPWIN_20235 (A.09.09_115) Application Server Technology Stack
DPWIN_20235 (A.09.09_115) Web Services
DPWIN_20235 (A.09.09_115) Java Runtime Environment Technology Stack
DPWIN_20235 (A.09.09_115) Job Control Engine Service Dispatcher
DPWIN_20235 (A.09.09_115) Job Control Engine Service Registry
Number of patches found: 16.

¿Any idea or approach to solve this problem?

Regards!