@sikeb , I've already mentioned it but lets get on the same page regarding the layers involved:
Proxmox Server Solutions GmbH - a company that develops PVE, PBS, and PMG. The name is often shortened to Proxmox.
Proxmox Virtual Environment (PVE) - Open Source Hypervisor product.
PVE is a management and HA overlay software suite that builds upon multiple standard Open Source technologies (Debian Linux, Ubuntu-derived Kernel, KVM, Ceph, Corosync, Fuse filesystem, etc).
The ability to access hardware (disk, CPU, GPU, NICs) is provided and controlled by Linux Kernel.
If the Linux Kernel is unable to see your hardware, PVE will not be able to use it.
The Linux Kernel differs from the one that comes with Vanilla Debian or Ubuntu installation, but only slightly.
The basic disk management is all in the Linux Kernel. It is the same as in Redhat, Slackware, Suse, or Mint.
Put the Proxmox layer aside for a moment. Imagine it does not exist.
You must present the FC LUNs to every host and they must see them for you to continue. If you have multiple paths between storage and client, you then must employ standard Linux Kernel and Userland Multipath components. Before this, you must ensure that each host sees at least a double of each disk (sometimes quadruple if you have a complex environment).
To answer your question - yes PVE works with multipath iSCSI and/or FC storage. But you must configure the basics for everything to work.
High-level steps for you to follow:
a) check as to what each host sees for disk (lsblk, lsscsi, dmesg, journalctl)
b) confirm that freshly booted hosts all see the appropriate amount of LUNs (including duplicates)
c) follow your vendor multipath guidelines
d) create an LVM volume group
e) create an LVM storage pool
f) the world is your oyster
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
