I want to use a remote WD NAS storage as volume within Trunenas (scale), so I did set a nfs share on the WD NAS and mounted it on Truenas through an init script. It is persistent and can RW from Truenas shell.
Next step : I was expecting this volume to be listed as disk, but it isn’t. Do I miss something there ?
NFS Shares are not disks. Nor are they ZFS pools - so they will not be listed in the UI.
I am not sure whether they would be mountable with a Host Storage mapping in an app - you would need to try it and see.
But if you were sharing an iSCSI disk from another server on your network and you mounted that in an init script, then that might well be seen as a “disk” and be visible in the UI.
But in essence TrueNAS is a network storage server dedicated to sharing its own storage with other devices and not designed to make use of storage shared by others (though the underlying O/S is Debian which can still be a network client).
I’m not sure why you would have expected that. It isn’t a disk, and it doesn’t behave like one. An iSCSI extent would behave more like one, but TrueNAS doesn’t support mounting remote iSCSI extents either.
Thanks for answering. I agree it’s not very useful … I’ve read here and there people complaining about fstab being non persistent and found this workaround using an init script, and it works.
But reading your statements, now, I don’t get why those people are complaining, as it’s anyway impossible to use this mounted volumes from within Truenas …
Within TrueNAS itself, yes. Within apps (under 24.04), not necessarily. The iX apps don’t directly support mounting a NFS share the way the TrueCharts apps did (they do support SMB shares, though), but you could still point a host path to the mounted NFS share. It’s kind of ugly, but it should work. I have no idea what if anything 24.10 will change in this regard, though. But at the end of the day,