Search results

It seems your disk is starting to fail, since logs show Raw_Read_Error_Rate and Hardware_ECC_Recovered values are increasing. I would definitely replace the disk. Don't use apt-get upgrade. Use always apt dist-upgrade to avoid dependency problems.

Timestamp of last_sync and last_try is expressed in Unix time format [0] [1]. In your script, you could store the timestamp before you start the snapshot with schedule_now , and when the snapshot is done check if last_sync value is greater than the one you've stored. Checking fail_count would...

You can do it through scripting, using the API from the node itself (pvesh) https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/replication/{id} An option would be to launch the replication using schedule now and then check its status through status.

This may be what are you looking for, if you have Ceph on both sides: https://pve.proxmox.com/wiki/Ceph_RBD_Mirroring

Well, I see you have two disks, one for boot and another one to use with your VMs. You should recreate the one that you want to use with your VMs using a snapshot-compatible storage. 1. Backup (if needed) and delete all your VMs. 2. Delete local-windows storage from Datacenter -> Storage 3...

After the initial install, did you have either local-lvm or local-zfs, apart from local? It looks like one of the default storages was manually removed after install. Well, it depends on how many disks you have and how the filesystem looks like. The simplest way, if you can afford a rebuild...

Yes indeed, you can install Win11 without TPM using a custom ISO that bypasses the installer requirements (using Rufus), but it's unknown if it may lead to problems in the future.

When you install Proxmox VE, the installer creates two storages by default: local (Ext4 filesystem for isos, local backups...) local-lvm or local-zfs (depending on what you chose during the installation process. This cannot be changed without reinstalling, but you can always expand your...

Hi, It seems you're using file-based storage, which only supports snapshots with qcow2 disks [1]. The VM disk is in qcow2 format, EFI disk can be in qcow2 too, but AFAIK TPM disk is always in raw format, which is preventing you from taking snapshots [2][3]. If that's the case, the only...

I answer myself, one of the nodes wasn't unable to verify the authenticity of the other one. I followed this solution: https://forum.proxmox.com/threads/failed-setup-of-external-quorum.147515/ On first node: ssh-keyscan second_node_ip >> ~/.ssh/known_hosts I see more posts about the update...

Hi, No matter how I try, the SSH workaround does not work for me. PVE freshly installed from 8.2 ISO. I see pve-cluster 8.0.7 is not in the enterprise repos yet, is there any ETA? BTW, I tried to upgrade using pve-no-subcription (where pve-cluster 8.0.7 has been released) and it asks to...

Maybe you upgraded from 8.1 and added Qdevice after upgrading? Host keys behaviour changed with PVE 8.2. https://bugzilla.proxmox.com/show_bug.cgi?id=4886 https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.2

Hi! There's an upcoming patch: https://bugzilla.proxmox.com/show_bug.cgi?id=5461

Take into account that a slow backup destination can lead to VM corruption due to how backup is implemented in PVE[1][2]. There's an upcoming feature (backup fleecing) that will solve it, but it is still in development[3]. I'd advise against use nothing but local storage in PBS. If your...

Hi, You can find recommended requirements for OS drive here: https://pbs.proxmox.com/docs/installation.html#recommended-server-system-requirements The easiest way to go is to use two small mirrored drives for boot and two 1TB mirrored NVMe drives as a datastore. If you cannot use dedicated...

Hello, I'm testing a 3-node cluster with Ceph, and I noticed that when one node is down, the total size of the ceph storage in the GUI increases. Here's the config for each node: pve01 2 x 32GB Boot disks with ZFS mirror 2 x 50GB OSDs pve02 2 x 32GB Boot disks with ZFS mirror 2 x 50GB OSDs...

Update: The replication of VM 501 just finished. Here's the complete replication log. The snapshot creation starts exactly one hour after "freeze guest filesystem". Between 8:31 and 9:31 we stopped qemu-guest-agent and VSSVC.exe inside the VM. It randomly makes the replication continue, but...

Hi, In a cluster with several nodes replicating between them, we noticed that sometimes ZFS replication task gets stuck on Windows VMs when freezing guest filesystem. Agents are updated to the last version. Here's the replication log when the issue happens: 2024-02-08 13:50:01 321-2: start...

Hi, I write just to confirm the motherboard change also did the trick for us. Now everything works as expected. I hope this can help to someone else!

Thanks for your update. I agree that it may be a hardware fault, but it's very hard to replicate. I'm waiting for the motherboards replacement. Let's see how it goes. I've got also some nodes with GIGA MX33-BS1-V1, but for now I've had no problems with these.