Proxmox runs on a Supermicro H12SSL-NT motherboard with an Epyc 7443p. I've attempted to pass through the onboard SATA controller to UnRaid to make disk spindown easier. Based on experience (and posts on the forum), the <SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)> is not well supported, and passing it through requires workarounds. So, I reverted to passing them through as SCSI.
The strange thing is that even after removing the SATA controller, Proxmox or BIOS did not detect the drives. To restore access to the drives, I had to disable the SATA controller in BIOS, reboot, and re-enable it. At this point, the drives were detected, and the error messages <ata1: softreset failed (1st FIS failed)> stopped.
Once I removed the PCI passthrough to the VM, I expect the system to detect the drive as before; what am I missing? How can I restore/clean up my Proxmox host after such failed explorations? Though my changes to BIOS worked in this case, there must be a better way to do this.
I am trying to learn from this adventure.
Versions
proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pv
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
The strange thing is that even after removing the SATA controller, Proxmox or BIOS did not detect the drives. To restore access to the drives, I had to disable the SATA controller in BIOS, reboot, and re-enable it. At this point, the drives were detected, and the error messages <ata1: softreset failed (1st FIS failed)> stopped.
Once I removed the PCI passthrough to the VM, I expect the system to detect the drive as before; what am I missing? How can I restore/clean up my Proxmox host after such failed explorations? Though my changes to BIOS worked in this case, there must be a better way to do this.
I am trying to learn from this adventure.
Versions
proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pv
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)