Search results

Hi @bbgeek17, Thanks for your patience. Please find attached the io performance between host and guest. As there is no package ssacli found on proxmox repository. I've captured RAID controller infomation from iLo Thank you

Hi, The user can’t see backups because permissions also need to be set on the PBS datastore itself, not just in PVE. Once you add Datastore on the PBS side, the backups will show up.

Hi @bbgeek17 1. So the disk was hosted locally? Yes on local-lvm. I.e. on local-lvm. It is still hosted locally based on the configuration attached to the opening post.? yes 2. It was moved to NFS share, but the configuration you provided does not show this. It still shows disk on "local-lvm2"...

Hi, Could someone kindly provide an update on the resolution of this issue? Looking forward to your response. Thank you.

Could you please check the logs to see why it’s timing out: journalctl -u pmgproxy -f grep 'error' /var/log/pmg/pmgproxy/pmgproxy.log If the problem is too many connections, use NGINX in front of PMG to handle more traffic. Don’t try to change the built-in proxy. Only if nothing else works...

Hi, The error usually happens because some of the partitions in the backup aren’t designed to be read directly, so the file restore tool can’t mount them. That’s why you’re able to restore from certain folders but not others. If you need files from those areas, the best option is to restore...

Hi @bbgeek17, Could you please provide an update. Looking forward to your reply. Thank you.

@bbgeek17 Orignally vm 121 was on storage local-lvm at pve4. To trouble shoot the IO issue, I've created storage local-lvm2 on the same VG at pve4 to see if it can help (actually it can't). I've already moved the vm disk back to local-lvm. I am sorry for confusing you. HW raid model? HPE...

Your testy NFS storage is inactive because it’s missing a path. Fix it with: pvesm set testy --path /mnt/pve/testy Then check: pvesm status It should be active. When adding NFS storage via CLI, always include --path /mnt/pve/<name>

The issue is likely because the USB SSD hasn’t been added as a storage location in Proxmox yet. Once it’s mounted and added under Datacenter → Storage, your backups will appear in the GUI and be ready for restore.

Hi @bbgeek17 Below is added the result, could you please look into it and advise dir: local path /var/lib/vz content vztmpl,iso,backup lvmthin: local-lvm thinpool data vgname pve content rootdir,images nfs: iso export /export path /mnt/pve/iso server...

We have a Proxmox VE Essentials 1xCPU subscription and are experiencing a disk performance drop after migrating a VM’s virtual disk. Originally, the VM’s disk was on a local RAID SSD. We moved it to an NFS shared disk (15K RPM RAID array) hosted on an ESXi server over the network. After the...

Hi, The issue is likely that some backup files or large data were accidentally saved to the root disk (like /mnt) instead of the backup storage. This can happen if the datastore wasn't mounted properly during a backup. You can check what's using space with: du -h -d1 / | sort -hr | head -n 20...

Hi, Regarding the issue, please check the following: System resources: Make sure the Windows VM isn’t running low on RAM or disk I/O during the backup. QEMU Guest Agent: Try disabling it temporarily to see if that helps. Logs: Check the PBS and PVE backup logs for more details about when the...

Hi, Since you still have the .qcow2 and .raw disk files, you can likely recover the VMs. You can do this by: Creating a new VM in Proxmox (with similar specs). Deleting the new empty disk it creates. Moving or linking your old disk file (like vm-101-disk-0.qcow2) into the new VM's folder...

Hi, Since your backup is around 60GB and the VM disk is showing 18TB, the easiest way to fix this is: Restore from backup Since you made a backup after setting up a new Home Assistant VM: Just restore that 60GB backup onto the new VM you created. It will ignore the oversized disk and only use...

Hi, This issue happens when the Veeam worker VM gets stuck in the "starting" state, and Proxmox locks the VM config file. That’s why backups fail. Since restarting pvedaemon fixes it, it might be a stuck task or process. You can try: Run journalctl -u pvedaemon -n 100 to check logs. Check if...

Hi, The error means that your PBS user doesn’t have permission to delete old backups (prune), which is why the retention rules are not working. The DatastoreBackup role only allows making backups, not deleting them. To fix this, you can give the user the DatastorePowerUser role on the...

Hi, When the Proxmox Backup Server (PBS) backup runs, my Proxmox VE server becomes unresponsive. The web GUI and SSH stop working until the backup is finished. Is there any way to fix this? Anybody please assist on this to help resolve the issue. Thanks.

Hi Team, We are using Proxmox Mail Gateway (PMG). When emails bounce or fail to send, PMG sends a message from mailer-daemon@<hostname>. The problem is that this email address is not allowed by our SPF/DMARC settings, so other servers sometimes reject it. Is there a way to change the...