steini84

Its done, thanks

I have moved the 2.0.1 builds to the unstable folder for now. #Enable unstable builds touch /boot/config/plugins/unRAID6-ZFS/USE_UNSTABLE_BUILDS rm /boot/config/plugins/unRAID6-ZFS/packages/* #Then reboot #Disable unstable builds rm /boot/config/plugins/unRAID6-ZFS/USE_UNSTABLE_BUILDS rm /boot/config/plugins/unRAID6-ZFS/packages/* #Then reboot Please let us know if you are running 2.0.1 without issues and better yet if the conflict reported by Marshalleq has been identified / resolved

You can use smb-extras.conf[emoji108] Sent from my iPhone using Tapatalk

I tried on both 6.9.0-rc2 & 6.8.3 and get the right version after a reboot. I have only ran it on my test server and have not seen anything strange. But to be honest I only run zfs on that install and nothing else going on there. Sent from my iPhone using Tapatalk

Built zfs-2.0.1 for 6.8.3 & 6.9.0-rc2 If you want to update zfs versions you have to remove the old cached version rm /boot/config/plugins/unRAID6-ZFS/packages/* And then restart the server Sent from my iPhone using Tapatalk

Sorry guys, did not see that update. Will build now Sent from my iPhone using Tapatalk

Im still on 6.8.3 but will see whats going on on my build server tomorrow Sent from my iPhone using Tapatalk

No I just wish all my standalone dockers and vms could stay up even though the array was stopped. But to be fair I really seldomly have to mess with the array. But I don't think this is really a problem though. I have had this running over 5 years now without a single hickup and 0 bytes in data loss. And with the daily zfs replication I had 3 months of daily backups I could go back to if I needed any old configs etc. My point being this started as a way for me to make the perfect setup for me and I'm happy that it has helped others. Funny to look back at the beginning and seeing the first

Just to be clear I meant for example plex in a docker accessing /mnt/user/Movies I keep everything zfs under /mnt/SSD including docker.img libvirt.img, vms and docker data without problems. I just was talking about media that is shared inside the vms/docker from /mnt/user/ eg music movies or tvshows Sent from my iPhone using Tapatalk

zfs 2.0.0 build for 6.9.0-rc2 is up. Thanks to @ich777 for the build server!

I agree, but it makes it a bit difficult if you are passing through Unraid storage to the VM or Dockers. Maybe there could be made a change to the KVM/Docker service and allow to run Vms/Containers that are not dependant on anything in /mnt/user even if the array is off. That would indeed mean that Pfsense/Homeassistant etc. could keep running even if you had to do some maintenance and stop the array. I guess there is more to this and how the network stack etc is set up. But if there is a will there is a way. My hope is that the native ZFS that is "Comin

Yeah sure I’m up for that [emoji3060] But yeah that process will get you on zfs 2.0 if you have not already updated to that in 6.8.3 Sent from my iPhone using Tapatalk

Yes. But to be clear I don’t update the plug-in every time I make a new build, only when I need to change the way we load the zfs modules. For example recently with the addition of overlayFS There has not been a change to the plug-in since November, only new builds: https://github.com/Steini1984/unRAID6-ZFS/commits/master Sent from my iPhone using Tapatalk

Built ZFS 2.0.0 for Unraid 6.9.0-rc1

Correct