TRUENAS IN Proxmox

TrueNAS General
1

I have Truenas in proxmox and I don’t know why, but I don’t see the CPU temperature and when I set spindown on the disks, there’s nothing.

processor: i5-2400 intel
graphics card: integrated
RAM: 2x 8GB x star
disk: Samsung SSD 128 GB
bios version: PO1-A

Settings proxmox:

image
image832×386 21.2 KB

2

CPU temperatures and in general hardware parameters are not available to a virtual machine on any virtualisation platform. You need to manage/monitor these things in Proxmox, e.g. by installing SNMP and using a network management system like Observium or LibreNMS.

Similarly for disk spindown. Your TrueNAS SCALE gets virtualised (VirtIO) disks, there is no way for it to talk to the devices directly.

Which leads to the conclusion that you have a very dangerous setup with a high probability of data loss. You should use a dedicated HBA, PCIe passthrough of that into the SCALE VM, and connect your SATA disks to that.

3 Likes
3

Apart from pmh’s advice, does devoting CPU/RAM resources to a TRUENAS VM make sense when you only have 4 cores & 16 GB RAM on your proxmox host?

Better to make use of lxc containers whenever possible. Learn to create and administer a zfs pool directly on your proxmox host. If you need file shares, create and configure a lxc container as a fileserver and bind mount zfs datasets on the host to the container. If you need “apps”, use docker in lxc, it’s not officially sanctioned by proxmox, but plenty of homelab folk do it.

2 Likes
4

Do you use Proxmox for anything that can’t be done in TrueNAS on Bare
Metal?

Because it’s quite easy to convert a virtual TrueNAS install to bare metal.

Can even be done temporarily if you have a spare boot drive.

5

Congratulations on getting it up and running. :slight_smile:

Set the CPU in the VM to host. You won’t be migrating your VM, so using one of the emulated/virtualized CPU-types is unnecessary.

Setting the CPU to host will let the VM take full advantage of the CPU by using its actual instruction set at full speed, with no emulation layer between them. I’m not sure if that’ll fix your temperature monitoring, but your VM will be happier.