Serein

Is there a chance of adding restic to this plugin?

Did you ever try this out? I've been attempting to set it up but can't seem to get all the docker variables correct.

Having this same issue. Often will take so long on a manual search (er, "interactive search" as it may now be called?) that the browser page goes unresponsive.

Yeah it's just for home use, likely not even any VMs in the short-term, just purely storage for the time being (planning on 1 parity drive and 5 storage drives). That's what I was thinking about the e1000e driver being updated to, or the newer kernel. If there was a way to run the newer driver in 6.8.3 would that be a good idea? Or would the newer driver possibly rely on something in the updated kernel and not function on the older one? I've also had issues in the past (with other software, not Unraid) where moving from beta/rc versions to stable requires resetting certain things. Is that something I would need to be concerned about?

Hi all. I just recently completed my build that I'm gonna be using for Unraid, at the recommendation of, well, many people. Will be using it to replace an old Synology DS410. But I'm running into some issues during my initial setup. The motherboard is the Asrock B460 Pro4, which has the Intel 1219V NIC built-in, and I have no PCIE network cards and no wifi chip installed, so that's the only network connection in the system. I know the hardware is functional because I have tested it with a bootable Ubuntu flash drive, and it can connect to the network just fine and see/be seen by other machines. However, when I use the Unraid flash drive (using the Sandisk Cruzer Fit, the usb 2.0, 16gb version I saw recommended somewhere on this site), I get the error that the IPv4 address is not set. I've tried both DHCP and Static IPs (adjusting the router settings accordingly), and on DHCP it will always say not set, and on Static it will show the IP I give it in the network.cfg file (or via the USB Creator, have tried both ways), but then it can't even ping the gateway or anything else on the network, and no other machines can reach it. I've tried turning off/on bonding/bridging in every combination, etc. and it's always the same result. The same Unraid flash drive in my laptop booted up and started working right away, so I know the flash drive is fine (and I've tried multiple usb ports, including 2.0 and 3.1, on the new machine). So, here's the weird part. All this testing was done with the stable build, 6.8.3, because I'm new to Unraid and that makes the most sense to start with. At the recommendaiton of some support threads, I tried the "lsmod" command on my 6.8.3 build, and it doesn't show the e1000e module that seems to be the driver for the 1219V NIC. However, just to try it, I decided to load up the 6.9 beta 22 build, and it worked right away. Running the "lsmod" command on it does show the e1000e module loaded, and I've tested it working with both DHCP and Static IP with no issues. But as I'm completely new to Unraid, and beta software is beta for a reason, I assume I shouldn't setup and run a brand-new array on 6.9 beta 22. It seems to me that I should just have to tell the 6.8.3 version to load the proper driver and it would start working, but I've kind of exhausted my abilities at this point. I know from reading other support threads here that the diagnostics files are useful for people, so I took one off the 6.8.3 stable (where network is not working) and another from the 6.9 beta 22 (where network is working). Thank you for anyone who can help! cayenne-diagnostics-20200622-1246 (version 6.9 beta 22).zip cayenne-diagnostics-20200622-1248 (version 6.8.3 stable).zip