Marshalleq

Thanks, out of interest, are the ZFS versions built from master? I was reading that 8.4 wasn't supported on kernel 5.7 unless it's build from latest master. Though I can't personally confirm that myself other than the 8.4 page says supported to kernel 5.6.

OK, so OpenZFS from here 0.8.4 is not supported on kernel 5.7, so you're using master branch. Master branch is newer? but has older version number. I have to say, that was unexpected, but thanks for clarifying!

Yeah - I realised that the first time I built your container, I built it on the ZFS plugin, so I need to shift between the two. But as I said before the primary reason I started using this (and promoted it) was because we could built it ourselves for beta releases and not have to annoy developers to do it for us. I thought this would make it a lot easier even if parts of it we had to do manually. It's an amazing step towards that, I guess we may see optimisations come out over time. And for the NVIDIA plugin it's a giant leap over what was available before.

I'm currently using this plugin on 8.0-1 . I'm not really concerned with 'trusting it' given ZFS itself is not in beta. @steini84am I reading right that your ZFS version is 8.0-1 when the latest stable is 0.8.4? And interestingly your plugin says it's on 8.2. This doesn't seem right. # zfs --version zfs-0.8.0-1 zfs-kmod-0.8.0-1 cat /sys/module/zfs/version 0.8.0-1

I think it would be a simple matter of pointing your container at their download URL like you do for all other things the container uses though right? Yeah, it will be great if they add those things in - I strongly suspect there will always be a need for a community kernel you can compile yourself though, differing versions of things for example is one area only your container handles. I expect, none of these are going to be fast though. Quite excited to see PAM mentioned in the logs too.

Hmmm, so I just went to do this - my docker runs on ZFS and apparently I need to have installed (or otherwise gotten) the new kernel first. Since docker doesn't start without ZFS for me, I can't build the new kernel. I'm sure there's a manual download somewhere I will try use that - but have a feeling there's some optimisation portential for the container here somewhere... Possibly I could install the other ZFS plugin, in order to build this ZFS kernel lol. Seems backwards but it'll work I'm sure - probably easiest thinking about it.

I see beta 22 has been released here: So when I get a chance, I will install it / compile for it. Won't be able to try for another 4 hours at least though - @ich777 it will be interesting to see if this container handles it already or needs changes to make it work.

Persistent l2arc! I hadn't noticed that! It will be a great feature - I'm running the non-persistent one on an NVME drive and it does make a huge difference for VM's and such - actually combined with a decent L1Arc makes VM's and dockers on mechanical HDD's very usable again. ZFS sure is magic.

Hey, welcome - I think QAT is built into ZFS since it was released in 2017 in the ZFS changelog, but also needs the QAT driver - which as far as I know is not included in the linux kernel (though you could just try that first). But unlike freenas, thinks like this are usually a bit easier in unraid. I'd suggest having a look at the community kernel and have a go at building the driver in there. The dev is quite helpful too, so I'm sure he'll give you some tips. Maybe, just maybe, he'll even include it as an option automatically since it's probably common to all INTEL processors and gives a performance boost.

Very nice plugin! I think I have some ideas to expand on the ZFS section too.....

I CAN subscribe to ZFS being more polished in freenas from a user interaction perspective (assuming you don't do console). I CAN'T subscribe to ZFS being more stable on freenas, there is nothing unstable about this plugin at all, in fact I'd say with absolute confidence it's more stable and robust than all other filesystems existing natively on unraid today. And if you like you can even run this in native kernel now anyway, not that it makes a difference to the stability of it. @steini84 has done an amazing job of bringing us a stable and robust option with this plugin and it has saved me a number of times already. I am extremely grateful for it. If you have some evidence around how ZFS on unraid is not stable, I'd certainly like to know about it so that I can re-asess my options. Thanks, Marshalleq

Yes that's good advice when playing with kernels - (they're in /boot BTW).

@JusI think it's important to add, it's extremely unlikely a new beta build or kernel update will lose data. By the time the kernel get's to unraid there's probably millions of people have used it and anything serious would be known. And in this case, the current unraid beta has been out for a very long time, so you're good. There's always a risk (hence the disclaimer), but it's a very very low risk. If you don't really understand this stuff, then I'd suggest using the prebuilt kernel mentioned above on any system that's in-use.

Perhaps with this docker, I can begin to manage that.

That's kinda the main reason I'm interested in this, is for beta builds. I was hoping this would autocompile against those newer kernels. I like not having to rely on others to get an update.

Actually, there's the home gadget geeks interview on the front page of unraid was an interview with Limetech - in it Limetech says they're really considering ZFS, (or something along those lines). He pretty much indicated it's in the works, which is very exciting. It would be great to get an official version.

Hey all, just thought I'd post that we are super lucky because we now have two methods of getting ZFS support in Unraid. 1 - This plugin, which has served us well (and I have to say, the ZFS developer has been both super responsive and amazing) 2 - And now an interesting alternative via a new community kernel method here. There isn't any difference in the ZFS capability, mainly it's just that you don't have to wait for the developer to update plugins when a new unraid version comes out. Obviously that's not really a big deal for ZFS since the developer is super responsive, but I always feel bad for asking! However, this kernel also builds in support for Nvidia drivers and DVB drivers, Nvidia at times was hard to get updated for the latest Unraid release, so this works around that, especially nice for testing against beta versions. I'm running it to try it out and it works well for me so far, thought I should share. Thanks, Marshalleq.

Hey, @ich777 thanks so much for the ZFS support, now when new kernels come out, I don't need to wait for any other devs to compile nvidia / zfs etc which is fantastic! And the ZFS works the same as the other ZFS plugin, so can switch back and forth if I so desired, but probably just going to use your version now, thanks!

Yes of course, add them to the top - no need to ask! Samba is here https://github.com/samba-team/samba The ZFS code that steini uses is at https://github.com/Steini1984/unRAID6-ZFS ZFS is the main one I'm interested in right now though. Steini's ZFS is for a plugin though, so I'm not sure what that means, I expect he'd be keen to help though, he's great like that. I'm quite sure there's a huge win in this for him (not having to compile the code each time himself) and us (not having to annoy him and wait to compile it for every beta version). This is a key advantage really, we're usually at the mercy of others when it comes to testing kernels in the rc path steini is very good, but others have refused at times. Thanks again, this docker is amazing!

Finally! Amazing! Thankyou! I dub thee, the official community kernel! Items on my wishlist to include are: The awesome ZFS plugin from @steini84 - he has previously published all the build scripts and while he's. always very accommodating to build a new version for us, it would be amazing to link the two. NFS updates Samba updates Tips for anyone else first doing this that I didn't know: The build process begins as soon as the docker starts (you will see the docker image is stopped when the process is finished) Use the logs. The whole process status is outlined by watching the logs (the button on the right of the docker) The image is built into /mnt/cache/appdata/kernel/output-version by default. You need to copy this to /boot on your USB key manually and you also need to delete it or move it for any subsequent builds There is a backup copied to /mnt/cache/appdata/kernel/backup-version. I would copy this to another drive external to your unraid box, that way you can easily copy it straight onto the unraid USB if something goes wrong. As a guide, the whole process took about 10 minutes on my Threadripper 1950x (32 threads). The actual compilation of the kernel seemed to be about 1 minute, so clearly there's a lot of other things going on. Hope that helps someone.

All good and thanks so much! I'm so tired of cloud mail. Finally realised how to get around the lack of PTR on home ISP's. Amazing what happens when you sit down and actually work stuff out! Marshalleq

Thanks - yeah in my original it says Imap - but recognise easy to overlook, you have a huge job responding to all these requests! Many thanks for the info, will check it out! Marshalleq

I was more thinking along these lines: https://www.nginx.com/resources/wiki/start/topics/examples/imapproxyexample/ Apparently nginx needs to be compiled with special support for the mail directive.

Hi all, anyone know if the lets encrypt container supports the mail directive? Am trying to use it to proxy imap and smtp. Many thanks.

Yeah, I'm finding I'm just outgrowing the unraid docker GUI. I need to to create multi-image containers and such. Trying to install something as 5 separate containers when unraid has little ability to offer any dependency mapping is a nightmare. Especially during updates. As far as I know, it can't work. So docker compose solves it apparently. But, for some reason it's been pulled from nerd pack, I'd certainly vote to have it back rather than have to use some bodgy script to keep it running.