Please share the context of the "/etc/pve/storage.cfg"
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
I'd pay attention to IP conflicts in your network - your symptoms can be explained by a transient duplicate IP.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hi @Jianming , also note that your backend storage may provide some level of thin provisioning at the SAN layer, independent of the iSCSI and LVM.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Hi @promxmox_user021 , welcome to the forum.
I understand that you would prefer to have a built-in checkmark to address your needs. However, you have a very specific use-case, and I believe you can already address it with post-clone processing...
The IO error indicates a basic Linux connectivity issue. Are you using Jumbo MTU? Are you sure there are no IP conflicts? Are there any errors on the network interface? Could this be a bad cable? A bad switch port?
Start with the basics -...
Another approach is to write a healthcheck/probe script that all the other PVE services will depend on. Once the probe determines that SAN is up - it lets the others to proceed.
Or, the probe is independent and simply reboots the host when the...
You can use pvesm command : https://pve.proxmox.com/pve-docs/pvesm.1.html
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Then it sounds like you dont need to disable it?
The subdirs are created by PVE as needed based on "context" option.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
The storage.cfg is a globally shared file within a cluster. The configuration in this file must be valid for all nodes.
The name of the storage pool is unique cluster-wide.
dir: local
disable
path /var/lib/vz
content...
As you can see from the output you posted (next time you should use CODE tag </>), the storage with question mark (magnus) is allowed to be present on both nodes. However, most likely is not present on node2 - hence the ?.
The "local" dir...
What is the context of your /etc/pve/storage.cfg? does it contain "node" restriction by chance?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Hello @bubblegoose, welcome to the forum.
There is one issue we should address first: the format of the data you provided is very difficult to read. Forum members, myself included, would greatly appreciate it if you could edit your post and use...
We are pleased to announce the release of Proxmox Datacenter Manager 1.1!
This point release focuses on expanding visibility and automation for large-scale, multi-site deployments. Our main focus for this iteration has been introducing...
I couldn't wait until tomorrow :). It is working now. Stupid mistake on my end. Thank you so much for getting me in the right place. I probably would have never gotten it. Much appreciated.
The system reported the above message, we have no reason to doubt this. If something changed since then - we have no evidence of it.
An LACP bond that is misconfigured between two network nodes leads to an unpredictable behavior. Trying to...
Most likely there is an issue (network or configuration) with RPC requests. The exports are probed via "showmount" and "rpcinfo". Try these commands manually, if they fail - the PVE probes will be unsuccessful and you will not be able to manage...
To be on the same page, none of this is PVE specific. You are dealing with basic Linux network management.
At one point in the thread you mentioned that there is a "direct" connectivity between the clients, is there an actual direct cable?
Your...
Wed May 27 12:54:51 2026] bond2: Warning: No 802.3ad response from the link partner for any adapters in the bond
I would recommend that you reduce your network complexity to bare minimum. Then start adding it back piece by piece, making sure...
You have two interfaces sitting on the same subnet, its very likely that this is what is tripping you up. I would recommend avoiding this configuration when possible.
If you are curious, you should examine routes and ARP tables during the...