StoreEver Tape Storage

mkltfs fails with "Format operation failed (-1)" Legitimate request

 
benwbooth
Occasional Advisor

mkltfs fails with "Format operation failed (-1)" Legitimate request

I have a HPE Ultrium 8-SCSI drive with a HP 1x8 G2 AUTOLDR loader. I'm running HP StoreOpen Software version 3.4.2-9 on CentOS 7. For some reason, I am no longer able to format my LTO-8 type M tapes using the mkltfs command:

$ sudo /usr/local/bin/mkltfs --device=/dev/sg2

LTFS15000I Starting mkltfs, HPE StoreOpen Software version 3.4.2, log level 2
LTFS15041I Launched by "/usr/local/bin/mkltfs --device=/dev/sg2"
LTFS15042I This binary is built for Linux (x86_64)
LTFS15043I GCC version is 4.8.5 20150623 (Red Hat 4.8.5-11)
LTFS17087I Kernel version: Linux version 3.10.0-957.5.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Fri Feb 1 14:54:57 UTC 2019 i386
LTFS17089I Distribution: CentOS Linux release 7.6.1810 (Core)
LTFS17089I Distribution: NAME="CentOS Linux"
LTFS17089I Distribution: CentOS Linux release 7.6.1810 (Core)
LTFS17089I Distribution: CentOS Linux release 7.6.1810 (Core)
LTFS15003I Formatting device '/dev/sg2'
LTFS15004I LTFS volume blocksize: 524288
LTFS15005I Index partition placement policy: None

LTFS17085I Plugin: Loading "ltotape" driver
LTFS20013I Drive type is HPE LTO8, serial number is DEC83406M7
LTFS17160I Maximum device block size is 524288
LTFS17157I Changing the drive setting to write-anywhere mode
LTFS17302W Cannot retrieve attribute (volumelockstate=0x1623)
LTFS17302W Cannot retrieve attribute (Application Vendor=0x800)
LTFS15049I Checking the medium (mount)
LTFS15010I Creating data partition b on SCSI partition 1
LTFS15011I Creating index partition a on SCSI partition 0
LTFS17165I Resetting the medium's capacity proportion
LTFS11097I Partitioning the medium
LTFS20107I Replacing existing MAM barcode ABJ406M8                         with user-specified
LTFS20068E Format operation failed (-1)
LTFS20076I Triggering drive diagnostic dump
LTFS20096I Diagnostic dump complete
LTFS12053E Cannot format medium: backend call failed (-1)
LTFS11098E Cannot format: failed to partition the medium (-1)
LTFS15012E Failed to format the medium
LTFS20076I Triggering drive diagnostic dump
LTFS20096I Diagnostic dump complete
LTFS15023I Formatting failed

I can still mount my previously formatted tapes without any issue. But I can no longer format any new tapes.

I am attaching diagnostic dump files in case that helps: Archive.zip

Here is the output with tracing enabled:

$ sudo /usr/local/bin/mkltfs --device=/dev/sg2 -t
LTFS15000I Starting mkltfs, HPE StoreOpen Software version 3.4.2, log level 3
LTFS15041I Launched by "/usr/local/bin/mkltfs --device=/dev/sg2 -t"
LTFS15042I This binary is built for Linux (x86_64)
LTFS15043I GCC version is 4.8.5 20150623 (Red Hat 4.8.5-11)
LTFS17087I Kernel version: Linux version 3.10.0-957.5.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Fri Feb 1 14:54:57 UTC 2019 i386
LTFS17089I Distribution: CentOS Linux release 7.6.1810 (Core)
LTFS17089I Distribution: NAME="CentOS Linux"
LTFS17089I Distribution: CentOS Linux release 7.6.1810 (Core)
LTFS17089I Distribution: CentOS Linux release 7.6.1810 (Core)
LTFS15025D Validating command line options
LTFS15037D Command line options are valid
LTFS15003I Formatting device '/dev/sg2'
LTFS15004I LTFS volume blocksize: 524288
LTFS15005I Index partition placement policy: None

LTFS15006D Opening the device
LTFS17085I Plugin: Loading "ltotape" driver
LTFS20020D SG_RESERVED_SIZE (max block size) now set to 524288 bytes
LTFS20010D SCSI request: [ 12 00 00 00 F0 00 ] Requested length=240
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=70
LTFS20084D Drive identification is 'Ultrium 8-SCSI  '
LTFS20010D SCSI request: [ 12 01 80 00 20 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=14
LTFS20013I Drive type is HPE LTO8, serial number is DEC83406M7
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20061D Backend modesense: 0x11
LTFS20010D SCSI request: [ 5A 00 51 00 00 00 00 00 20 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS12023D Reserving device
LTFS20010D SCSI request: [ 16 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS12028D Unlocking medium
LTFS20010D SCSI request: [ 1E 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS17160I Maximum device block size is 524288
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20061D Backend logsense: 0x31
LTFS20010D SCSI request: [ 4D 00 71 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=36
LTFS20057D Backend capacity part0: (5722045, 5722045)
LTFS20057D Backend capacity part1: (0, 0)
LTFS20061D Backend modesense: 0x10
LTFS20010D SCSI request: [ 5A 00 10 01 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS17157I Changing the drive setting to write-anywhere mode
LTFS20061D Backend modesense: 0x10
LTFS20010D SCSI request: [ 5A 00 10 01 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS15007D Device opened
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 1B 00 00 00 01 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS12026D Locking medium in the drive
LTFS20010D SCSI request: [ 1E 00 00 00 01 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 10 00 ] Requested length=16
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=16
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 10 00 ] Requested length=16
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=16
LTFS20061D Backend logsense: 0x31
LTFS20010D SCSI request: [ 4D 00 71 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=36
LTFS20057D Backend capacity part0: (5722045, 5722045)
LTFS20057D Backend capacity part1: (0, 0)
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS20061D Backend modesense: 0x10
LTFS20010D SCSI request: [ 5A 00 10 01 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20057D Backend readattr: (0, 5376)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 15 00 00 00 00 0D 00 00 ] Requested length=13
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : 70 00 05 00 00 00 00 58 00 00 00 00 24 00 30 CF 00 08 00 00 01 03 41 42 4A 34 30 36 4D 00 00 00 0A 8C E0 00 00 5C C3 E0 81 8C 60 4C 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4C 47 50 30 52 39 37 36 34
LTFS20098D Attribute 0x1500 not found
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS20057D Backend readattr: (0, 5667)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 16 23 00 00 00 0A 00 00 ] Requested length=10
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : 70 00 05 00 00 00 00 58 00 00 00 00 24 00 30 CF 00 08 00 00 01 03 41 42 4A 34 30 36 4D 00 00 00 0A 8C E0 00 00 5C C3 E0 81 8C 60 4C 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4C 47 50 30 52 39 37 36 34
LTFS20098D Attribute 0x1623 not found
LTFS17302W Cannot retrieve attribute (volumelockstate=0x1623)
LTFS20057D Backend readattr: (0, 2048)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 08 00 00 00 00 18 00 00 ] Requested length=24
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : 70 00 05 00 00 00 00 58 00 00 00 00 24 00 30 CF 00 08 00 00 01 03 41 42 4A 34 30 36 4D 00 00 00 0A 8C E0 00 00 5C C3 E0 81 8C 60 4C 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4C 47 50 30 52 39 37 36 34
LTFS20098D Attribute 0x800 not found
LTFS17302W Cannot retrieve attribute (Application Vendor=0x800)
LTFS15049I Checking the medium (mount)
LTFS11012D Loading the tape
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 1B 00 00 00 01 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 10 00 ] Requested length=16
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=16
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 10 00 ] Requested length=16
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=16
LTFS20061D Backend logsense: 0x31
LTFS20010D SCSI request: [ 4D 00 71 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=36
LTFS20057D Backend capacity part0: (5722045, 5722045)
LTFS20057D Backend capacity part1: (0, 0)
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS20061D Backend modesense: 0x10
LTFS20010D SCSI request: [ 5A 00 10 01 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20057D Backend readattr: (0, 5376)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 15 00 00 00 00 0D 00 00 ] Requested length=13
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : 70 00 05 00 00 00 00 58 00 00 00 00 24 00 30 CF 00 08 00 00 01 03 41 42 4A 34 30 36 4D 00 00 00 0A 8C E0 00 00 5C C3 E0 81 8C 60 4C 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4C 47 50 30 52 39 37 36 34
LTFS20098D Attribute 0x1500 not found
LTFS11007D Tape is loaded
LTFS20061D Backend logsense: 0x31
LTFS20010D SCSI request: [ 4D 00 71 00 00 00 00 04 00 00 ] Requested length=1024
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=36
LTFS20057D Backend capacity part0: (5722045, 5722045)
LTFS20057D Backend capacity part1: (0, 0)
LTFS15010I Creating data partition b on SCSI partition 1
LTFS15011I Creating index partition a on SCSI partition 0
LTFS20061D Backend modesense: 0x00
LTFS20010D SCSI request: [ 5A 00 00 00 00 00 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 05 00 00 00 00 00 ] Requested length=6
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=6
LTFS17165I Resetting the medium's capacity proportion
LTFS20057D Backend locate: (0, 0)
LTFS20010D SCSI request: [ 92 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS11097I Partitioning the medium
LTFS20010D SCSI request: [ 1B 00 00 00 01 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS20061D Backend modesense: 0x1D
LTFS20010D SCSI request: [ 5A 00 1D 00 00 00 00 00 40 00 ] Requested length=64
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20061D Backend modesense: 0x11
LTFS20010D SCSI request: [ 5A 00 11 00 00 00 00 00 20 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 20 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=32
LTFS20012D SCSI sense  : 70 00 01 00 00 00 00 58 00 00 00 00 37 00 30 00 10 39 00 00 01 03 41 42 4A 34 30 36 4D 00 00 00 00 00 E0 00 00 5C C3 E0 81 55 60 4C 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4C 47 50 30 52 39 37 36 34
LTFS20057D Backend readattr: (0, 2054)
LTFS20010D SCSI request: [ 8C 00 00 00 00 00 00 00 08 06 00 00 00 2C 00 00 ] Requested length=44
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=44
LTFS20107I Replacing existing MAM barcode ABJ406M8                         with user-specified
LTFS20010D SCSI request: [ 04 00 02 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : 70 00 04 00 00 00 00 58 00 00 00 00 03 02 36 00 10 58 00 00 01 03 41 42 4A 34 30 36 4D 00 00 00 00 00 E0 00 00 5C C3 E0 81 04 60 4C 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4C 47 50 30 52 39 37 36 34
LTFS20068E Format operation failed (-1)
LTFS20092D Found 10 log snapshot files, oldest is 'ltfs_20190904_153413_DEC83406M7.ltd'
LTFS20094D Removed old snapshot file '/var/log/ltfs_20190904_153413_DEC83406M7.ltd'
LTFS20076I Triggering drive diagnostic dump
LTFS20010D SCSI request: [ 1D 11 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20010D SCSI request: [ 3C 03 01 00 00 00 00 00 04 00 ] Requested length=4
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=4
LTFS20010D SCSI request: [ 3C 02 01 00 00 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=524288
LTFS20010D SCSI request: [ 3C 02 01 08 00 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=524288
LTFS20010D SCSI request: [ 3C 02 01 10 00 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=524288
LTFS20010D SCSI request: [ 3C 02 01 18 00 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=524288
LTFS20010D SCSI request: [ 3C 02 01 20 00 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=524288
LTFS20010D SCSI request: [ 3C 02 01 28 00 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=524288
LTFS20010D SCSI request: [ 3C 02 01 30 00 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=524288
LTFS20010D SCSI request: [ 3C 02 01 38 00 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=524288
LTFS20010D SCSI request: [ 3C 02 01 40 00 00 08 00 00 00 ] Requested length=524288
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=119280
LTFS20010D SCSI request: [ 3C 1C FF 00 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20080D Saved drive dump to /var/log/ltfs_20201107_161705_DEC83406M7.ltd
LTFS20096I Diagnostic dump complete
LTFS12053E Cannot format medium: backend call failed (-1)
LTFS11098E Cannot format: failed to partition the medium (-1)
LTFS15012E Failed to format the medium
LTFS12028D Unlocking medium
LTFS20010D SCSI request: [ 1E 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20092D Found 10 log snapshot files, oldest is 'ltfs_20190905_103419_DEC83406M7.ltd'
LTFS20094D Removed old snapshot file '/var/log/ltfs_20190905_103419_DEC83406M7.ltd'
LTFS20076I Triggering drive diagnostic dump
LTFS20010D SCSI request: [ 1D 11 00 00 08 00 ] Requested length=8
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=8
LTFS20010D SCSI request: [ 3C 1C 02 00 00 00 00 01 00 00 ] Requested length=256
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=136
LTFS20010D SCSI request: [ 3C 1C 11 00 00 00 04 00 00 00 ] Requested length=262144
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=183916
LTFS20010D SCSI request: [ 3C 1C FF 00 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20080D Saved drive dump to /var/log/ltfs_20201107_161736_DEC83406M7.ltd
LTFS20096I Diagnostic dump complete
LTFS20010D SCSI request: [ 00 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20061D Backend modesense: 0x10
LTFS20010D SCSI request: [ 5A 00 10 01 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS20010D SCSI request: [ 55 10 00 00 00 00 00 00 30 00 ] Requested length=48
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=48
LTFS12025D Releasing device
LTFS20010D SCSI request: [ 17 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 01 00 00 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=0
LTFS20010D SCSI request: [ 34 06 00 00 00 00 00 00 00 00 ] Requested length=32
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x00 Actual length=32
LTFS20060D Backend ReadPosition: Partition=0, LogObject=0, FMcount=0
LTFS15023I Formatting failed

Any help would be appreciated. Thanks!

17 REPLIES 17
benwbooth
Occasional Advisor

Re: mkltfs fails with "Format operation failed (-1)" Legitimate request

Here is a link to a github issue I raised for this at the ltfs github repo. It got marked as wontfix because I'm using HP software and not vanilla LTFS. If anyone could please check this issue and offer advice, it would be greatly appreciated. Thanks!

 

https://github.com/LinearTapeFileSystem/ltfs/issues/224

Curtis_Ballard
HPE Pro

Re: mkltfs fails with "Format operation failed (-1)" Legitimate request

Not sure why your post was getting marked as spam.  The subject on this one almost looks like spam but didn't get marked.

I looked at your bug report.  The response sure wasn't helpful.  You posted good information and they could have at least looked at it.

The format fails at this point:

LTFS20010D SCSI request: [ 04 00 02 00 00 00 ] Requested length=0
LTFS20011D SCSI outcome: Driver status=0x00 SCSI status=0x02 Actual length=0
LTFS20012D SCSI sense  : 70 00 04 00 00 00 00 58 00 00 00 00 03 02 36 00 10 58 00 00 01 03 41 42 4A 34 30 36 4D 00 00 00 00 00 E0 00 00 5C C3 E0 81 04 60 4C 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4D 4C 47 50 30 52 39 37 36 34

The most interestest parts in that error message are Sense Key 04, ASC/ASCQ 03/02

That error decodes as Hardware Error, EXCESSIVE WRITE ERRORS

Have you tried multiple tapes?  If multiple tapes are failing with the same error code then maybe the write head was damaged.

Are you able to write to tapes that have already been formatted?


I work for HPE

Accept or Kudo

Parvez_AL
Community Manager

Re: mkltfs fails with "Format operation failed (-1)" Legitimate request

@benwbooth 

Sorry for the inconvenience. Our spam filter marked it as spam by error. I have merged and restored the posts now. 


Thanks,
Parvez_AL
I work for HPE
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
CM_Cert_Logo_Color.png
benwbooth
Occasional Advisor

Re: mkltfs fails with "Format operation failed (-1)" Legitimate request

Have you tried multiple tapes?  If multiple tapes are failing with the same error code then maybe the write head was damaged.

I have tried 3 or 4 different tapes. I cannot format any of them. The other tapes that worked are from the same batch of tapes with barcodes from the same barcode sheet.

Are you able to write to tapes that have already been formatted?

 I haven't tried this yet. Most of my tapes are completely full. I'll see if I can find a tape that's not completely full.

benwbooth
Occasional Advisor

Re: mkltfs fails with "Format operation failed (-1)" Legitimate request

Another thing I noticed is that in the web UI I see "Media Attention" in the System Status area. I have a brand new unformatted LTO-7 type M tape in the drive right now. If I click on the "Media Status" link it says "Media Error" in the Drive Inventory - Source section. Is this just because the media is unformatted? The other tapes that I've already written to do not give a "Media Error" status.

Curtis_Ballard
HPE Pro

Re: mkltfs fails with "Format operation failed (-1)" Legitimate request

The brand new, unformatted LTO-7 Type M tape is an interesting wrinkle.  Special processing occurs the first time those tapes are written and that has to happen using a drive in a library that supports LTO-7 Type M.

Are you are using the tape in a tape library that support LTO-7 Type M?

Can you get HPE Library and Tape Tools and run a read/write test on that tape?

I would be interesting in finding out whether the tape is able to be formatted to LTFS after it has been fully initialized.


I work for HPE

Accept or Kudo

benwbooth
Occasional Advisor

Re: mkltfs fails with "Format operation failed (-1)" Legitimate request

The brand new, unformatted LTO-7 Type M tape is an interesting wrinkle.  Special processing occurs the first time those tapes are written and that has to happen using a drive in a library that supports LTO-7 Type M.

Are you are using the tape in a tape library that support LTO-7 Type M?

Yes, LTO-8 drives can read/write LTO-7 type M tapes. I have already successfully written and read back about a dozen of type M tapes in the past.

Can you get HPE Library and Tape Tools and run a read/write test on that tape?

I would be interesting in finding out whether the tape is able to be formatted to LTFS after it has been fully initialized.

I have the ltt tools installed. I'm not sure which test is the read/write test you're referring to.  I ran the "Backup Performance Test" but it seemed to finish nearly instantaneously. I got this for the results:

0.429578 MB read (136 files) in 0.010783 seconds with rate 39.838433 MB/sec
Backup Performance Test successfully read files.

I ran the restore performance test:

1020 KB written (8 files) in 0 seconds at 230821 KB/sec
Restore Performance Test successfully created files.

These tests were both done with an unformatted disk in the drive, so I'm not sure if the results are even valid.

Thanks for your help looking into this!

Curtis_Ballard
HPE Pro

Re: mkltfs fails with "Format operation failed (-1)" Legitimate request

The Backup and Restore performance tests are used to test the maximum possible rates for your system without actually read/writing to the tape.  They test the infrastructure outside of the tape drive.

For a simple write/read test the "Drive Performance Test" is my preferred quick check.

I regret to report that I asked a person more familiar with the low level error codes than I am to take a look at this and they reported that there is a low level drive error code in the additional information for the error I pulled out earlier indicating that the failure writing was due to an issue with a write head open circuit.

It looks like there is a write head failure in the tape drive.

You should run the "Drive Assessment" test with L&TT and see what it reports.  That runs a pretty exhaustive test on the drive.


I work for HPE

Accept or Kudo

benwbooth
Occasional Advisor

Re: mkltfs fails with "Format operation failed (-1)" Legitimate request

The Backup and Restore performance tests are used to test the maximum possible rates for your system without actually read/writing to the tape.  They test the infrastructure outside of the tape drive.

For a simple write/read test the "Drive Performance Test" is my preferred quick check.

I regret to report that I asked a person more familiar with the low level error codes than I am to take a look at this and they reported that there is a low level drive error code in the additional information for the error I pulled out earlier indicating that the failure writing was due to an issue with a write head open circuit.

It looks like there is a write head failure in the tape drive.

You should run the "Drive Assessment" test with L&TT and see what it reports.  That runs a pretty exhaustive test on the drive.

Thanks for your help Curtis. I can't seem to find either the "Drive Performance Test" or the "Drive Assessment" test in the ltt tool. I'm using ltt 4.28. Do I need a newer version of the ltt tools to find these tests? It looks like there is a section in the ltt tools to enter a password. I tried entering the numeric access password for the loader, but it didn't work. The only tests I've been able to find are the backup and restore tests. The menu system is somewhat hard to navigate. Can you tell me how to find these tests?

Thanks!