UPDATE EDIT:
Man it is crazy to watch the dashboard and console at the time. Even with no HDD’s spinning, and as much RAM as I can give the Scale VM, services just slowly takes over the RAM, until the console shows kernel panic.

core was solid for so long with everything i threw at it.

it runs out of memory after services soaks up all the RAM, ZFS cache is choked down to 3gb out of 16.

  • xeon E3 1265LV2
  • Asus p8z77-v-deluxe
  • 32GB DDR3
  • hba passed through to truenas running a mirror pool

VM for truenas is running on the local proxmox SSD.

  • proxmox 9.1.1
  • TrueNAS scale 25.10.0.1 but i tried a 24 version also

once the install starts crashing, the VM will still crash after booting up without the HBA card

I’ve seen a few posts with other people having the out of memory issues (OOM) but almost every reply says it will be fixed in the next update, which is older than what we’ve got now.

it did run okay enough JUST long enough to make the mistake of updating the ZFS flags, so now i can’t roll back to core.

does scale have this issue because it’s virtualized? would it run better on bare metal?

anyone tried xigmaNAS? freeBSD based again at least.

Unraid looks okay, but paywall?

open media vault?

any advice or discussion is appreciated!

  • SapphironZA@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    10 hours ago

    By exprience with Trunas has been that ZFS does not like virtual disks. Especially when the Proxmox host also uses ZFS. Two layers of ZFS arc caching creates some memory issues. Setting the Host datasets to Metadata only may help.

    But the most reliable method would be doing hardware passthrough of physical disks to the VM. It gets you most of the bare metal reliability benefits without having to commit the entire hardware box to one OS.

    You may also want to disable memory ballooning in your VMs. It works well when you have lots of small VMs, but if you have a few large ones, it can cause issues if you overallocate Ram to VMs, beyond what the OS has available. I suspect it could also be interferring the zfs arc as well.

    Lastly, check that your VM is set to use the “host” Cpu type. Freenas would likely benefit from having access to more CPU functions.