I've "solved" this issue this morning, my VM needed a network card and a SATA controller so instead of using my motherboard controller I gave it the PCI card. Problem solved !
Thanks a lot for the help anyway !
I may have found something: the SATA PCI Card is on the same IOMMU group that a network card. This network card is being passthrough in one of my VM so maybe that's the problem. How can I put this card in its own IOMMU group ?
I double checked: At boot I have a screen that says I have this card plugged in with a 500GB SSD plugged in. That makes me think that the problem is at Proxmox level.
Hello everyone,
New server is up and running and is working like a charm except one major issue.
I had to add a few extra SATA ports so I bought this SATA PCI controller (based on Marvell 9215).
At boot I see the card and the drive attached to it but one Proxmox is started no traces of the disk...
I've "solved" it by editing /etc/default/grub
and in GRUB_CMDLINE_LINUX_DEFAULT I added pci=nommconf and I no longer have the issue.
Is it recommended and safe ?
Hi everyone,
I have a problem on my new Proxmox server. The logs are flooded with these lines:
Oct 3 19:22:42 proxmox kernel: [ 99.530012] pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0
Oct 3 19:22:42 proxmox kernel: [ 99.530016] pcieport 0000:00:01.0: PCIe...
You're right that seems better.
Anyway I'll try to activate IOMMU and pass my SATA controller to my OMV VM that seems the simpler and better solution you propose.
Hello,
So I've setup my Proxmox on a PCIe 500GB inside my server. I started my first machines (PiHole, LibreNMS, etc...). Now what I need to do is to use 4 3Tb HDDs to setup a NAS.
What I did was to create my VM on the SSD and I connected the physical drives through "qm set VMID --sataX...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.