Recent content by Weehooey-HSS

Hello! Bugs are reported here : https://bugzilla.proxmox.com/ Thank you!

Hello! To move your VMs to the new disk: Select the VM where the virtual disk needs to be moved, click Hardware > "The disk you wish to move" > Disk Action > Move Storage. For copying/SCP files to your LVM drive: If you refer to the storage table here...

If feasible, it's ideal to maintain at least one standalone Corosync link on dedicated hardware. Your backup Corosync links can share connections, but ensure that your primary link remains on dedicated hardware. You should also always have multiple Corosync links.

I am under the impression that running corosync over a bond is not recommended. Two separate links would be lower latency and easier for corosync to rebalance. https://forum.proxmox.com/threads/interface-bonding-iscsi-storage-corosync-ceph-and-vm-network-best-practice.123804/post-538938 You...

From the logs, you have significant network issues, at least over your corosync links. This is likely causing your cluster to lose quorum. If possible, it is recommended to have multiple corosync links, with one preferably over a dedicated switch. I would test connectivity between all nodes...

How many corosync links do you have? Giving your logs a peek may point you in the right direction. /var/log/ceph/ and journalctl -u corosync journalctl --since "10 hour ago"

Hello! To my knowledge, enabling NUMA on a device with just one NUMA node or socket presents no disadvantages. This configuration informs the guest of the host's NUMA topology, allowing the guest to allocate resources more strategically. In rare instances where NUMA is enabled on a system...

You will not need to re-install; it is in ALPHA, however. More information here and here You can run it as a VM, and it will handle the Remote migration commands from the PDM GUI.

Hello! The screenshots of the commands you ran above show that you are missing some arguments for qm remote-migrate. If you use the IP and not the hostnames, you need to specify a fingerprint when using the command. qm remote-migrate <localVMID> <RemoteVMID>...

Hello! I always have great luck with: qm remote-migrate Check out the options here

Oh, Perfect! Thanks for the update!

Hello! To get your VM up and running, try detaching the disk and reattaching it as IDE or SATA. Be sure to check your "Boot Order" under options. You may need to temporarily return your controller to the LSI until you install the VirtIO drivers. After you get it up and running, you will need...

Would this be a permanent solution? You could pass the drive through over USB or a spare drive controller if not. I am unaware of any "Clean" way of doing this permanently. But if you need the data copied, the passthrough is an option. Thanks!

Hello! Proxmox Feature requests go here: https://bugzilla.proxmox.com/. Once you submit it, please post the link so anyone searching for it can CC or comment. Thanks!

Unless you copy the NAS data to a VM or CT and then backup that VM or CT, I don't think there is a clean way to achieve what you're asking. I would heavily recommend staying away from that in any form of production. PBS is primarily designed for backing up and restoring PVE VMs and...