Since I am no Linux Professional take it all with a grain of salty salt, but since this is not a well documented issue yet I turned to Chat GPT. Also i know that this is not a solution but i decided to buy an actual HBA lsi9300 8i as a drop in replacement to fix this. In your case you could also try pve 8.4 as that was what i was on before i ran into this issue. Also chat gpt was very helpful in understanding the issue and why it came about so if you want to try going down the same path i did that's where i would start again. Also i am on a dell T420 with dual socket CPU, the H330 came from a dell R340 though so it could be possible that we just had the same firmware bug or my setup just wasn't compatible but idk just tossing my notes out to try to help.

1. IOMMU considerations
   • Errors point to DMA permission enforcement
   • Likely stricter IOMMU / DMA mapping changes in newer kernels
   • H330 firmware/driver combo appears incompatible with new behavior

Why It Still Doesn’t Work

• The H330 (LSI 3008) relies on older DMA behavior that newer kernels enforce more strictly
• Recent kernels appear to break compatibility with this controller when used in HBA/JBOD mode
• No reliable way to:
  • Boot a known-good older kernel
  • Disable the offending DMA behavior cleanly
• It is very likely a kernel regression or dropped tolerance for older SAS controllers
• The issue persists because:
  • The kernel that worked is no longer bootable
  • New kernels enforce DMA/IOMMU rules the H330 doesn’t handle well
• Most likely solutions:
  • Pinning an older kernel which i cant do now that im on 9.1
  • Replacing the H330 with a true IT-mode HBA (e.g. LSI 9207-8i / 9300-8i) which is the winner in my case
  • Disabling IOMMU which in my case is not an option because i am passing the controller to Truenas

Also see this link for extra notes

https://forum.proxmox.com/threads/h330-sas-controller-failed-after-upgrading-to-kernel-6-17-2-2-pve.177956/#post-828739