I followed the instructions on Proxmox documentation to have an HBA card passed though to a VM. Proxmox sees all the drives with no issues. Boot drive is not connected via HBA card.
Initially the VM recognized the card and drives with no issues.
Then after rebooting the Proxmox server and left it at idle for exactly 5 mins, without starting the VM, the log shows the drives that are NOT connected to the HBA card go through "synchronizing SCSI cache" and then immediately after, mpt3sas seems to disconnect the drives on the HBA card one by one. (See photo). Then I cant get those drives to come back online and booting the VM causes it to either hang, crash, or not see the drives anymore. The card itself has it's green light that is normally flashing, is off. The drives still are shown under 'storage' section Proxmox.
I assume this is a power management issue? What should I be checking?
I want to retain the ability to spin down drives if I need to. That's why I thought passing through the HBA card would be better to manage this.
Any ideas?
Initially the VM recognized the card and drives with no issues.
Then after rebooting the Proxmox server and left it at idle for exactly 5 mins, without starting the VM, the log shows the drives that are NOT connected to the HBA card go through "synchronizing SCSI cache" and then immediately after, mpt3sas seems to disconnect the drives on the HBA card one by one. (See photo). Then I cant get those drives to come back online and booting the VM causes it to either hang, crash, or not see the drives anymore. The card itself has it's green light that is normally flashing, is off. The drives still are shown under 'storage' section Proxmox.
I assume this is a power management issue? What should I be checking?
I want to retain the ability to spin down drives if I need to. That's why I thought passing through the HBA card would be better to manage this.
Any ideas?