Iâm running various WD Red Plus hard drives (7 of them ranging between 8 and 12TB)
In TrueNAS, I can create a pool, data store and SMB share (using raidz2). I can start copying my data over and at some point (about the most I got was around 1TB), it fails and repeatedly said power-on or device reset occured.
I have since set up trueNAS bare metal and I copied 10TB over without any issue at all. I donât think itâs a temperature think (case is currently open with a box fan pointing at it).
BIOS has VTD enabled.
Any thoughts on anything else I need to check? I suspect itâs a bios/hyperv/windows setting. I can provide any additional information that you need.
Maybe itâs a HyperV thing, maybe your HBA is overheating or just faulty. A box fan is typically not that much airflow over a small area, it does move air but the pressure is low.
So you only have issues with Truenas when you use windows server as the hypervisor & pass through the HBA to truenas? It works just fine bare metal as you statedâŚ
I mean, if youâre dead set on running Truenas as a VM, then give proxmox a test spin. At least itâll narrow down if this is a passthrough issue or windows server issue?
Otherwise, any reason running bare metal isnât acceptable?
Thanks for the reply. Mostly running windows for the flexibility because there are a couple other nice to have apps that need windows. I can get by without them if need be and then just run TrueNAS bare metal.
Iâll try to give proxmox a test spin at some point. Iâve never used it. Any good walkthrough before I go looking for one?
None off the top of my head - only warning I got is that proxmox also understands zfs⌠so passthrough the hba/sata controller (as youâre already doing) & blacklist them from proxmox.
Honestly it was very point & click to setup; would recommend slapping it onto a usb stick to just get a feel for it & for a quick âdoes this fix my issueâ test.
Edit; Truenas can also be a hypervisor, I personally donât have any issues with the vms on my truenas system⌠Iâm sorry that every solution I have for you is âtry something else as your hypervisorâ btw. I have no windows server experience beyond some 90s version for a very, very legacy product.