BRiT

As I have said in the past, we should have gotten multiple array support long before any and all of those. I'd gladly have traded the order of features added to move multiple array support earlier. Stop being silly goose, I am not proposing to use a time machine to change the past nor to remove features, just proposing to focus on NAS features. Once its added then go for the fringe cases.

I am not confusing anything. I'd rather even just 5 minutes of LimeTech time be spent on genuine NAS functions and features than on any and all GPU-related work.

I'd rather Limetech focus their limited development efforts and time on NAS functions and features. Sure, if they had unlimited time then include everything. Alas, that's not reality.

Well over a long enough timeline, the need for transcoding has gone down. When media streaming was first making the rounds, every server had to transcode for the clients, like back when Xbox Media Center was actually run on original Xbox hardware with hacked setups. During that time, any media over 480p generally had to be transcoded. You used to need transcoding for anything in MKV containers, then codec of x264, then x265. Then as time went on, clients became more capable and now you really don't see a need for video transcoding of 1080p even with x265. Of course new media formats and resolution always push against this, but then after it becomes more mainstream, the clients will adapt. As you said, right now the bleeding edge push is 4K and 8K media with HEVC. The encoder for HEVC is insanely slow, so I don't see it proliferating until the encoding times are addressed.

As time goes on, there will be less need for video card specific features, not more in a NAS server platform. Upgrade your clients and you wont have a need for transcoding which removes the need for this Nvidia build.

Since you seem to still be posting comments about this, let me recycle my previous comment or give you a pointer to all the dejavu stuff.

DejaVu. We've already discussed that in this thread.

Every time there is a change to what's configured and included has an impact on what's required to create the custom distributions such as Nvidia and DVB. This includes the kernel version, the drivers and especially out-of-tree drivers, and additional patches. Fortunately, some tiny part of this is mitigated as Limetech generally does a good job of including what additional patches they apply. however, if a new patch is added then the fine folks at LinuxServer.IO have to be aware of it and be certain to include it in their build. It's very easy to overlook new items, especially if you attempt to have your builds mostly automated. I used to run a permanent persistent install on HDD of unRaid, but the task of doing all this was taking too much of my time.

Yes, requires more time and effort.

Upgraded and rebooted after having to navigate to another page just to reboot after the update finished. 😉 So far so good.

I'm not certain of the parameter on the parity check, I know it's NOCORRECT for non-correcting parity check, so I'm guessing it's CORRECT for correcting parity check. # get the week number of the year without any padding weeknumber=$(date +%-V) # see if it's an even multiple of 4 by using modulo arithmetic, 0 means multiple of 4 forthweek=$((($weeknumber)%4)) if [ "$forthweek" -eq "0" ]; then # invoke parity check here /usr/local/sbin/mdcmd check CORRECT &> /dev/null fi

Somewhat expected, depending on how you "transfer content" from one share to the other. Mover does not move files from cache to disk for shares set as use cache: no. Mover does not move files from cache to disk for share set as use cache: prefer.

Update the firmware on your router and change your netgear and router username and password. They (netgear) have been hacked multiple times so anyone using the cloud features on their firmware are at severe risk.

Probably need to do the following 2 steps. Watch out for the second step, it's a dozy. 1. Disable parity check schedule. 2. Write your own custom bash script scheduled to run every Saturday. Inside this custom script, determine the week of the year and if divisible by 4 then kick off a parity check, otherwise exit. Hint for day of year (ISO, Monday start, 01-53) /bin/date +%V

Easier to use the user.scripts plugin to manage customizations than to modify the go file. Search for it in Community Applications.

Validate this, but one trick I recall is ... Dont assign anything as parity. If you assign all drives as data then any old parity drive(s) will likely say unknown filesystem and can't be mounted. However, if you assign a data drive as new parity it will begin overwriting it immediately and your old data will be lost.

Using separate router/firewall and access points is the way to go. You get the ability to upgrade and scale the WIFI portion as needed without having to redo/replace the router. Getting a ubiquity or mikrotik router should serve you well, being able to handle Gigabit or even multi Gigabit ISP connections. Price wise, it's not even more expensive compared to the higher-end consumer wifi all in one routers. Using dedicated router and separate WIFI APs was the best upgrade I ever did for myself, my parents, and sister's family.

Also, you can't really go wrong with getting more capable and performant client hardware.

From the command line or from the UI showing the usage. df -h /var/lib/docker

Was that you using insmod directly? Use modprobe instead. And use lsmod to see what is loaded. That SFC module loaded fine for me using modprobe. Of course I dont have the hardware. Also, are you using unraid or unraid-nvidia or unraid-dvb (one of those custom community version)?

Did you try manually loading those kernel modules, at least the SFC?

Is the SFC module loaded? If not, try: modprobe sfc

The list of UnRaid 6.8.1 configuration for the kernel is located in /usr/src/linux-4.19.94-Unraid/.config and I attached it as a zip file to this post. unraid681.config.zip Maybe you need to load some modules? It has the following specified -- CONFIG_NET_VENDOR_SOLARFLARE=y CONFIG_SFC=m CONFIG_SFC_MCDI_MON=y CONFIG_SFC_SRIOV=y CONFIG_SFC_MCDI_LOGGING=y CONFIG_SFC_FALCON=m

TLDR: It's complicated. It is impossible for any company to know the exact state of support for all hardware as it is possible for bugs to be introduced on newer versions of the Linux kernel that could break hardware support, or a hardware company could stop supporting Linux entirely or not bother to port their hardware drivers to newer kernels. So many things can happen that is outside the control of LimeTech. A solid positive and benefit is LimeTech supplies trial versions so if you have the hardware already and are uncertain about hardware support you can try it out before hand.

Emby has DVR support included for some tuners (HDHomeRun ?) but dont know if that requires premium or not.