LXC Startup Issues after Host Reboot (SMB Dependency) & TrueNAS VM Storage

[tzagor]

Hello Proxmox Community,

I'm facing a significant challenge with LXC containers failing to start after a Proxmox host reboot. My LXCs depend on SMB shares mounted on the Proxmox host.

I'm seeking advice on two related points:

1. Reliable LXC Startup with Network Shares:
   
   Is there a more robust and native way to ensure LXCs only start once their required network mounts are truly active on the host, particularly given post-reboot timing complexities? The current hook script approach isn't proving foolproof.
2. TrueNAS VM Storage Integration Best Practices:
   
   My storage originates from a TrueNAS VM running on the same Proxmox host. Currently, I'm mounting SMB shares from the TrueNAS VM onto the Proxmox host, then bind-mounting these paths into my LXCs. I'm looking for more reliable and performant methods to integrate storage from this TrueNAS VM into other LXCs/VMs on the same Proxmox host.
   
   • Would switching to NFS from TrueNAS be a better fit for Linux environments compared to SMB, offering greater stability during host startup and reboot?
   • Are there other best practices for tight, reliable storage integration when the storage provider (TrueNAS) is itself a VM on the same Proxmox server?

My goal is to achieve reliable LXC startup and a robust, performant storage solution. Any insights or recommendations would be greatly appreciated.

Thank you!