Good day support staff and community,
We have stumbled into some backup failure issues while using the latest version of Proxmox (7) in conjunction with ZFS.
My hardware configuration is the following:
Server Brand and model: Dell R630
Storage controller PERC H730 in HBA mode and cache disabled
Storage configuration: RAIDZ-1 of 5 Crucial MX500 1TB SSD drives
I have used those SSD drives on other machines and they have always worked flawlessly.
We have already ran some benchmarks on this server but performance-wise everything seems to be in perfect working order.
This is the first time I am using this specific server-controller combo as i have always used the H310 mini mono flashed with the LSI Firmware in IT mode.
We have noticed a “systemd timout error” message popping out sometimes when the backups fail. Unfortunately, after a thorough log
analysys we have discovered that those timout errors seem to be unrelated to those failures.
This problem is becoming a frequent occurence and we are quite concerned about it.
We are currently evaluating a temporary full hardware replacement with a machine with which we have more experience.
Are you aware if this kind of issue is only present in the latest proxmox version (7)?
Do you have any knowledge of it happening in the previous versions as well.
Furthermore i’d like to know if by using the enterprise repositories I may not incur in such trouble and which version of proxmox you suggest us to use.
Thank you for your time and I am looking forward to hearing from you guys.
attached log files
We have stumbled into some backup failure issues while using the latest version of Proxmox (7) in conjunction with ZFS.
My hardware configuration is the following:
Server Brand and model: Dell R630
Storage controller PERC H730 in HBA mode and cache disabled
Storage configuration: RAIDZ-1 of 5 Crucial MX500 1TB SSD drives
I have used those SSD drives on other machines and they have always worked flawlessly.
We have already ran some benchmarks on this server but performance-wise everything seems to be in perfect working order.
This is the first time I am using this specific server-controller combo as i have always used the H310 mini mono flashed with the LSI Firmware in IT mode.
We have noticed a “systemd timout error” message popping out sometimes when the backups fail. Unfortunately, after a thorough log
analysys we have discovered that those timout errors seem to be unrelated to those failures.
This problem is becoming a frequent occurence and we are quite concerned about it.
We are currently evaluating a temporary full hardware replacement with a machine with which we have more experience.
Are you aware if this kind of issue is only present in the latest proxmox version (7)?
Do you have any knowledge of it happening in the previous versions as well.
Furthermore i’d like to know if by using the enterprise repositories I may not incur in such trouble and which version of proxmox you suggest us to use.
Thank you for your time and I am looking forward to hearing from you guys.
proxmox-ve: 7.0-2 (running kernel:
5.11.22-5-pve)
pve-manager: 7.0-13 (running version:
7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11:
7.0-8
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-3-pve: 5.11.22-7
pve-kernel-5.11.22-1-pve:
5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.5-pve1
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.22-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control:
7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl:
7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl:
7.0-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve:
1.2.0-3
proxmox-backup-client:
2.0.11-1
proxmox-backup-file-restore:
2.0.11-1
proxmox-mini-journalreader:
1.2-1
proxmox-widget-toolkit:
3.3-6
pve-cluster:
7.0-3
pve-container:
4.0-10
pve-docs:
7.0-5
pve-edk2-firmware:
3.20210831-1
pve-firewall:
4.2-3
pve-firmware:
3.3-2
pve-ha-manager:
3.3-1
pve-i18n:
2.5-1
pve-qemu-kvm:
6.0.0-4
pve-xtermjs:
4.12.0-1
qemu-server:
7.0-16
smartmontools:
7.2-1
spiceterm:
3.2-2
vncterm:
1.7-1
zfsutils-linux:
2.0.5-pve1
5.11.22-5-pve)
pve-manager: 7.0-13 (running version:
7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11:
7.0-8
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-3-pve: 5.11.22-7
pve-kernel-5.11.22-1-pve:
5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.5-pve1
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.22-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control:
7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl:
7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl:
7.0-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve:
1.2.0-3
proxmox-backup-client:
2.0.11-1
proxmox-backup-file-restore:
2.0.11-1
proxmox-mini-journalreader:
1.2-1
proxmox-widget-toolkit:
3.3-6
pve-cluster:
7.0-3
pve-container:
4.0-10
pve-docs:
7.0-5
pve-edk2-firmware:
3.20210831-1
pve-firewall:
4.2-3
pve-firmware:
3.3-2
pve-ha-manager:
3.3-1
pve-i18n:
2.5-1
pve-qemu-kvm:
6.0.0-4
pve-xtermjs:
4.12.0-1
qemu-server:
7.0-16
smartmontools:
7.2-1
spiceterm:
3.2-2
vncterm:
1.7-1
zfsutils-linux:
2.0.5-pve1
attached log files