Eventuell ist hier Proxmox VE ein bisschen Overkill.
Fuer die Heimanwendung empfehle ich Dir eine Debian-Installation auf dem "ThinClient" und dort alles mittels Docker Containern laufen lassen.
HomeAssistant, zigbee2mqtt, Paperless-NGX...
Possible, but that would make it a RAID0 (a single stripe in ZFS terms) and you might lose all data when one of the drives fails. This can also be done with LVM and BTRFS.
Anyway, be careful as you double your chances to lose data from a drive...
For the record, the guide on the wiki[0] is a great resource on how to upgrade from PVE 8 to 9 and lists a number of possible issues that may be encountered in the process.
This specific error is documented in the Troubleshooting section.
[0]...
so update.....wiped the datastore for backup (essentially started over again) and it ran great for about 2 weeks and now I am at the point again that the drive is full and I am unable to perform a garbage collection WTF am I doing wrong.
I have...
I tested kernel-7.0.14-22_bnxt-test1, in my case, the problem is gone, there are no issues in the logs regarding the bnxt_en driver, and the network is working.
Just Install it without the dkms module - it won't support freezing filesystems then, but that is not really relevant, you only really need the pve configs.
Install a veeam worker to backup your vms.
I would recommend 13.1, it got a lot of fixes...
To clarify: The patches mentioned by @fabian fix an issue where restores from PBS/VMA to ZFS can cause increased IO latencies on other ZFS-backed VMs during page writeback. The patches are included in pve-qemu-kvm 11.0.3-3 and qemu-server 9.2.7...
I tested kernel-7.0.14-22_bnxt-test1, in my case, the problem is gone, there are no issues in the logs regarding the bnxt_en driver, and the network is working.
Ok, so I found that running the following command:
ceph mon set auth_preferred_cipher aes256k
and then running:
root@pve01:~# /usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys --apply --confirm-all-clients-refreshed...
the proposed kernel (and checksums of the package files) are available here: http://download.proxmox.com/temp/kernel-7.0.14-22_bnxt-test1/
the proposed fix is here...
Hello,
With Proxmox 8 we had installed Veeam Agent for Linux on each hypervisors to have a backup of the system disks.
But it is no more possible with Proxmox 9.2.
Veeam Agent for Linux install a kernel module via DKMS, but it is not compatible...
hi, please check if this happens with latest upstream firefox and report it there, since a 'normal' webpage shouldn't be able to crash the whole browser...
Guest VM (i.e. Windows Server 2022 with VirtIO driver and QEMU agent installed ver. 0.1.271)
looses performance migrating from old CPU type (hstp-pve01 and hst-pve02) to "less older" CPU type
(hst-pve04, hst-pve05, hst-pve06).
For example...