Selfhosted

I hope you have backups

Never should you pass disks though by VM. The disk and SMART data is not passed though so ZFS has no way of knowing disk status. It also has more overhead than just passing though a PCIe device.

I would strongly recommend that you fix this ASAP

Proxmox supports ZFS natively with management in the WebUI. So you could get rid of TrueNAS entirely and not need to deal with HBA pass-through or anything.

You also wouldn't need NFS or have to deal with shares, as the data is available directly to Proxmox Containers via bind mounts.

You should have all your data separately stored, it shouldn't be locked inside containers, and using a VM hosted on a device to serve the data is a little convoluted

I personally don't like TrueNAS - I'm not a hater, it just doesn't float my boat (but I suspect someone will rage-downvote me 😉)

So, as an alternative approach, have a look at OpenMediaVault

It's basically a Debian based NAS designed for DIY systems, which serves the local drives but it also has docker on, so feels like it might be a better fit for you.

Debian supports zfs so why the extra hassle of truenas? Seems to be a lot of extra work to add a vm when you could just use zfs in Debian. Or install something like Minio in Debian and use that to manage the data in s3 style buckets, again no vm needed

I would probably shy away from passing the raw disk. There are a few dozen ways to skin that, But in the end I would probably just mount the disc through NFS,smb, whatever it takes. Reading that smart data is paramount for your situation. You could have a bad cable and never know it.

You could run a couple of VMs K8S and longhorn the data, It's capable of backing up to an S3 compliant storage.

For my home stuff at the moment I'm running unraid with a BTRFS and a parity disc. The first every month I run a scrub if I had any corruption it would find it for me and alert me. It's slow as balls but more protection is better than less. You can also buy some recycled discs and keep a offline store. I don't love the recycled discs but for backup purposes that aren't running 24x7 they're better than nothing.

I run a docker host in Proxmox using ZFS datasets for the VM storage for things like my mailserver and NexcloudAIO. When I backup the docker VM, it snapshots the VM at a point in time, and backs up the snapshot to PBS. I've restored from that backup and it's like the machine had just shut down as far as the data is concerned. It journals itself back to a consistent state and no data loss.

I wouldn't run TrueNAS at all because I have no idea how that's managing it's storage and wouldn't trust the result.

@thelemonalex I usually find that sata cable or connector are bad.

Personally I use proxmox as a host and share bulky nfs mounts for each VM like Immich, Plex/Jellyfin. For gitea and other small VM - use VM virtual drive and back it up periodically

I was in somewhat of a similar situation but some of the SATA ports were bad and ended up buying a cheap SATA to PCIE card and passing it instead but that still had some issues so I ended up moving TrueNAS to its own dedicated machine and haven’t had any problems since.

Just my two cents.

If you're only doing a VM or two, I'd get rid of proxmox and run truenas directly. It's gotten better for VMs.

Also make sure you read up on the ecc requirements for truenas if you're not using ecc ram

If you pass a whole raw disk, not virtualized, then TrueNAS should not complain. I don't know if you can do that in proxmox, I haven't tried.

Personally I'd get rid of TrueNAS. Even if docker is down, the VM with the data is still up and accessible over anything running on the VM, like scp via ssh.

I have two identical HDDs as a mirror, another one that has no failsafe (but it's fine, because the data it contains is non-critical)

On separate pools, I hope? My understanding of ZFS is that the loss of any vdev will mean the loss of the pool, so your striped vdev should be in its own pool that you don't mind losing.

you can install dockge in truenas and then all your docker data is not "locked" inside their application data