powersupport's latest activity
-
powersupport replied to the thread Proxmox 8.4 and Veeam Backup issue while the VM is offline.Hi, This is expected in Proxmox. When a VM is shut down from the GUI, its disk is fully deactivated, so Veeam can’t see it. Using: qm stop 114 --keepactive works because it keeps the disk active even when the VM is off. a way to make... -
powersupport replied to the thread VM not booting up with LVM FC LUN storage.Hi, Anyone advice on this issue? Thank you
-
powersupport replied to the thread VM not booting up with LVM FC LUN storage.This is results @alexskysilk root@pVE-04:~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content backup,vztmpl,iso lvmthin: local-lvm thinpool data vgname pve content images,rootdir lvm: pVE-DataStore vgname PVE-DS01 content...
-
powersupport replied to the thread Caching drive replacement.This looks more like a cache path / mount issue than an S3 problem. When PBS marks an S3 datastore as “unavailable,” it’s usually because the local cache directory isn’t accessible or doesn’t match what PBS expects. Here are a few things to...
-
powersupport replied to the thread Failed backup - unable to activate storage.Hi, This looks like the NFS storage is temporarily disconnecting during backup. Since it happens on different nodes and VMs, it’s likely a network or NFS mount issue, not the VM itself. Please check NFS connectivity, server logs, and mount...
-
powersupport posted the thread VM not booting up with LVM FC LUN storage in Proxmox VE: Installation and configuration.We have set up a single-node Proxmox environment with storage backed by an FC LUN. Two storage types are configured on it: one as LVM and the other as directory storage. Recently, we attempted to migrate a VM from VMware to Proxmox. We tried...
-
powersupport replied to the thread Proxmox Backup Server 4.1.6 Random Hang Issue.This issue does not look like a CPU or RAM problem. The behavior you described (GUI freezing for 10–15 minutes and then recovering) is usually related to storage I/O delays. Since you have around 200 VMs, it’s possible that too many backups...
-
powersupport replied to the thread Error when backing up 1 out of 4 vms only.timesout.Hi, This usually happens when the server is a bit busy during the scheduled backup time. Since manual backups work fine, the issue is likely due to higher load when the automatic backups run. You can try running backups at a different time...
-
powersupport replied to the thread VM Fails to backup and job gets stuck.Hi, From the config, the VM is currently showing lock: backup, which suggests a previous backup task may be stuck. That alone can prevent new backups from progressing. Also, since the disk is QCOW2 on NFS and you’re using snapshot mode, it...
-
powersupport posted the thread Proxmox VE 8.4.x Offline Upgrade in Proxmox VE: Installation and configuration.Hi Team, I have a question regarding the Proxmox version upgrade. Currently, our Proxmox is running version 8.4.0, and we plan to upgrade it to the last version of 8.4.x.However, because our security department does not allow us to grant...
-
powersupport replied to the thread Move backups from disk to disk.Hi, You may want to check how your storage is configured first. In Proxmox, backups are usually stored as regular files (in the <span>dump/</span> directory), so there’s no direct GUI option to move them between storages. One approach you can...
-
powersupport replied to the thread windows server 2025 not starting in Proxmox.Hi, The issue appears to be that your Windows Server 2025 VM is stuck in an Automatic Repair loop and unable to boot normally. Since the cloned VM is also showing the same behavior, this likely indicates OS-level corruption or a possible...
-
powersupport replied to the thread Whole disk backup every time on stopped VM.Hi, This is normal behavior. Even though the virtual machine is stopped and hasn’t changed, the system still needs to scan the whole disk during backup. However, it does not actually store or upload the full data again. Since nothing changed...
-
powersupport replied to the thread Raid1 boot array, drive replacement procedure.Replacing a Failed Disk in Proxmox (BTRFS RAID1 – Simple Explanation) If one disk fails in a Proxmox BTRFS RAID1 setup, your server will still boot from the other disk. That’s normal and expected. Sometimes it boots in “read-only mode.” This is...
-
powersupport replied to the thread move vm backup to namespace but vm id is equal.Hi, This is expected behavior in Proxmox Backup Server. VMIDs must be unique within the same namespace, so moving a backup to the root namespace will fail if the same VMID already exists there. Currently, there is no way to rename or change the...
-
powersupport posted the thread Secure Boot – Microsoft UEFI CA 2023 certificate support in current Proxmox VE versio in Proxmox VE: Installation and configuration.Hi, We are preparing Windows Server VMs for Microsoft's Secure Boot certificate updates (Microsoft UEFI CA 2023). We are currently using Proxmox VE with Secure Boot enabled and EFI disks (OVMF). May I confirm: Does our current Proxmox version...
-
powersupport replied to the thread Secure Boot – Microsoft UEFI CA 2023 Certificate Not Included in EFI Disk.Hi, We are preparing Windows Server VMs for Microsoft's Secure Boot certificate updates (Microsoft UEFI CA 2023). We are currently using Proxmox VE with Secure Boot enabled and EFI disks (OVMF). May I confirm: Does our current Proxmox version...
-
powersupport replied to the thread VM names disappear.Hi, This usually happens when the Proxmox GUI or services don’t refresh the VM list properly, even though the VMs are still running. You can try restarting Proxmox services instead of rebooting: systemctl restart pve-cluster pvedaemon pvestatd...
-
powersupport replied to the thread Mountpoints for LXC containers broken after update.After the update, Proxmox now handles container mount points more strictly. This mainly affects unprivileged containers. Mounted folders now show up as root:root inside the container, so services like MySQL can’t access their files. If a mount...
-
powersupport replied to the thread VM Internal Error.This VM runs Blue Iris, which heavily uses the GPU all the time (video decoding, encoding, and AI processing). Other VMs using the same Intel GPU are fine because they don’t use the GPU as heavily or continuously. What appears to be happening...