Search results

Hi @larryd, welcome to the forum. Its hard to provide ideas as there is not enough technical information in your post. Answering the following questions may assist members to provide some guidance: - What type of storage are you using? (Vendor, model) - What type of connectivity? - What is the...

Hello @br8k , welcome to the forum. When you have an orphan disk, it should appear as "unusedX" in the VM's hardware configuration after doing "qm disk rescan". If it did not, there are more things to look at. One possibility - NFS is no longer marked as Image-carrying storage. That said, a...

It should be fine to tick one and untick the other. No warranty, express or implied, regarding the results :-) If you need a more deterministic answer - purchasing a support subscription and opening the case with your Hypervisor vendor is the way to go. Cheers Blockbridge : Ultra low latency...

For zeroing out the volumes you will want to change this to 1. I am not sure what you want to uncheck about the LUN access. The iSCSI storage is already set to "content image", that should be sufficient. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

What is the context of your /etc/pve/storage.cfg? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

It is hard to say what the risk profile is. You would need to examine what this storage is, what portion of it is used and in what way. If nothing is actually using the storage or Direct LUNs, then unchecking it will not hurt. A Direct LUN means that you took an iSCSI LUN and passed it through...

You should not Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

The man page states: --saferemove <boolean> Zero-out data when removing LVs. It zero's out the blocks which were occupied by a particular LV, not the entire physical disk. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

https://forum.proxmox.com/threads/issue-with-deleting-vms-in-proxmox-environment-use-luns-directly.182261/#post-846221 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @2000gtacoma , You should look into "saferemove" option for storage pool (man pvesm // search for saferemove). I believe when an LVM/qcow is removed, the standard option is just to delete the metadata. The actual user data is still left on the disk. Obviously zeroing out the disk, especially...

lvremove simply deletes the metadata entry. The actual data is still on disk. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

The additional information you provided seems to confirm my theory that you had a disk that was was not wiped on deletion. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @mlukasik , Its possible that you are running into a situation where a VM or its disk were removed but not wiped. The data is still on the physical disk and can be read by other processes/VMs. That said, you did not provide sufficient data about the "different VM" (is it still around, is the...

Hi. The output you provided is from the very first moments of your PC boot. It contains nothing of value for the question at hand. I've asked AI to generate a quick list of commands that can assist in troubleshooting a failed PVE instance. Please run them, examine them first on your own. If you...

@ASM-Network You could try to configure two iSCSI storage pools and scope each to one node only (using "nodes" option). Or you can simply use direct iscsiadm commands to manually connect iSCSI on each server and only use shared LVM pool. The process is described in the article I mentioned...

Please run the commands that were requested earlier. The configuration and system state may be clear to you, but the forum members are not familiar with your infrastructure. It is unusual for a system to present two different iSCSI targets out of two interfaces of the same controller. Did you...

Hi @Andrei18 , welcome to the forum. Have you played with clustering this system at any point? The screenshot indicates that not all PVE services are starting. You can check "systemctl" for additional information. Also, "journalctl -b0" may be informative. You mentioned that pings work, are you...

Hi @ASM-Network , welcome to the forum. This is an unusual configuration. What forced you down this particular path? Is the Sever2 connected to Port2 on Controller1 or Controller2? No, you can't just edit storage.cfg on the second server. The storage.cfg is located on a shared/clustered...

Hi @Pigi_102 , LVM is not a filesystem; it is a volume manager. The logical volumes it creates are exposed as raw block devices. The volume is attached to the VM as a virtual disk, and the filesystem is created and managed inside the VM. Because of this, you will not see any mounts on the...

Proxmox has the ability to incorporate patches and build updated packages as needed. Given that Proxmox VE is frequently deployed as an appliance, and is relied upon by many enterprise environments, there may be cases where, depending on the severity of a vulnerability, it makes sense for fixes...