To everyone who has problems accessiing ZFS throught samba shares. I have a solution which works for me but its sounds realy stupid:
I mounted my Pool Tank at /mnt/Tank and created a fs at /mnt/Tank/Share
PS: If someone has a better fix to this then pls let me know
having just moved to Un-Fun-Raid yesterday, I managed to knuckle my way around this issue as it drove me nuts for 12 hours straight. (no I am not kidding)
(I've seen two others post about this issue, no one seems to respond with how.. so here goes to help!
Keep the array started.
1) Terminal - Make sure the mounted ZFS folder (in my case 3 of them, SSD, Seagate and Western) were all write access. (view this with a " ls -l " command)
a - Root:Root for the Owner and Group, but you will need to " chmod 777 " the folders (mount points) themselves to enable everyone have read/write access.
2) Make a share in the web-UI of the same name to my mounts. (it will allocate the folders to the array, I know, we will edit it)
a - Set the users/permissions and settings you wish to use for the folder
b - (Be mindful here, as it will create additional config files in your /boot/config/shares folder, these reflect the unraid array shares but will be destroyed later to prevent conflicts)
3) Continuing within the UI, using the plugin 'Config file editor' go to the tools tab to Config File Editor and then using the right side file list navigate your flash storage to: " /etc/samba/smb-shares.conf " and click the write symbol next to the address you entered. it will present you with all your folder shares.
a - highlight the content you want, copy it to a notepad/texteditor and save it (just incase) Example of mine.
[SSD]
path = /mnt/SSD
comment = VM / Docker
browseable = yes
public = yes
writeable = no
write list = administator,synology
vfs objects = catia fruit streams_xattr extd_audit recycle
case sensitive = auto
preserve case = yes
short preserve case = yes
recycle:repository = .Recycle.Bin
recycle:directory_mode = 0777
recycle:keeptree = Yes
recycle:touch = Yes
recycle:touch_mtime = No
recycle:minsize = 1
recycle:versions = Yes
recycle:exclude = *.tmp
recycle:exclude_dir = .Recycle.Bin
4) Remove those shares, and stop the array
a - (At this point the excess files from point 2B above should be eradicated, any files in there NOT concerning the unraid array, delete them. we cannot have ZFS share configs in this /boot/config/shares folder)
5) Goto your settings tab, SMB, and paste that information into the SAMBA EXTRA CONFIG area, I've put mine above all the other commands there.
Notice I have edited my path directory to reflect my mount point
Save/Apply button and SMB will save the config.
at which point, goto your dashboard, the SAMBA service will ignite and your ZFS shares should be there, ready and waiting to be written.
Hopefully this works for you, I was screwing around with mine for ages and if I missed a step then I apologise, once I got it working I just had to goto bed at such an obscene hour.
Might make a youtube video of it for my endeavours to help others and show them how to use a ZFS array on unraid, the level 1 techs guide and Gamers nexus video is nice but is not a step by step by a long shot.
ZFS plugin for unRAID
in Plugin Support
Posted
having just moved to Un-Fun-Raid yesterday, I managed to knuckle my way around this issue as it drove me nuts for 12 hours straight. (no I am not kidding)
(I've seen two others post about this issue, no one seems to respond with how.. so here goes to help!
Keep the array started.
1) Terminal - Make sure the mounted ZFS folder (in my case 3 of them, SSD, Seagate and Western) were all write access. (view this with a " ls -l " command)
a - Root:Root for the Owner and Group, but you will need to " chmod 777 " the folders (mount points) themselves to enable everyone have read/write access.
2) Make a share in the web-UI of the same name to my mounts. (it will allocate the folders to the array, I know, we will edit it)
a - Set the users/permissions and settings you wish to use for the folder
b - (Be mindful here, as it will create additional config files in your /boot/config/shares folder, these reflect the unraid array shares but will be destroyed later to prevent conflicts)
3) Continuing within the UI, using the plugin 'Config file editor' go to the tools tab to Config File Editor and then using the right side file list navigate your flash storage to: " /etc/samba/smb-shares.conf " and click the write symbol next to the address you entered. it will present you with all your folder shares.
a - highlight the content you want, copy it to a notepad/texteditor and save it (just incase) Example of mine.
[SSD] path = /mnt/SSD comment = VM / Docker browseable = yes public = yes writeable = no write list = administator,synology vfs objects = catia fruit streams_xattr extd_audit recycle case sensitive = auto preserve case = yes short preserve case = yes recycle:repository = .Recycle.Bin recycle:directory_mode = 0777 recycle:keeptree = Yes recycle:touch = Yes recycle:touch_mtime = No recycle:minsize = 1 recycle:versions = Yes recycle:exclude = *.tmp recycle:exclude_dir = .Recycle.Bin4) Remove those shares, and stop the array
a - (At this point the excess files from point 2B above should be eradicated, any files in there NOT concerning the unraid array, delete them. we cannot have ZFS share configs in this /boot/config/shares folder)
5) Goto your settings tab, SMB, and paste that information into the SAMBA EXTRA CONFIG area, I've put mine above all the other commands there.
Notice I have edited my path directory to reflect my mount point
Save/Apply button and SMB will save the config.
at which point, goto your dashboard, the SAMBA service will ignite and your ZFS shares should be there, ready and waiting to be written.
Hopefully this works for you, I was screwing around with mine for ages and if I missed a step then I apologise, once I got it working I just had to goto bed at such an obscene hour.
Might make a youtube video of it for my endeavours to help others and show them how to use a ZFS array on unraid, the level 1 techs guide and Gamers nexus video is nice but is not a step by step by a long shot.
Hope it helps.