13 November 2025
At first there was only one plugin, then two, then between June and November 2025, it became 4:
- https://github.com/ondrejbima/freenas-proxmox
- https://github.com/TheGrandWazoo/freenas-proxmox
- https://github.com/boomshankerx/proxmox-truenas
- https://github.com/WarlockSyno/TrueNAS-Proxmox-VE-Storage-Plugin
To be honest, I wish the folk at Proxmox folk would take over the development of this module because clearly there is demand. And they have other drivers already. But for the uninitiated, here is a quick breakdown:
#1 was last updated 4 years ago
#2 was forked from #1, updated for a while, and then abandoned somewhere in 2025
#3 was inspired (note, not forked), from #2 and now actively maintained.
#4 Seems to have a lot of energy from WarlockSyno. I’m still learning where this comes from, but to be honest, to have two new modules competing with each other is a bit shit, but there you go. It’s a free world.
My concern is #2 because I can’t use deprecated software.
Environment
As of November 2025, the latest version of TrueNAS (Scale) is 25.10.0
https://www.truenas.com/download-truenas-community-edition/
https://www.truenas.com/docs/softwarereleases/
I guess on the plugin front, my concern is these folk are asking for donations. That’s not true open source because now you’re motivated by money and how many people donate, and I guess that’s why Kevin got bored because it just doesn’t pay. But moving on…
Freenas-Proxmox
July 31 Post below
Problem #1 (with #2 “freenas-proxmox”):
- Got stuck in the old name “freenas”
- Doesn’t work with Perl Library
- Stopped working with Proxmox 8.4 (?) upgrade Perl library, and this is a huge issue:
Workaround
For now we’ll prefer to be stuck in time till we can observe the new guys fight it out with their competing plugins on GitHub.
apt list --installed | grep libpve-storage-perl apt policy libpve-storage-perl apt install libpve-storage-perl=8.3.6
Note, if you do this on an already upgraded system, the freenas installation will give a post installation error. Reason:
dpkg stores failure state internally.
Once a package’s “configure” step fails, dpkg will always report errors on it unless:
-
the package is removed/purged
the broken maintainer scripts are deleted
Reference
The reference below is a user in the issue log who tried fixing it themselves.
https://github.com/TheGrandWazoo/freenas-proxmox/issues/210
proxmox-truenas – BoomshankerX
Issues
BOTH VERSIONS OF THIS PLUGIN CANNOT BE INSTALLED AT THE SAME TIME – compatibility, see here:
Main version compatibility:
- TrueNAS 25.10+
- Proxmox VE 8/9
Deprecated:
- TrueNAS 24.10 – 25.04
- pve-manager 8.4.14 / 9.0.11
- libpve-storage-perl 8.3.7 / 9.0.13
Strong points:
- It has an upgrade guide for #2 (GrandWazoo) users.
- Nice guide.nd can be actively maintained by the community.
https://github.com/boomshankerx/proxmox-truenas/wiki/Configuration-Guide
WarlockSyno
Introduction on Reddit
- https://www.reddit.com/r/Proxmox/comments/1nwi3a3/truenas_storage_plugin_for_pve/
Introduction 17 October 2025 (and long post) on the Proxmox forum:
- https://forum.proxmox.com/threads/truenas-storage-plugin.174134/
Possible issues:
- Seemed to be more manual, but then a script came about, currently seems alpha.
- MPIO is slow? https://github.com/WarlockSyno/True…ions.md#multipath-read-performance-limitation
- NVMe-TCP not implemented?
On WarlockSyno’s readme we learn of more important deprecations:
TrueNAS SCALE 25.04+ Users: The TrueNAS REST API has been deprecated as of version 25.04 and will be completely removed in version 26.04. This plugin supports both WebSocket (recommended) and REST transports. Ensure you use WebSocket transport (api_transport ws) for TrueNAS 25.04+.
For TrueNAS 26.04+, REST transport will no longer function.
Other information
Unsupported SA: 0x12 aka SAI_GET_LBA_STATUS
This is also nicely mentioned in BoomshankerX’s readme, this and TPM below.
- https://forum.proxmox.com/threads/lsi-sas2308-scsi-controller-unsupported-sa-0x12.78785/
- https://bugzilla.proxmox.com/show_bug.cgi?id=4046