BRiT

If you want real fun, when you're done with the .bat version, port it over to powershell.

Wonder if user mentions work at all... @jonp @SpencerJ @limetech @Squid @trurl ...

Tapatalk is entirely a different set of problems, but this latest isn't one of them.

And here I thought everyone just figured out how to solve their own issues and no one needed to reply or post new topics.

/var/log/ is is RAM. It will all be removed on reboots. Since it's in memory, the more you store the more it uses. If you don't have enough memory it will lead to OOM - Out of Memory errors and the kernel will pick randomly what programs to kill.

Not sure how this would be any faster than that. This: 1) reading entirely from disk to memory 2) writing from memory to cache 3) reading from cache to memory to be used That: 1) reading entirely from disk to memory to be used. Probably bigger speedup would come from increasing your server's memory.

If I followed properly ... From the other thread about Nvidia, there are many extremely time consuming tasks still required to be sorted, like the OOT WireGuard drivers. Not to take anything away from the amazing efforts of CHMB and LSIO, but to appease those who need to be on latest and greatest ... I will once again suggest those who can to go ahead and replace your DVB hardware with ethernet based tuners or use your USB based Tuners on a RasPi device and expose them that way. This way you will be able to use mainline unRaid.

Only thing shown in there was your 3 VMs using cpu. When you see spike CPU, run htop or top at the linux prompt to see what processes are using cpu. top - 22:04:15 up 14 days, 8:08, 0 users, load average: 2.95, 3.79, 5.87 Tasks: 634 total, 2 running, 630 sleeping, 0 stopped, 2 zombie %Cpu(s): 2.2 us, 2.8 sy, 0.0 ni, 95.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 32196.3 total, 2019.7 free, 26162.6 used, 4014.0 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 4918.6 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 8316 root 20 0 9354092 8.1g 19204 S 82.4 25.7 14356:40 qemu-syst+ 10128 root 20 0 9265796 8.2g 21072 R 76.5 26.2 12721:27 qemu-syst+ 8745 root 20 0 5066388 4.2g 21120 S 35.3 13.5 8788:36 qemu-syst+ 7679 root 20 0 6924 3264 2316 R 5.9 0.0 0:00.02 top

I have not tried enabling it in 6.8.1 since none of the release line-items looks like anything changed related to this.

This bug where WSDD for Samba Discovery pegs 1 CPU core at 100%:

Because there will be some users on the forums who ask for it and / or demand it. The same way they need to have bleeding-edge docker versions, they will act the same way with these drivers. *shrug*

Upgraded from 6.8.0 a few days back without issue -- still have WSDD disabled, have not tried to see if it's still a CPU HOG or not.

And then be forced to update unraid releases whenever Nvidia puts out new drivers? Sounds like plenty of extra work for LT.

Wouldn't it work if you schedule it to do increments with the pause time to be before your Duplicati Backup is scheduled to run? This was the only item related to parity I saw.

Parity Check Tuning. Search for "parity" in the excellent Community Applications plugin "Apps" section. Support Thread: https://lime-technology.com/forums/topic/78394-parity-check-tuning/

Direct consumer review from the 1-to-2 SATA Cable and the 4 SATA Cable variants of the product you linked:

Be extremely careful when using power splitters. some models are very prone to being garbage and ruining your drives after catching fire. There's more details in a thread somewhere in this forum that goes into what exact style you want and what you need to avoid like the plague.

And I hope I never need to. 😝

That just means you wont get updates, but depending on what you need to do a job, it still might be suitable, like if you only need an environment to write scripts that would be enough. But being likely large changes from 11.3 to 12.1 I can see that not being enough for production level. Ah yeah, might be nearly impossible to install over versions if they don't have the old media available anymore.

In the UI settings for Docker? You first need to stop Docker in order to be able to make changes there. Maybe also changes in any particular mappings for RADAR to use /mnt/cache/ for temporary paths etc.

And you can't use a version of FreeBSD that worked before?

I think he's saying to set it as /mnt/cache/appdata instead of /mnt/user/appdata.

Perhaps a silly request or a sign of being truly lazy and not wanting to have to remember which screen to navigate to in order to do the next step of the Update process ... Can we have the Reboot Server option on the Update OS screen after updating the OS? It already indicates a Reboot Is Required, so why not let that be done from that page as well?

Have you tried reverting changes to your network.cfg file on the flash drive? I think there's been a few posts in here detailing that. If you want community help you're probably going to have to post full diagnostics zip file to your next post.

Turn them off? Maybe use the builtin send notification functionality first? Would be nice way to have then generate the popup or email or log it in syslog.