Unable to upgrade -

IrishJim

New Member
Jun 9, 2021
4
0
1
38
Hello,

I have been searching for a solution to the issue of being unable to upgrade. Versions, outputs from commands etc below. I have been able to upgrade once before after the initial installation but now I am unable to. Any help or advice would be great.


Code:
proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-7
pve-kernel-5.3: 6.1-5
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.13-2-pve: 5.3.13-2
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-22
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

Repository: /etc/apt/sources.list ( I have also # out the enterprise list)

Code:
deb http://ftp.debian.org/debian buster main contrib

deb http://ftp.debian.org/debian buster-updates main contrib

# security updates
deb http://security.debian.org/debian-security buster/updates main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

apt update:

Code:
root@lab:~# apt update
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:2 http://ftp.debian.org/debian buster InRelease                                                                   
Hit:3 http://ftp.debian.org/debian buster-updates InRelease                                                           
Hit:4 http://download.proxmox.com/debian/pve buster InRelease                                       
Fetched 65.4 kB in 0s (145 kB/s)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
139 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Target Packages (pve-no-subscription/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/pve-community.list:1
W: Target Packages (pve-no-subscription/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/pve-community.list:1
W: Target Translations (pve-no-subscription/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/pve-community.list:1
W: Target Translations (pve-no-subscription/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/pve-community.list:1
W: Target Packages (pve-no-subscription/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/pve-community.list:1
W: Target Packages (pve-no-subscription/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/pve-community.list:1
W: Target Translations (pve-no-subscription/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/pve-community.list:1
W: Target Translations (pve-no-subscription/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/pve-community.list:1
root@lab:~#


apt upgrade:

Code:
root@lab:~# apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  curl idn libcurl4 libfuse3-3 libproxmox-acme-perl libproxmox-acme-plugins libproxmox-backup-qemu0 libqrencode4 libyaml-0-2 libyaml-libyaml-perl
  proxmox-archive-keyring proxmox-backup-client proxmox-backup-file-restore proxmox-backup-restore-image pve-kernel-5.3.18-3-pve pve-kernel-5.4 pve-kernel-5.4.114-1-pve
  qrencode zstd
The following packages have been kept back:
  libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-initramfs zfs-zed zfsutils-linux
The following packages will be upgraded:
  apt apt-utils base-files bind9-host ca-certificates corosync dbus debian-archive-keyring dnsutils file fuse groff-base iproute2 iputils-ping krb5-locales
  libapt-inst2.0 libapt-pkg5.0 libavahi-client3 libavahi-common-data libavahi-common3 libbind9-161 libbsd0 libcairo2 libcfg7 libcmap4 libcorosync-common4 libcpg4
  libcups2 libcurl3-gnutls libdbus-1-3 libdns-export1104 libdns1104 libefiboot1 libefivar1 libfreetype6 libfuse2 libgnutls30 libgnutlsxx28 libgssapi-krb5-2
  libgstreamer-plugins-base1.0-0 libicu63 libirs161 libisc-export1100 libisc1100 libisccc161 libisccfg163 libjpeg62-turbo libjs-jquery libjs-underscore libjson-c3
  libk5crypto3 libknet1 libkrb5-3 libkrb5support0 libldap-2.4-2 libldap-common libldb1 liblwres161 liblz4-1 libmagic-mgc libmagic1 libnss-systemd libnss3 libp11-kit0
  libpam-systemd libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libperl5.28 libpve-access-control libpve-apiclient-perl libpve-cluster-api-perl
  libpve-cluster-perl libpve-common-perl libpve-guest-common-perl libpve-http-server-perl libpve-storage-perl libpython3.7 libpython3.7-minimal libpython3.7-stdlib
  libquorum5 libsqlite3-0 libssl1.1 libsystemd0 libudev1 libunwind8 libvotequorum8 libx11-6 libx11-data libx11-xcb1 libxml2 libzstd1 linux-libc-dev lxc-pve lxcfs
  nfs-common nmap nmap-common openssl perl perl-base perl-modules-5.28 postfix proxmox-ve proxmox-widget-toolkit pve-cluster pve-container pve-docs pve-edk2-firmware
  pve-firewall pve-firmware pve-ha-manager pve-i18n pve-kernel-5.3 pve-kernel-helper pve-manager pve-qemu-kvm pve-xtermjs python-apt-common python3-apt python3.7
  python3.7-minimal qemu-server smartmontools spl sqlite3 systemd systemd-sysv tcpdump tzdata udev vncterm
132 upgraded, 19 newly installed, 0 to remove and 7 not upgraded.
Need to get 0 B/316 MB of archives.
After this operation, 859 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
dpkg: unrecoverable fatal error, aborting:
 loading files list file for package 'spiceterm': cannot read /var/lib/dpkg/info/spiceterm.list (Input/output error)
E: Sub-process /usr/bin/dpkg returned an error code (2)
 
Target Packages (pve-no-subscription/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/pve-community.list:1
You have defined your repository also in /etc/apt/sources.list.d/pve-community.list
It's best to follow the admin documentation [1]

So I think you need to delete /etc/apt/sources.list.d/pve-community.list.

Another important thing:
apt upgrade
Always use dist-upgrade, never use upgrade on pve. [2]

[1] https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_package_repositories
[2] https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_pac
 
I #'d out the /pve-community.list entry, and then ran apt update again, that issue looks resolved. It's now not stating that the package is configured multiple times. thanks :)

I re-ran the apt update:

Code:
root@lab:~# apt update
Hit:1 http://ftp.debian.org/debian buster InRelease
Get:2 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:3 http://ftp.debian.org/debian buster-updates InRelease                   
Hit:4 http://download.proxmox.com/debian/pve buster InRelease                 
Fetched 65.4 kB in 1s (95.5 kB/s)                         
Reading package lists... Done
Building dependency tree       
Reading state information... Done
139 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@lab:~# apt dis-upgrade
E: Invalid operation dis-upgrade

apt dist-upgrade returned the same error:

Code:
root@lab:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
The following NEW packages will be installed:
  curl idn libcurl4 libfuse3-3 libnvpair3linux libproxmox-acme-perl libproxmox-acme-plugins libproxmox-backup-qemu0 libqrencode4 libuutil3linux libyaml-0-2
  libyaml-libyaml-perl libzfs4linux libzpool4linux proxmox-archive-keyring proxmox-backup-client proxmox-backup-file-restore proxmox-backup-restore-image
  pve-kernel-5.3.18-3-pve pve-kernel-5.4 pve-kernel-5.4.114-1-pve qrencode zstd
The following packages will be upgraded:
  apt apt-utils base-files bind9-host ca-certificates corosync dbus debian-archive-keyring dnsutils file fuse groff-base iproute2 iputils-ping krb5-locales
  libapt-inst2.0 libapt-pkg5.0 libavahi-client3 libavahi-common-data libavahi-common3 libbind9-161 libbsd0 libcairo2 libcfg7 libcmap4 libcorosync-common4 libcpg4
  libcups2 libcurl3-gnutls libdbus-1-3 libdns-export1104 libdns1104 libefiboot1 libefivar1 libfreetype6 libfuse2 libgnutls30 libgnutlsxx28 libgssapi-krb5-2
  libgstreamer-plugins-base1.0-0 libicu63 libirs161 libisc-export1100 libisc1100 libisccc161 libisccfg163 libjpeg62-turbo libjs-jquery libjs-underscore libjson-c3
  libk5crypto3 libknet1 libkrb5-3 libkrb5support0 libldap-2.4-2 libldap-common libldb1 liblwres161 liblz4-1 libmagic-mgc libmagic1 libnss-systemd libnss3 libp11-kit0
  libpam-systemd libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libperl5.28 libpve-access-control libpve-apiclient-perl libpve-cluster-api-perl
  libpve-cluster-perl libpve-common-perl libpve-guest-common-perl libpve-http-server-perl libpve-storage-perl libpython3.7 libpython3.7-minimal libpython3.7-stdlib
  libquorum5 libsqlite3-0 libssl1.1 libsystemd0 libudev1 libunwind8 libvotequorum8 libx11-6 libx11-data libx11-xcb1 libxml2 libzstd1 linux-libc-dev lxc-pve lxcfs
  nfs-common nmap nmap-common openssl perl perl-base perl-modules-5.28 postfix proxmox-ve proxmox-widget-toolkit pve-cluster pve-container pve-docs pve-edk2-firmware
  pve-firewall pve-firmware pve-ha-manager pve-i18n pve-kernel-5.3 pve-kernel-helper pve-manager pve-qemu-kvm pve-xtermjs python-apt-common python3-apt python3.7
  python3.7-minimal qemu-server smartmontools spl sqlite3 systemd systemd-sysv tcpdump tzdata udev vncterm zfs-initramfs zfs-zed zfsutils-linux
135 upgraded, 23 newly installed, 4 to remove and 0 not upgraded.
Need to get 0 B/318 MB of archives.
After this operation, 860 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
dpkg: unrecoverable fatal error, aborting:
 loading files list file for package 'spiceterm': cannot read /var/lib/dpkg/info/spiceterm.list (Input/output error)
E: Sub-process /usr/bin/dpkg returned an error code (2)
 
Something seems to be wrong with dpkg status of package spiceterm.
Question is how much time do you want to spend investigating what the problem is. A reinstall of pve could be faster, off course after backing up your current VM's and perhaps config.

However, It could also be a hardware issue with the drive you installed proxmox on or faulty ram.
If you upgraded before with just upgrade and not dist-upgrade, question remains in what current state you're system really is now.

If you go troubleshoot, first thing I would look for is in your journal, and see if there are hardware related issues:
journalctl -b

If all seems fine you could try some quick apt or dpkg command to try a repair or finish of a pending package config.
dpkg --configure -a
or
try to remove the package:
apt remove spiceterm
And install it again:
apt install spiceterm
 
Last edited:
From the journalctl -b:

Seems fine bar the following:

Code:
un 09 11:00:18 lab kernel: scsi 2:0:0:0: Direct-Access     ATA      WDC WDS240G2G0B- 0400 PQ: 0 ANSI: 5
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/224 GiB)
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] Write Protect is off
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 09 11:00:18 lab kernel:  sdb: sdb1 sdb2 sdb3
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
Jun 09 11:00:18 lab kernel: ata2.00: READ LOG DMA EXT failed, trying PIO
Jun 09 11:00:18 lab kernel: ata2.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
Jun 09 11:00:18 lab kernel: ata2.00: irq_stat 0x40000008
Jun 09 11:00:18 lab kernel: ata2.00: failed command: READ FPDMA QUEUED
Jun 09 11:00:18 lab kernel: ata2.00: cmd 60/f8:10:08:0a:00/01:00:00:00:00/40 tag 2 ncq dma 258048 in
                                     res 41/40:00:b8:0b:00/00:00:00:00:00/00 Emask 0x409 (media error) <F>
Jun 09 11:00:18 lab kernel: ata2.00: status: { DRDY ERR }
Jun 09 11:00:18 lab kernel: ata2.00: error: { UNC }
Jun 09 11:00:18 lab kernel: ata2.00: configured for UDMA/133
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] tag#2 Sense Key : Medium Error [current]
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] tag#2 Add. Sense: Unrecovered read error - auto reallocate failed
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] tag#2 CDB: Read(10) 28 00 00 00 0a 08 00 01 f8 00
Jun 09 11:00:18 lab kernel: blk_update_request: I/O error, dev sdb, sector 3000 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
Jun 09 11:00:18 lab kernel: ata2: EH complete


quite a few of those errors:

un 09 11:00:18 lab kernel: scsi 2:0:0:0: Direct-Access     ATA      WDC WDS240G2G0B- 0400 PQ: 0 ANSI: 5
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/224 GiB)
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] Write Protect is off
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 09 11:00:18 lab kernel:  sdb: sdb1 sdb2 sdb3
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
Jun 09 11:00:18 lab kernel: ata2.00: READ LOG DMA EXT failed, trying PIO
Jun 09 11:00:18 lab kernel: ata2.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
Jun 09 11:00:18 lab kernel: ata2.00: irq_stat 0x40000008
Jun 09 11:00:18 lab kernel: ata2.00: failed command: READ FPDMA QUEUED
Jun 09 11:00:18 lab kernel: ata2.00: cmd 60/f8:10:08:0a:00/01:00:00:00:00/40 tag 2 ncq dma 258048 in
                                     res 41/40:00:b8:0b:00/00:00:00:00:00/00 Emask 0x409 (media error) <F>
Jun 09 11:00:18 lab kernel: ata2.00: status: { DRDY ERR }
Jun 09 11:00:18 lab kernel: ata2.00: error: { UNC }
Jun 09 11:00:18 lab kernel: ata2.00: configured for UDMA/133
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] tag#2 Sense Key : Medium Error [current]
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] tag#2 Add. Sense: Unrecovered read error - auto reallocate failed
Jun 09 11:00:18 lab kernel: sd 2:0:0:0: [sdb] tag#2 CDB: Read(10) 28 00 00 00 0a 08 00 01 f8 00
Jun 09 11:00:18 lab kernel: blk_update_request: I/O error, dev sdb, sector 3000 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
Jun 09 11:00:18 lab kernel: ata2: EH complete

dpkg --configure -a did nothing

removing spiceterm warned me that to remove it I needed to remove proxmox-ve



I think a reinstall may be needed
 
Thanks for providing part of the log.
Indeed a reinstall could be done, however these errors are concerning and probably this will generate issues after reinstalling.
It could be faulty sata cables. Sometimes disconnecting them and reinserting will help.
Best is also to check smart status of all your drives:
smartctl -a /dev/sdx
 
The test does seem to indicate the drive is fine by the looks of it.

Code:
root@lab:~# smartctl -a /dev/sdb
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.3.18-2-pve] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     WD Blue and Green SSDs
Device Model:     WDC WDS240G2G0B-00EPW0
Serial Number:    19438D805074
LU WWN Device Id: 5 001b44 8b189af16
Firmware Version: UJ220400
User Capacity:    240,057,409,536 bytes [240 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      M.2
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3, ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Jun  9 14:41:39 2021 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  120) seconds.
Offline data collection
capabilities:                    (0x11) SMART execute Offline immediate.
                                        No Auto Offline data collection support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        No Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        (  41) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0032   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       645
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       24
165 Block_Erase_Count       0x0032   100   100   000    Old_age   Always       -       582
166 Minimum_PE_Cycles_TLC   0x0032   100   100   ---    Old_age   Always       -       2
167 Max_Bad_Blocks_per_Die  0x0032   100   100   ---    Old_age   Always       -       10
168 Maximum_PE_Cycles_TLC   0x0032   100   100   ---    Old_age   Always       -       5
169 Total_Bad_Blocks        0x0032   100   100   ---    Old_age   Always       -       113
170 Grown_Bad_Blocks        0x0032   100   100   ---    Old_age   Always       -       0
171 Program_Fail_Count      0x0032   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       0
173 Average_PE_Cycles_TLC   0x0032   100   100   000    Old_age   Always       -       2
174 Unexpected_Power_Loss   0x0032   100   100   000    Old_age   Always       -       16
184 End-to-End_Error        0x0032   100   100   ---    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       1566
188 Command_Timeout         0x0032   100   100   ---    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   074   038   000    Old_age   Always       -       26 (Min/Max 13/38)
199 UDMA_CRC_Error_Count    0x0032   100   100   ---    Old_age   Always       -       0
230 Media_Wearout_Indicator 0x0032   100   100   000    Old_age   Always       -       0x014200280142
232 Available_Reservd_Space 0x0033   100   100   005    Pre-fail  Always       -       100
233 NAND_GB_Written_TLC     0x0032   100   100   ---    Old_age   Always       -       558
234 NAND_GB_Written_SLC     0x0032   100   100   000    Old_age   Always       -       4646
241 Host_Writes_GiB         0x0030   100   100   000    Old_age   Offline      -       1306
242 Host_Reads_GiB          0x0030   100   100   000    Old_age   Offline      -       4334
244 Temp_Throttle_Status    0x0032   000   100   ---    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

The only part looking suspect is in bold.
 
Ah, I forgot to check your drive type and see that it's a m.2 :oops:, so no sata cable, could still be dust in between contacts, so perhaps cleaning and reseating it could be one step (this often works for RAM modules). However, personally I don't really have experience with these kind of drives.
The overall health check passed, and I can't see real issues in the smart stats, so seems fine to me too.
Perhaps you could check for a mainboard bios update.
And perhaps your bios features onboard raid functionality that somehow interferes. (if using zfs it's always wise to connect to non-raid ports, zfs wants direct access)
Maybe another forum member with hands-on experience with these kind of drive could give a helping hand.
 

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!