Search results

It sounds a problem with the underlaying disks of storage. Have you tried a SMART check on disks?

You need to add only a cluster, and then all the nodes of the cluster appear. If you add each node of the cluster to PDM you may have duplicated (or x 3or x5 depending on the number of nodes) VM in PDM

The zones are logically separated; you must install a device (router) that allows communication between zones.

Which version of Proxmox do you have at the destination? It will be a problem with the versión of Proxmox at the destination cluster, because live migration is only supported on latest PVE 8 versions

It appears to be a problem with the UEFI. Try to update UEFI BIOS settings and PCI devices (PCI0.GPP1)

Have you any information on dmesg or journalctl?, it will be a hardware failure, due to ram (memtest is your friend) or even power supply failure not serving the necessary voltage/current to the equipment.

You may setup another PBS instance in a remote location and made a sync Job between the two pbs. https://pbs.proxmox.com/docs/managing-remotes.html After this You can setup another pbs storage for the remote pbs

You can try to use the NFS as a removable storage in PBS, if the PBS host dies, you can create a new one, and add the storage again as a removable existent media. If you use this trick you can access again to your backups.

Then try to check why is not booting, check dmesg and journalctl. Have you updated the kernel?, if so, try to go back to a older kernel version

Yo have already checked the original disk? qemu-img check -f vmdk /path-to-original-vmdk

You can try to boot with a live debian image, and do a copy of the disks in the lvm volume to a external usb or via rsync to a new machine. To find the disks you can use: pvesm list local-lvm Then for example: qemu-img convert -O qcow2 /dev/local-lvm/vm-100-disk-0 /mnt/usb01/vm-100-disk-0.qcow2

I dont test this solution, but you can read this post, may help you https://forum.proxmox.com/threads/api-returns-500-but-no-logs.93425/

pvedaemon start --debug 1? pvedaemon start [OPTIONS] Start the daemon. --debug <boolean> (default =0) Debug mode - stay in foreground

Hi, you can find the API HTTP access log at /var/log/pmgproxy/pmgproxy.log

Try to use BTRFS instead of SW raid for the boot, i use this option with NVME boot disks

First you need to check the performance of your storage, yo can test it with fio command https://pve.proxmox.com/wiki/Benchmarking_Storage Also you can try pveperf For example pveperf /var/lib/vz

Is not a good idea making backups in different datastores as you miss the dirty bit, so every time you do a backup weekly or monthly is a new copy not incremental.

The existing storage network is not affected. You only need to add a network that can communicate with your PBS, and when you add /modify the PBS storage it will try to reach the PBS by the new IP address.

There are some several escenarios for your approach: 1) You can use a firewall like Pfsense/Opnsense to connect it directly to your wan connection of any way (ppoE, DHCP, etc) for this you need to know what is the method for doing this. After that, you have a Virtual Machine (VM) with 2...

This is a known issue after upgrade due changes made to systemd defaults. As shown in this section of the upgrade process, audit logging is disabled by default in Bookworm, and in Trixie this audit log is enabled. systemctl disable --now systemd-journald-audit.socket...