Then, apparently to mount the share to Plex, I needed to pass the pool from TrueNAS back to ProxMox.
I doubt this part.
I think as soon as the NAS is working, the others (including prox) should use it, and no additional complications.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Then, apparently to mount the share to Plex, I needed to pass the pool from TrueNAS back to ProxMox.
I doubt this part.
I think as soon as the NAS is working, the others (including prox) should use it, and no additional complications.
It's probable that I'm missing something but I couldn't get the share to be available to any other VM or LXC on ProxMox until I passed the pool from TrueNAS back to ProxMox.
I'm all for getting rid of the TrueNAS VM as long as I can reassemble the zfspool in ProxMox without losing the data (though if I did, no big deal). And I'd also like a user friendly way of monitoring the health of my disks.
reassemble the zfspool
zfs itself can do that. The zpool members know the pool and the other members.
I am working on setting up somethin similar. I have a Truenas Scale VM and some lxc-Container where i plan to run some arr-services and paperless ngx. Mounting the NFS-Share proves to be a bitch. I tried it several ways and to this point in time i wasnt sucessfull.
i'm sure its a skillissus on my part ;)
@some_dude I would not run truenas as a VM on the proxmox cluster youre storing for. This should be a separate box, connected over NFS. If your proxmox fails, you rebuild the host and import the VMs stored on the truesnas share. If your true nas fails, you rebuild the boot drive and zpool import your zfs disks.