Marshalleq

For within your network, it's likely best to create a static DNS record, with the same domain name you're using and point that at your INTERNAL nextcloud / unraid address. So: Unraid needs to have the correct IP for the domain Cloudflare needs to have the correct IP for the domain The proxy setting in cloudflare should be off You need to give it time for the new cloudflare setting to propagate to the DNS servers on the internet (which will include the DNS server at whatever phone provider you are using AND the DNS server that your home router is using) Internal devices either need the internal DNS updated or some router trickery which you may or may not have, which is why I suggest adding this manually for now If you can't figure out how to do this in the router, for testing purposes you can test by just pastin the internal unraid / letsencrypt IP and DNS record into your clients hosts file. Be sure you clear the DNS cache on the local client each time you change this as it will always remember the last setting. Hope that helps.

With this I found I had to be carefeul - just because it's returning the right address on one machine, doesn't mean it's returning the right address in all cases, and if it's not, it won't work. Cloudflare is pretty good with speedy DNS updates, but I found I had to wait for this particular change. Are you pinging from the server or the client? Also, I assume you're testing via some external internet connection such as tethering through your phone? If so, checking that IP address pings correctly is important. At this point I'd suggest looking at the active logs of both the letsencrypt docker and the particular app you're going to e.g. nextcloud wihtin the appdata directory or equivalent. I found I could see issues in there fairly easily. Also the logs in the GUI of the docker container on the docker page in unraid.

Yes, it was rather frustrating this one! I'm sure between the two of us we can get you sorted.

Hey, I don't use duckdns because I have a fixed IP, but I have got Nextcloud running. I had this issue at the beginning too. Also, the LuaJIT / restycore error at the end of your letsencrypt log is apparently perfectly normal (I think it's just a docker issue and I have it too), so don't worry about that. What I suggest you do is turn off the 'cloudflare proxy' setting for any non-working cname. I'm not actually sure how duckdns works, but to start with I'd suggest you also turn of any cloudflare proxy setting to do with duckdns set up as well. You can gradually turn them on later to test which ones work. I found some apps are OK, others are not. I found I got a 'too many redirects' error with this turned on - and if you're using duckdns it's probably going to be even more redirects. Also, I found I had to wait quite some time (up to a day maybe) after turning this off for it to take effect. The proxy feature hides the IP address of the real host by providing a cloudflare one, then redirecting it. I've read that enabling strict HTTPS can help this issue, (as normally it only occurs when using https, which everyone either does or should now). I suspect this will get you working, then if you ever manage to move that forward more so that you can get the proxy enabled as well, please let me know cause I haven't managed to yet! Also, don't worry about turning off the proxy setting too much - this is the way most people run their DNS - it's a great feature but not absolutely necessary. You'd be better spent ensuring you have a real firewall installed like OPNsense or similar. Let me know if you need any more help and good luck!! Thanks, Marshalleq

Awesome. BIOS didn't work for me unbelievably, so glad it did for you as that's even better.

From my experience, the only way to disable it and have a working system afterward is to stub the eth0 pci device. I personally think the networking config when it comes to this type of procedure needs some serious improvement in unraid as it just doesn't do what you'd think it would. That said, other people don't agree with me, but I don't think they were listening properly either, so depending on your experience I'd be the best or worst person to help you with this. lol. But yeah, for a dead device anyway, just stub it so it never shows up, then probably delete your network config file to reset the networking stack. That's where I'd start.

Answering your question, it should 'just' work. Which version of unraid are you running? I'd suggest you try either 6.6.7 or the 6.8 rc series. The latter being newer so maybe things are fixed, the former being the most stable and also older in case something broke. You could try the 6.7 series but I wouldn't recommend making that your daily driver due to the raid storage bug in it. Then, for whichever case is interesting, post your diagnostics back here.

Update for me on 6.8 - so far, the HDD based read errors have gone in 6.8. Which would be amazing, and preferable to whatever else could have been going on with my disks / cables or controllers. Normally by now I would have had one or two of them. Also, the unsafe shutdown count which was appearing on my brand new enterprise SSD with power loss data protection under 6.7 seems to have stopped counting. I'm quite sure now that 6.7 was somehow killing my SSD's. Again, time will tell if that problem has gone. So all for the positive on 6.8 so far.

In case it helps, my Mac OS also exhibiting strange behaviour. I can actually go to the share the first time, but second time it doesn't show up as mounted in the GUI, only if I go via console. Haven't fully had a look at it yet, but thought it might help with the thinking. On RC3 and RC1 though.

Well, the below is what I get when I ask for version. So yes.. I'm quite new to ZFS, but the package maintainer of this plugin is very speedy with updates and such. Plus you get the advantage of being able to have a flexible array with unraid on the side. The big minus with unraid is that nothing with ZFS has a GUI as it's an unofficial plugin. But unofficial plugins with unraid are not as unofficial as they sound really, the way the product works, it is very inclusive. Good community and good developers. I've considered freenas a few times, but I think for me unraid is mostly better - especially since I discovered ZFS! Also, the developer just packaged znapzend which makes things a bit easier. # zfs --version zfs-0.8.2-1 zfs-kmod-0.8.2-1

Quick question, does mbuffer path need to be specified, or is it included and compiled in somehow? Thanks.

Installed, configuring and very happy you've taken the time to create this! Thankyou very much @steini84. Marshalleq

Fantastic, thank you. It's hard reading all that ZnapZend documentation isn't it - getting used to all those replaced S's. Especially outside of the US where we use S instead of Z a lot lol.

So does that mean I can upgrade unraid to rc3 and ZFS will keep working, or does the same kernel need to be assigned to the RC3 version of zfs so that it activates post upgrade?

I just discovered Zvol's. Oh boy. And this on an NTFS formatted block device: INTEL1TB/virtual_machines/zvol_test refcompressratio 170.22x Soooo good.

I've just looked up ZnapZend, yes please that would be fantastic! It's kind of a major point for ZFS I'm struggling with - but even so at the moment I can do it manually - which is cool. Thankyou!

Hello again all, I've been trying to get autosnapshot working as per page 4 of this post, but have had no end of issues. It may be the new version of unraid I'm not sure. For example, the update_cron command doesn't seem to actually update cron i.e /etc/cron.anything or crontab -e - I didn't know unraid could support custom cron - I thought that's why the user scripts plugin was made. Manually running the cron script says that the file it's referencing doesn't exist, even though I can see quite clearly that it does exist. So I suppose that's due to permissions, which are -rw------- 1 root root 16937 Oct 19 12:17 zfs-auto-snapshot.sh - however I can't actually change these permissions as root doing anything not even chmod 777 works - is this normal? I've not noticed this issue before, but to be honest I haven't played around in the scripts directory before. On the command line I assume the following is acceptable, ID=zfs-auto-snapshot-weekly /boot/config/scripts/zfs-auto-snapshot.sh --quiet --syslog --label=02 --keep=8 but I get permission denied which aligns with the above. I'm assuming you're going to tell me I need to fix the permissions issue - but thought I'd check in case I'm missing something obvious. I see 6.8 RC3 is already out which was fast! Thanks.

After my very recent foray into zfs plugin, it would be super great if syncoid and sanoid could be included in this pack. Anyone know how I might go about getting it added? https://github.com/jimsalterjrs/sanoid (syncoid is at the bottom).

I haven't done specific testing yet - just letting everything settle. The system does not seem to have exhibited any issues so far. Thankyou @limetech, I know this was a challenging one. I do have the below recurring error in the log, which I assume is unrelated and may have existed prior, but hard to tell. It does have an open kernel.org ticket. Oct 14 15:37:07 OBI-WAN kernel: pcieport 0000:40:03.1: AER: Multiple Corrected error received: 0000:00:00.0 Oct 14 15:37:07 OBI-WAN kernel: pcieport 0000:40:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Oct 14 15:37:07 OBI-WAN kernel: pcieport 0000:40:03.1: AER: device [1022:1453] error status/mask=00001180/00006000 [1022:1453] 40:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge

I've just installed the ZFS plugin on unraid and love it. I decided to take two drives out of my unraid array and assign them to a ZFS mirror to store important photos and documents on. This makes unraid nearly the perfect system. I agree it would be great to have ZFS cache pool. I've been bitten several times with btrfs cache and I note depsite some contrary views, the latest Unraid 6.8 rc1 changelog which confirms some of these bugs. Would be great if ZFS was included - even if only hidden under an advanced option, then among other things we'd probably find e.g. proper integration with plugins to help e.g. the scheduling of scrubs and such. Licensing doesn't seem to be a concern any more either: E.g. ubuntu and software freedom legal council Actual releases in Ubuntu and proxmox Others if you google it.

I've figured it out, like you I have been testing it by turning it off. It seems it didn't show until I turned it on, now it shows when on and off. Thanks.

Given the Threadripper 3rd Gen is only a little way off, I'd probably wait too, but I wouldn't wait longer than that. The release of Gen 3 should bring down prices of other TR's which is another decent option. I was reading somewhere intel's dropping their prices by 50%, because they have more cash in the bank than AMD and are hoping to wash them out. But the thing is AMD are making the better processors right now in my opinion - and they're future proofed too - I have x399 gen 1 board and can put gen 2 chip in it - which I might just do when people are upgrading to gen 3 and those second hand parts are on the market. Threadripper also goes to 128GB RAM vs 64 I think it is on Ryzen. i7 is 64 too, i9 128. That's something else to consider that many people don't. After that it's Xeon and Epyc I suppose. The new Epyc's sound pretty crazy too, so some old TR's and Epyc's probably going to hit the streets too.

Dear all, has autotrim been removed from this version / considered too unstable? I believe I'm meant to be able to use zpool set autortim=on <poolname> since 0.8 as per https://zfsonlinux.org/manpages/0.8.1/man8/zpool.8.html. However running zpool set does not list autotrim as a supported property. Seems we're on version 0.8.2.1 though. Maybe @steini84 can tell us. Thanks.

No problem, Unraid is pretty awesome huh.

My apologies for all the questions, is it possible to make a share with unraid into this mount? It doesn't seem possible from the GUI. I assume I'd have to use the Go file?