I did. About the only thing I didn't try was downgrading the firmware.
Oh well. I'll just pass the volume. I am tired of dealing with it and that seems to work.
Potentially I might want to create 15+ drive storage spaces based pool. Then I'd need to pass the controller or hba (I'd just get the hba, would be silly to just use the expensive raid card for jbod). I thought about doing this, but I don't think I will. Yes, I know about ZFS, I just don't want...
There isn't a *need* to pass it to windows. At least, as long as I use it as RAID and not JBOD. (You can only pass 15 scsi disks to a VM).
It works in Windows 10. It doesn't work in Windows Server. While the volume is empty right now, it isn't a big deal. Understanding the root of the problem...
Everything works great passing the controller to Windows 10. It all falls apart passing the controller to Windows Server 2016/2019.
Inside the Windows 10 VM, I was able fill 75% of the new volume by copying data from a 2nd volume on the same controller. Inside Server VM, I can't even format the...
This is more of a question, not saying anything is wrong with proxmox.
I am able to pass thru an Areca 1882ix-24 to Windows 10 and use the latest Areca driver (6.20.00.33) without any issue.
If I attempt to pass this card thru to a Windows 2016 or even Windows 2019, I start having all kinds of...
I have an Areca raid controller that I was going to pass to the VM, but I'm having issues with it the VM not being able to reboot because it isn't "releasing" the card. I am going to look into blacklisting it on the host to see if that makes a difference, but I thought, maybe I'd just pass the...
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.