FC San Boot Installation: Fails to enable Multipath kernel boot argument during ISO boot

[arunkum]

I am attempting FC sanboot installation with Proxmox 9.0 for the first time, by appending the kernel argument "multipath=on" (press 'e' and update linux kernel argument) during the ISO boot wizard.

Proxmox picks up a single SCSI device as installation device, instead of the /dev/mapper/







Post installation:

root@HPE-DL365-14-180:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 170G 0 disk
└─sda3 8:3 0 169G 0 part
├─pve-swap 252:3 0 8G 0 lvm [SWAP]
├─pve-root 252:4 0 52.2G 0 lvm /
├─pve-data_tmeta 252:5 0 1G 0 lvm
│ └─pve-data 252:7 0 90.7G 0 lvm
└─pve-data_tdata 252:6 0 90.7G 0 lvm
└─pve-data 252:7 0 90.7G 0 lvm
sdb 8:16 0 170G 0 disk
sdc 8:32 0 170G 0 disk
├─sdc1 8:33 0 1007K 0 part
├─sdc2 8:34 0 1G 0 part
└─sdc3 8:35 0 169G 0 part
sdd 8:48 0 170G 0 disk
├─sdd1 8:49 0 1007K 0 part
├─sdd2 8:50 0 1G 0 part /boot/efi
└─sdd3 8:51 0 169G 0 part




Not sure if i missed any config steps here.... is "multipath=on" a supported argument to enable device-mapper for FC san boot installation ??

 

[bbgeek17]

I believe for FC boot the advice has always been to install PVE over Debian: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie
And in this case, you'd use standard Debian instructions for SAN boot.

---

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