HP TapeLibrary MSL6000 wait_until_ready failed

[FabianLPHD]

Hey there,

i have a problem with my Tape Library. It's a MSL6000 with 4x Ultrium 1840 LTO-4 Drives.

Format / Label Media and so on is working, if i first load the tape.


If i want to create a Backup on Tape, or Format the Tape without loading it first, so it does that automaticly,
the library put the tape into the drive, but proxmox doesn't know that and is waiting forever.
Task Output:

2022-05-13T10:49:51+02:00: update media online status
2022-05-13T10:49:51+02:00: starting new media set - reason: forced
2022-05-13T10:49:51+02:00: media set uuid: a8bfbb24-3601-487c-af21-3e7b0a2d2cf8
2022-05-13T10:49:51+02:00: found 22 groups
2022-05-13T10:49:51+02:00: backup snapshot ct/100/2022-05-12T20:20:29Z
2022-05-13T10:49:51+02:00: allocated new writable media 'PCO453L4'
2022-05-13T10:49:51+02:00: loading media 'PCO453L4' into drive 'Drive0'
2022-05-13T11:00:19+02:00: TASK ERROR: open drive 'Drive0' (/dev/tape/by-id/scsi-HUE3510CY1-sg) failed - wait_until_ready failed - got timeout

My Version:

proxmox-backup             2.1-1        running kernel: 5.13.19-6-pve
proxmox-backup-server      2.1.8-1      running version: 2.1.8
pve-kernel-helper          7.2-3
pve-kernel-5.13            7.1-9
pve-kernel-5.13.19-6-pve   5.13.19-15
pve-kernel-5.13.19-1-pve   5.13.19-3
ifupdown2                  3.1.0-1+pmx3
libjs-extjs                7.0.0-1
proxmox-backup-docs        2.1.8-1
proxmox-backup-client      2.1.8-1
proxmox-mini-journalreader 1.2-1
proxmox-widget-toolkit     3.4-10
pve-xtermjs                4.16.0-1
smartmontools              7.2-pve3
zfsutils-linux             2.1.4-pve1

Maybe it can be fixed somehow, because all other functions are working fine so far.

Thanks in advance.

 

[FabianLPHD]

Now i got it to attempted to do something more:
I formated all tapes, load one, Label Media and created a backup job.

2022-05-13T12:33:38+02:00: update media online status
2022-05-13T12:33:38+02:00: media set uuid: 476d4412-7fee-4649-8dbd-376822e8258c
2022-05-13T12:33:38+02:00: found 22 groups
2022-05-13T12:33:38+02:00: backup snapshot ct/100/2022-05-12T20:20:29Z
2022-05-13T12:33:38+02:00: allocated new writable media 'PCO453L4'
2022-05-13T12:33:38+02:00: loading media 'PCO453L4' into drive 'Drive1'
2022-05-13T12:33:38+02:00: found media label PCO453L4 (012d4ea1-192b-41ae-a104-4f7519578dd6)
2022-05-13T12:33:38+02:00: writing new media set label (overwrite '00000000-0000-0000-0000-000000000000/0')
2022-05-13T12:33:40+02:00: moving to end of media
2022-05-13T12:33:45+02:00: TASK ERROR: write chunk failed - write failed - Aborted Command, Additional sense: Information unit iuCRC error detected

 

[dcsapak]

please note that we don't actively support LTO4 drives/libararies, LTO5 is required for all to work properly.

that said, we try to make it work (if sensible).

2022-05-13T12:33:45+02:00: TASK ERROR: write chunk failed - write failed - Aborted Command, Additional sense: Information unit iuCRC error detected

searching for that error brings some threads about problems with the hba/raid controller. Did you check the available firmware (for the hba/raid controller, and the tape lib/drives) ?