proxmox 8.0.3 and 7.4-16 with smartmontools 7.2-pve3 and 7.3-pve1"program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO"

Szymons

Member
Feb 11, 2021
69
8
13
Poland
Hello,

I have dmesg errors :

program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

proxmox version:
proxmox-ve: 7.4-1 (running kernel: 5.15.108-1-pve)
pve-manager: 7.4-15 (running version: 7.4-15/a5d2a31e)
pve-kernel-5.15: 7.4-4
pve-kernel-5.15.108-1-pve: 5.15.108-1
pve-kernel-5.15.107-2-pve: 5.15.107-2
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.2-1
proxmox-backup-file-restore: 2.4.2-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-4
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

I found that that could be some old smart version issue :
https://www.smartmontools.org/changeset/5348
https://www.smartmontools.org/ticket/1618
 
I can admit that also in proxmox v8 there is that same smartmontools version

v8.00
ii smartmontools 7.2-pve3

Edit ! :
now in v8.03 there is
ii smartmontools 7.3-pve1


and in both version BUG is present :

Code:
[ 3311.342359] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[ 3311.490039] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[ 3311.490345] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[ 3311.578589] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[ 3311.580487] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[ 3311.581473] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[ 3311.623365] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[ 3311.625046] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[ 5926.129408] hrtimer: interrupt took 8660 ns
root@hv-03:~# dpkg -l | grep smart
ii  libsmartcols1:amd64                  2.38.1-5+b1                        amd64        smart column output alignment library
ii  smartmontools                        7.3-pve1                           amd64        control and monitor storage systems using S.M.A.R.T.
root@hv-03:~#

Code:
root@hv-03:~# pveversion -v
proxmox-ve: 8.0.1 (running kernel: 6.2.16-5-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)
pve-kernel-6.2: 8.0.4
pve-kernel-5.15: 7.4-4
pve-kernel-5.4: 6.4-18
pve-kernel-6.2.16-5-pve: 6.2.16-6
pve-kernel-6.2.16-3-pve: 6.2.16-3
pve-kernel-5.15.108-1-pve: 5.15.108-1
pve-kernel-5.4.189-2-pve: 5.4.189-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.0
libpve-access-control: 8.0.3
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.6
libpve-guest-common-perl: 5.0.3
libpve-http-server-perl: 5.0.4
libpve-network-perl: 0.8.1
libpve-rs-perl: 0.8.4
libpve-storage-perl: 8.0.2
libqb0: 1.0.5-1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.1-1
proxmox-backup-file-restore: 3.0.1-1
proxmox-kernel-helper: 8.0.2
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.2
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-3
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1
 
Last edited:
seeing the same here, but only on 1 of my 3 pve nodes.
dmesg is being "flooded" with these every minute, 24 at a time (i've 13 sata disks connected, so isnt 1:1).

what i cant tell is if it's a per-model of disk issue, as theres no info on what devices its complaining about; is it 1 disk 24 times, or 4 disks 6x etc.
I'm running a mix of onboard sata and 2x similar but not identical PCIe sata cards and i think all ahci connected.
seems to have started when i upgraded to v8, but i've also done various other work recently like CPU & motherboard swap.
 
Last edited:
Hi,
we try to stay based off the Debian version, which is 7.3 currently. There is a Debian bug report about this issue already: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907842
Maybe you'd like to bump it, indicating that it's still an issue and that a fix is available upstream already.
 
  • Like
Reactions: i_am_jam
Do you have any actual issues or is it just the log messages? It's unfortunately a non-trivial change, so trying to backport carries the risk to break something for somebody else.
 
I cannot see 'dmesg' startup information cause there is only :
View attachment 55821

this is not enought ?
I know it's annoying, but if there is no real breakage and it doesn't affect more users, then it's not important enough to:
  • put in the work to look at the nontrivial upsteam change in detail and understand if it can be backported safely
  • diverge from Debian's package more
  • risk breaking things for other users
You can filter out those messages, to get what you really want to see.
 
I cannot see 'dmesg' startup information cause there is only :
View attachment 55821

this is not enought ?
Are you using Zabbix to monitor your proxmox server?
Because I'm using it and it also spams this message in dmesg.

But you can set rsyslog to ignore it, so it doesn't bother you anymore. (I believe pve 8 doesn't have rsyslog but journalctl, so this isn't aplicable for it unless you upgraded it from 7.4).

create this file: /etc/rsyslog.d/10-filter-smartctl-syslog.conf with this content:
Bash:
# Filter out messages like these:
# Oct  4 13:20:19 px02 kernel: [609055.097277] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

:msg, contains, "program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO" stop

And then /etc/init.d/rsyslog restart
 
Last edited:
您是否正在使用Zabbix来监控您的proxmox服务器?
因为我正在使用它,它也在 dmesg 中发送此消息的垃圾邮件。

但是您可以将 rsyslog 设置为忽略它,这样它就不会再打扰您了。(我相信 pve 8 没有 rsyslog 而是 journalctl,所以除非您从 7.4 升级它,否则这不适用于它)。

创建此文件: 包含以下内容:/etc/rsyslog.d/10-filter-smartctl-syslog.conf
Bash:
# 过滤掉如下消息:
# Oct 4 13:20:19 px02 内核: [609055.097277] 程序 smartctl 正在使用已弃用的 SCSI ioctl,请将其转换为 SG_IO

:msg,包含“程序 smartctl 正在使用已弃用的 SCSI ioctl,请将其转换为 SG_IO” stop

然后/etc/init.d/rsyslog restart
我真的希望他的问题能有一个彻底的解决方案
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!