[SOLVED] How to blacklist a pcie hba

cherowley

New Member
Apr 22, 2025
8
2
3
Hi!

I'm trying to stop proxmox from mounting some mdadm lvm's on disks attached to a LSi hba during proxmox boot.

I've added the following 2 lines to /etc/modprobe.d/blacklist.conf:

softdep mpt3sas pre: vfio-pci
options vfio-pci ids=1000:00ac

But they are still being seen during boot and can be seen in the pve disks tab.

This causes a problem as when I then pass the pcie hba through to a virtual running xpenology the proxmox system must be looking for the lvms and starts to get hung tasks and eventually the webui goes unresponsive and rebooting via ssh takes ages as it waits for all the hung tasks (lvs, lvm etc)....


When do the lines I added to blacklist not hide the hba and therefore the disks?!

Help!
 
softdep mpt3sas pre: vfio-pci
options vfio-pci ids=1000:00ac

But they are still being seen during boot and can be seen in the pve disks tab.
Did you run update-initramfs -u (for your active kernel), otherwise it won't be active? What is the output of lspci -nnks THE_PCI_ID_OF_YOUR_LSI_HBA after a reboot before starting the VM?

Note that you call this "blacklisting a device" but it's actually called "early binding the device to VFIO" (not to be confused with blacklisting a specific driver).
 
Try passing it through without any disks attached. I passed through a m.2 to SATA adapter to TrueNAS scale and I didn't have to blacklist anything. Once it was attached to the VM, Proxmox stopped seeing it.
 
Did you run update-initramfs -u (for your active kernel), otherwise it won't be active? What is the output of lspci -nnks THE_PCI_ID_OF_YOUR_LSI_HBA after a reboot before starting the VM?

Note that you call this "blacklisting a device" but it's actually called "early binding the device to VFIO" (not to be confused with blacklisting a specific driver).
Ooo, thanks buddy, no I hadn't done the update-initramfs -u!

Ah many thanks, that did the trick!

Been trying to sort this issue for a few days, now all's good :)
 
Try passing it through without any disks attached. I passed through a m.2 to SATA adapter to TrueNAS scale and I didn't have to blacklist anything. Once it was attached to the VM, Proxmox stopped seeing it.
Thanks, the problem was as the hba was seen during the starting up of proxmox, proxmox then mounted the lvms on ths hba disks. running the virtual passed through the hba cutting the lvms off from proxmox wihich it didn't like lol.

Thanks anyways :)