pve-manager error on upgrade

[Kyle Menigoz]

I've recently updated from 6.x to 7.2. During that process, everything appeared to complete (and the server is online) but I get these errors from

apt dist-upgrade

and after hours of searching, I've not found anything related or helpful:

grep: /etc/lvm/lvm.conf: No such file or directory
Backing up lvm.conf before setting pve-manager specific settings..
cp: cannot stat '/etc/lvm/lvm.conf': No such file or directory
dpkg: error processing package pve-manager (--configure):
 installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

pveversion -v

proxmox-ve: not correctly installed (running kernel: 5.15.64-1-pve)
pve-manager: not correctly installed (running version: 7.2-11/b76d3178)
pve-kernel-5.15: 7.2-13
pve-kernel-helper: 7.2-13
pve-kernel-5.4: 6.4-20
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.4.203-1-pve: 5.4.203-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+pve2
ifupdown2: residual config
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-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-3
libpve-guest-common-perl: 4.1-4
libpve-http-server-perl: 4.1-4
libpve-storage-perl: 7.2-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

 

[Moayad]

Hello,

Have you followed our wiki guide about the upgrade from Proxmox VE 6.x to Proxmox VE 7.x [0]?
Can you please provide us with the output of the following commands:

grep '' /etc/apt/sources.list.d/*
grep '' /etc/apt/sources.list
apt update

proxmox-ve: not correctly installed (running kernel: 5.15.64-1-pve) pve-manager: not correctly installed (running version: 7.2-11/b76d3178)

From the output of `pveversion -v` provided, the prefix message says 'not correctly installed` did you see any error during the upgrade process?

I would try reinstalling the following packages, but first let us see the output of the above commands:

apt install proxmox-ve --reinstall
apt install pve-manager --reinstall

[0] https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

 

[Kyle Menigoz]

Have you followed our wiki guide about the upgrade from Proxmox VE 6.x to Proxmox VE 7.x [0]?
Can you please provide us with the output of the following commands:

I followed the guide exactly.

grep '' /etc/apt/sources.list.d/*

deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

grep '' /etc/apt/sources.list

deb http://debian.mirrors.ovh.net/debian/ bullseye main
deb-src http://debian.mirrors.ovh.net/debian/ bullseye main

deb http://security.debian.org/debian-security bullseye-security main
deb-src http://security.debian.org/debian-security bullseye-security main

# bullseye-updates, previously known as 'volatile'
deb http://debian.mirrors.ovh.net/debian/ bullseye-updates main
deb-src http://debian.mirrors.ovh.net/debian/ bullseye-updates main

apt update

Get:1 http://debian.mirrors.ovh.net/debian bullseye InRelease [116 kB]
Get:2 http://debian.mirrors.ovh.net/debian bullseye-updates InRelease [44.1 kB]
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease
Fetched 160 kB in 1s (140 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

From the output of `pveversion -v` provided, the prefix message says 'not correctly installed` did you see any error during the upgrade process?

I posted these in the first post, they come from the upgrade process and are repeatable, any time I run apt dist-upgrade:

grep: /etc/lvm/lvm.conf: No such file or directory
Backing up lvm.conf before setting pve-manager specific settings..
cp: cannot stat '/etc/lvm/lvm.conf': No such file or directory
dpkg: error processing package pve-manager (--configure):
 installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

apt install proxmox-ve --reinstall
apt install pve-manager --reinstall

apt install proxmox-ve --reinstall

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for proxmox-ve:amd64

and

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for pve-manager:amd64

 

[fiona]

Hi,
please check if the lvm2 package is correctly installed/reinstall it. That one should include the /etc/lvm/lvm.conf file.

 

[fabian]

since you or some script removed it and Debian tracks changes/removals for config files like this, you also have to pass -o Dpkg::Options::="--force-confmiss" to apt (it tells it to re-install config files which have previously been removed).

 

[Kyle Menigoz]

Tried reinstalling lvm, it appeared to run successfully, but now I get

apt install pve-manager --reinstall
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for pve-manager:amd64

And same errors for the other four that show currently.

Also this might help, but I'm moderately lost in config files ATM:

apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up ifupdown2 (3.1.0-1+pmx3) ...
bridge 'vmbr1' - unable to find bridge port 'dummy0'
Reloading network config on first install
error: vmbr1: bridge port dummy0 does not exist
dpkg: error processing package ifupdown2 (--configure):
 installed ifupdown2 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of ifenslave:
 ifenslave depends on ifupdown; however:
  Package ifupdown is not installed.
  Package ifupdown2 which provides ifupdown is not configured yet.

dpkg: error processing package ifenslave (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
 pve-manager depends on ifupdown2 (>= 2.0.1-1+pve8) | ifenslave (>= 2.6); however:
  Package ifupdown2 is not configured yet.
  Package ifenslave is not configured yet.

dpkg: error processing package pve-manager (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 ifupdown2
 ifenslave
 pve-manager
 proxmox-ve

 

[fiona]

Also this might help, but I'm moderately lost in config files ATM:

apt upgrade

Please always use apt dist-upgrade when updating Proxmox VE! Not likely the cause of the problem in this case, but using apt upgrade can lead to problems.

Setting up ifupdown2 (3.1.0-1+pmx3) ...
bridge 'vmbr1' - unable to find bridge port 'dummy0'

How does /etc/network/interfaces look like? If a bridge doesn't have a real port, you can use bridge-ports none.

 

[Kyle Menigoz]

I've used `apt dist-upgrade` for everything in the guide and every attempt otherwise minus a few to just get the error messages. The errors originated from `apt dist-upgrade`

Edit because I missed part of the file:
I don't believe I use vmbr1 for anything, am I safe to just remove it?

# The loopback network interface
auto lo
iface lo inet loopback

# for Routing
auto vmbr1
iface vmbr1 inet manual
        bridge_ports dummy0
        bridge_stp off
        bridge_fd 0

auto vmbr0
iface vmbr0 inet static
        address *redacted*
        netmask 255.255.255.0
        network *redacted*
        broadcast *redacted*
        gateway *redacted*
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
        hwaddress *redacted*

iface vmbr0 inet6 static
        address *redacted*
        netmask 64
        post-up /sbin/ip -f inet6 route add *redacted* dev vmbr0
        post-up /sbin/ip -f inet6 route add default via *redacted*
        pre-down /sbin/ip -f inet6 route del default via *redacted*
        pre-down /sbin/ip -f inet6 route del *redacted* dev vmbr0

But also, I'm on OVH, so IPv6 support doesn't work properly, I never configured the IPv6 section.

 

[Kyle Menigoz]

Updated the /etc/network/interfaces file and that allowed ifupdown2 to configure. Here's the output of `apt dist-upgrade` again:

 apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  linux-libc-dev
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
Need to get 0 B/1,551 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 56447 files and directories currently installed.)
Preparing to unpack .../linux-libc-dev_5.10.149-2_amd64.deb ...
Unpacking linux-libc-dev:amd64 (5.10.149-2) over (5.10.149-1) ...
Setting up linux-libc-dev:amd64 (5.10.149-2) ...
Setting up ifupdown2 (3.1.0-1+pmx3) ...

network config changes have been detected for ifupdown2 compatibility.
Saved in /etc/network/interfaces.new for hot-apply or next reboot.

Reloading network config on first install
Setting up ifenslave (2.13~deb11u1) ...
Setting up pve-manager (7.2-11) ...
machine-id check OK
grep: /etc/lvm/lvm.conf: No such file or directory
Backing up lvm.conf before setting pve-manager specific settings..
cp: cannot stat '/etc/lvm/lvm.conf': No such file or directory
dpkg: error processing package pve-manager (--configure):
 installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pve-manager
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Earlier I was told to try reinstalling lvm2, so tried that again. It processes correctly and repeats the same errors as above.

These are the contents of my /etc/lvm folder:

archive  backup  lvm.conf.dpkg-dist  lvmlocal.conf  profile

 

[Kyle Menigoz]

I compared the lvm.conf.dpkg-dist file to an lvm.conf I found in another file posted in the forums that was confirmed to be identical by a Proxmox staff member and mv'ed it to lvm.conf (made a backup copy first) and that allowed the apt dist-upgrade to properly configure the packages. All appears to be good now!

 

[PatRiot]

I get a similar error. But I am already at version 7.x. Preparing for v 8.

root@pve:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  pve-kernel-5.15.143-1-pve pve-kernel-5.15.85-1-pve
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up proxmox-backup-file-restore (2.4.7-1) ...
Updating file-restore initramfs...
cp: error reading '/usr/lib/x86_64-linux-gnu/proxmox-backup/file-restore/initramfs.img': Input/output error
dpkg: error processing package proxmox-backup-file-restore (--configure):
 installed proxmox-backup-file-restore package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of libpve-storage-perl:
 libpve-storage-perl depends on proxmox-backup-file-restore; however:
  Package proxmox-backup-file-restore is not configured yet.

dpkg: error processing package libpve-storage-perl (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
 pve-container depends on libpve-storage-perl (>= 7.2-10); however:
  Package libpve-storage-perl is not configured yet.

dpkg: error processing package pve-container (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
 pve-manager depends on libpve-storage-perl (>= 7.2-12); however:
  Package libpve-storage-perl is not configured yet.
 pve-manager depends on pve-container (>= 4.0-9); however:
  Package pve-container is not configured yet.

dpkg: error processing package pve-manager (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
 qemu-server depends on libpve-storage-perl (>= 7.2-10); however:
  Package libpve-storage-perl is not configured yet.

dpkg: error processing package qemu-server (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.
 proxmox-ve depends on qemu-server; however:
  Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpve-guest-common-perl:
 libpve-guest-common-perl depends on libpve-storage-perl (>= 7.0-14); however:
  Package libpve-storage-perl is not configured yet.

dpkg: error processing package libpve-guest-common-perl (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
 pve-ha-manager depends on pve-container; however:
  Package pve-container is not configured yet.
 pve-ha-manager depends on qemu-server (>= 6.0-15); however:
  Package qemu-server is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-backup-file-restore
 libpve-storage-perl
 pve-container
 pve-manager
 qemu-server
 proxmox-ve
 libpve-guest-common-perl
 pve-ha-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

Should I delete the two things: pve-kernel-5.15.143-1-pve pve-kernel-5.15.85-1-pve ?

What can I do? I don't have a file called lvm.conf.dpkg-dist.


I did a:

root@pve:~# pve7to8 --full
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =

Checking for package updates..
PASS: all packages up-to-date

Checking proxmox-ve package version..
PASS: proxmox-ve package has version >= 7.4-1

Checking running kernel version..
PASS: running kernel '5.15.158-1-pve' is considered suitable for upgrade.

= CHECKING CLUSTER HEALTH/SETTINGS =

SKIP: standalone node.

= CHECKING HYPER-CONVERGED CEPH STATUS =

SKIP: no hyper-converged ceph setup detected!

= CHECKING CONFIGURED STORAGES =

PASS: storage 'local' enabled and active.
PASS: storage 'local-lvm' enabled and active.
INFO: Checking storage content type configuration..
PASS: no storage content problems found
PASS: no storage re-uses a directory for multiple content types.

= MISCELLANEOUS CHECKS =

INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvescheduler.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for supported & active NTP service..
PASS: Detected active time synchronisation unit 'chrony.service'
INFO: Checking for running guests..
WARN: 5 running guest(s) detected - consider migrating or stopping them.
INFO: Checking if the local node's hostname 'pve' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '192.168.178.4' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 >= 2048)
INFO: Checking backup retention settings..
PASS: no backup retention problems found.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking permission system changes..
INFO: Checking custom role IDs for clashes with new 'PVE' namespace..
PASS: no custom roles defined, so no clash with 'PVE' role ID namespace enforced in Proxmox VE 8
INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded..
SKIP: not yet upgraded, no need to check the FUSE library version LXCFS uses
INFO: Checking node and guest description/note length..
PASS: All node config descriptions fit in the new limit of 64 KiB
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking if the suite for the Debian security repository is correct..
PASS: found no suite mismatch
INFO: Checking for existence of NVIDIA vGPU Manager..
PASS: No NVIDIA vGPU Service found.
INFO: Checking bootloader configuration...
WARN: System booted in uefi mode but grub-efi-amd64 meta-package not installed, new grub versions will not be installed to /boot/efi! Install grub-efi-amd64.
INFO: Check for dkms modules...
SKIP: could not get dkms status

= SUMMARY =

TOTAL:    29
PASSED:   23
SKIPPED:  4
WARNINGS: 2
FAILURES: 0

ATTENTION: Please check the output for detailed information!

Can I upgrade to 8 with this or is it too risky?

 

[fabian]

that is a totally different error:

cp: error reading '/usr/lib/x86_64-linux-gnu/proxmox-backup/file-restore/initramfs.img': Input/output error

this file should exist on disk and be readable, if it is not, it sounds like your disk might have an issue..

 

[PatRiot]

that is a totally different error:

cp: error reading '/usr/lib/x86_64-linux-gnu/proxmox-backup/file-restore/initramfs.img': Input/output error

this file should exist on disk and be readable, if it is not, it sounds like your disk might have an issue..

smartmontools says everything is fine, doesn't it?

root@pve:~# smartctl -a /dev/nvme0
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.158-1-pve] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 980 PRO 1TB
Serial Number:                      S5GXNF1R820884N
Firmware Version:                   3B2QGXA7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      6
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Utilization:            651,950,678,016 [651 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 b811c0b73e
Local Time is:                      Fri Oct 11 18:06:57 2024 CEST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.49W       -        -    0  0  0  0        0       0
 1 +     4.48W       -        -    1  1  1  1        0     200
 2 +     3.18W       -        -    2  2  2  2        0    1000
 3 -   0.0400W       -        -    3  3  3  3     2000    1200
 4 -   0.0050W       -        -    4  4  4  4      500    9500

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

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

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        31 Celsius
Available Spare:                    97%
Available Spare Threshold:          10%
Percentage Used:                    14%
Data Units Read:                    12,792,568 [6.54 TB]
Data Units Written:                 15,856,121 [8.11 TB]
Host Read Commands:                 87,348,928
Host Write Commands:                1,048,676,821
Controller Busy Time:               30,146
Power Cycles:                       65
Power On Hours:                     5,293
Unsafe Shutdowns:                   15
Media and Data Integrity Errors:    450
Error Information Log Entries:      450
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               31 Celsius
Temperature Sensor 2:               32 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0        450     2  0xf092  0xc502  0x000    715715256     1     -
  1        449     5  0xa17a  0xc502  0x000    715715256     1     -
  2        448     2  0xd08d  0xc502  0x000    715715256     1     -
  3        447     7  0xd2b8  0xc502  0x000    715715256     1     -
  4        446     2  0xd0b2  0xc502  0x000    715715256     1     -
  5        445     5  0xe158  0xc502  0x000    715715256     1     -
  6        444     5  0x3152  0xc502  0x000    715715256     1     -
  7        443     6  0x413e  0xc502  0x000    715715256     1     -
  8        442     5  0x6175  0xc502  0x000    715715256     1     -
  9        441     7  0x328f  0xc502  0x000    715715256     1     -
 10        440     3  0x63dd  0xc502  0x000    715715256     1     -
 11        439     7  0x228a  0xc502  0x000    715715256     1     -
 12        438     7  0x52a7  0xc502  0x000    715715256     1     -
 13        437     1  0x2252  0xc502  0x000     19219080     1     -
 14        436     1  0x2251  0xc502  0x000     19219080     1     -
 15        435     1  0x224f  0xc502  0x000     19219080     1     -
... (48 entries not read)

I tried to backup a VM, which quits with an error when I don't exclude the second disk (data-disk, it's openmediavault):

[...]
INFO:   4% (18.1 GiB of 400.0 GiB) in 48s, read: 307.4 MiB/s, write: 286.0 MiB/s
ERROR: job failed with err -61 - No data available
INFO: aborting backup job
INFO: stopping kvm after backup task
ERROR: Backup of VM 102 failed - job failed with err -61 - No data available
INFO: Failed at 2024-10-11 18:56:06
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[fabian]

Media and Data Integrity Errors:    450

that is not good and possibly the source of your issues.. you might want to run some more in-deph tests and consider RMAing it if it's still covered..

 

[PatRiot]

Media and Data Integrity Errors:    450

that is not good and possibly the source of your issues.. you might want to run some more in-deph tests and consider RMAing it if it's still covered..

which kind of test can you recommend to me please?

Is

smartctl --test=long /dev/sda

enough?

Maybe I got these errors because I always updated proxmox without shutting down the LXCs and VMs? Hm.

 

[fabian]

no, that is a clear indicator for hardware errors. yes, a smart long test might be a good idea. or simply reading the disk form end to end and checking if the counter goes up..