[SOLVED] After update from 6.4 to 7.2 the tape drive can't be accessed

[digidax]

Spoiler: pveversion

root@pve4:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.35-2-pve)
pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc)
pve-kernel-5.15: 7.2-4
pve-kernel-helper: 7.2-4
pve-kernel-5.4: 6.4-18
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.4.189-2-pve: 5.4.189-2
pve-kernel-5.4.162-1-pve: 5.4.162-2
pve-kernel-5.4.128-1-pve: 5.4.128-2
pve-kernel-5.4.124-1-pve: 5.4.124-2
pve-kernel-5.4.119-1-pve: 5.4.119-1
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-4
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

Hi there,
I have done the upgrade from 6.4 to 7.2 with a node, where a tape drive was used.
After upgrade, I can't access it (QUANTUM ULTRIUM-HH7) from the node (LXC CT not tested because node must working first):

root@pve4:~# lsscsi -g
[1:2:0:0]    disk    LSI      RAID 5/6 SAS 6G  2.13  /dev/sda   /dev/sg0
[2:0:0:0]    disk    ATA      WDC WD10EZRZ-00H 1A01  /dev/sdb   /dev/sg4
[6:0:0:0]    disk    ATA      WDC WD10EZRZ-00H 1A01  /dev/sdc   /dev/sg5
[9:0:0:0]    tape    QUANTUM  ULTRIUM-HH7      MA71  /dev/st0   /dev/sg1
[9:0:1:0]    enclosu Adaptec  Smart Adapter    3.53  -          /dev/sg2
[9:2:0:0]    storage Adaptec  1100-4i          3.53  -          /dev/sg3

root@pve4:~# lsmod | grep scsi
iscsi_tcp              24576  0
libiscsi_tcp           32768  1 iscsi_tcp
libiscsi               65536  3 libiscsi_tcp,iscsi_tcp,ib_iser
scsi_transport_iscsi   135168  5 libiscsi_tcp,iscsi_tcp,ib_iser,libiscsi
scsi_transport_sas     45056  2 ses,smartpqi

root@pve4:/# ls -l /dev/tape/by-id
lrwxrwxrwx 1 root root  9 Jun 16 11:45 scsi-10WT127230 -> ../../st0
lrwxrwxrwx 1 root root 10 Jun 16 11:45 scsi-10WT127230-nst -> ../../nst0
lrwxrwxrwx 1 root root  9 Jun 16 11:45 scsi-3500507631218dd5c -> ../../st0
lrwxrwxrwx 1 root root 10 Jun 16 11:45 scsi-3500507631218dd5c-nst -> ../../nst0

root@pve4:~# ls -l /dev/n*
crw-rw---- 1 root tape  9, 128 Jun 16 11:12 /dev/nst0
crw-rw---- 1 root tape  9, 224 Jun 16 11:12 /dev/nst0a
crw-rw---- 1 root tape  9, 160 Jun 16 11:12 /dev/nst0l
crw-rw---- 1 root tape  9, 192 Jun 16 11:12 /dev/nst0m

root@pve4:~# ls -l /dev/st*
crw-rw---- 1 root tape 9,  0 Jun 16 11:12 /dev/st0
crw-rw---- 1 root tape 9, 96 Jun 16 11:12 /dev/st0a
crw-rw---- 1 root tape 9, 32 Jun 16 11:12 /dev/st0l
crw-rw---- 1 root tape 9, 64 Jun 16 11:12 /dev/st0m

root@pve4:~# mt -f /dev/st0 status
mt: /dev/st0: rmtopen failed: Input/output error

Can anyone help me please?

 

[digidax]

I will do now a clean install of 7.2 on this node and if the tape can not be used from the node, I will reinstall 6.4
to get working my Bareos Backup System inside the CT.

 

[dcsapak]

if you read this before reinstalling with 6.4, could you maybe post the output of 'dmesg' and try the 5.13 kernel instead of 5.15?

 

[digidax]

Have make a clean install of 7.2 from ISO, now I can handle the tape drive from the node:

root@pve4:~# mt -f /dev/st0 status
drive type = 114
drive status = 1543503872
sense key error = 0
residue count = 0
file number = 0
block number = 0

At the moment I add the node back to the cluster and restore the CT with Beareos inside. Will keeping updated this thred.

actual versions

Spoiler: PVE Versions

proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve) pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc) pve-kernel-helper: 7.2-4 pve-kernel-5.15: 7.2-1 pve-kernel-5.15.30-2-pve: 5.15.30-3 ceph-fuse: 15.2.16-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve1 libproxmox-acme-perl: 1.4.2 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.2-2 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.2-2 libpve-guest-common-perl: 4.1-2 libpve-http-server-perl: 4.1-2 libpve-storage-perl: 7.2-4 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.12-1 lxcfs: 4.0.12-pve1 novnc-pve: 1.3.0-3 proxmox-backup-client: 2.2.3-1 proxmox-backup-file-restore: 2.2.3-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.5.1 pve-cluster: 7.2-1 pve-container: 4.2-1 pve-docs: 7.2-2 pve-edk2-firmware: 3.20210831-2 pve-firewall: 4.2-5 pve-firmware: 3.4-2 pve-ha-manager: 3.3-4 pve-i18n: 2.7-2 pve-qemu-kvm: 6.2.0-10 pve-xtermjs: 4.16.0-1 qemu-server: 7.2-3 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.7.1~bpo11+1 vncterm: 1.7-1 zfsutils-linux: 2.1.4-pve1

root@pve4:~# uname -a
Linux pve4 5.15.30-2-pve #1 SMP PVE 5.15.30-3 (Fri, 22 Apr 2022 18:08:27 +0200) x86_64 GNU/Linux

 

[digidax]

Everything is working well. Installing 7.2 from ISO instead of upgrade from 6.4 to 7.2 solves the problem with accessing the tape drive.