Search results

ds-1 and ds-2 on a root disc ds-2 and ds-3 on zfs datasets proxmox-backup-manager version --verbose proxmox-backup unknown running kernel: 6.2.11-2-pve proxmox-backup-server 2.4.2-1 running version: 2.4.2 ifupdown2 3.1.0-1+pmx4...

zugehörige Ticket: https://bugzilla.proxmox.com/show_bug.cgi?id=4728 und kommende Änderung in proxmox-sys 0.5.0-1 https://git.proxmox.com/?p=proxmox.git;a=commit;h=ce389914ff79bc99b054c23ae4ca3a487fefe950

If your BIOS is not up to date, try updating it. I had the same problem with Asrock Rack W480D4U motherboard + Intel i7-10700 CPU, after BIOS update the problem is gone.

you can check with systool: apt install sysfsutils systool -c scsi_host -v -d host0 if you have active_mode = "Initiator" and supported_mode = "Initiator" (Initiator Target -> IT) your Controller is in IT-mode. by the way, your log already shows: May 01 13:38:02 Enterprise kernel: mpt2sas_cm0...

Try with following "global_filter": global_filter = [ "r|/dev/zd.*|", "r|/dev/mapper/pve-.*|", "r|/dev/mapper/.*-(vm|base)--[0-9]+--disk--[0-9]+|", "r|/dev/sda|", "r|/dev/sdb|", "r|/dev/sdc|" ] Close the Proxmox GUI in Browser, this can wake up the disks!

Try without "apm". for example:

Es funktioniert bei mir leider nicht.

Ich habe das gleiche Problem mit i7-10700 (Host friert, ohne Log Eintrag, keine Kernel-Panik). Ich habe jetzt Hyper-Threading im Bios ausgeschaltet, mal sehen ob es hilft.

Mit Proxmox 7.3 / Kernel 5.15 schon probiert?

bei mir funktioniert nur mit VirtIO Version 0.1.208: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.208-1/virtio-win-0.1.208.iso

set/check containter features: Nesting: true FUSE: true check docker storage driver: docker info | grep Storage Storage Driver: fuse-overlayfs

make it executable: chmod +x /usr/local/bin/fuse-overlayfs

please check with "ls -la"

you don't need execute that file, docker auto-detect that and use it.

Download the "fuse-overlayfs-x86_64" file, move to "/usr/local/bin/fuse-overlayfs" and make it executable.

Google Translator: I think their "product" will not take off. Everyone will understand why, well, except for those who want to stay on a normal platform but at the same time comply with the law. As it appeared, so it will die.

Have you tried with pve-kernel-5.13?

ja, genau

mit "systemctl suspend" über ssh zb.: ssh root@pbs -i ~/.ssh/id_rsa_pbs 'systemctl suspend'

mit pve-manager 7.1-11 und "job-init" Hook funktioniert: vzdump-hook-script: #!/bin/bash if [ "$1" == "job-init" ]; then etherwake XX:YY:ZZ:XX:YY:ZZ ping -W 20 -c 1 pbs-test.lan /usr/sbin/pvesm set pbs-test -disable false fi exit 0