Kilrah

Looks like you did not adjust the min free space setting on that "Serien2" share so it still has the 10% default, i.e. 3.7TB.

Check your drives' datasheets for workload ratings.
As mentioned parity checks themselves are easy on the drives, the fact you say it takes 48h means either you have HBA bottlenecks or that the array is doing other stuff at the same time, if the latter than that'll be more "wear" than the check itself.
Also some people increase intervals once the system is "trusted", I do one every 2 months but some people do 4-6.

Notification settings.

I have a couple of 16GB 2242s I've used for various things (not unraid boot) and yeah they're always hot.

Appdata backup plugin.

Could be the image repo, but that doesn't work since there can be multiple templates in CA referencing the same repo, if it used that it'd then show "installed" on a template that is not the one you actually installed.

So the name is the most "unique" way to identify an installed template, and since 1) most people would not change it unless they really needed to (e.g. to install multiple instances) and 2) it literally does nothing but put the cosmetic "installed" flag and has no functional effect it's probably the most appropriate.

Video was before everything was ready, you can select to dedicate the whole pool size to boot in the release version. Usual problem when relying only on video content.

Video should really be removed at this point.

Set to Yes.

No. Running apps will always be doing stuff regardless of the OS, that's the whole point or you wouldn't be running them...

The RAM disk for Docker logs can reduce that a bit if it's just Docker-level logging but anything from the apps themselves will always cause usage.

Regarding CPU you can look at e.g. htop to find what apps use most of it, and choose not to use them if you think that's too much I guess...

Do you have the RAM-Disk for Docker logs plugin installed? if so try removing it temporarily

Unbind any bound system devices, make sure to disable autostart for the VMs if enabled.
Reboot, rebind, and also select the proper device in the VM template again as it might have changed.

Install Unassigned Devices Plus on unraid, enable destructive mode, clear all partitions, then format NTFS.

No because you can't have a data drive larger than parity.

If the system is trusted I would remove the existing parity drive, install the 3 new drives (1 data and 2 parity if I understand well), let it build parity (yes it'll take 2-3 days depending on activity), then replace one of the 8TBs with the old 18TB parity.

Would disable Docker, reboot, try again, if it doesn't help check filesystem on the disk in question.

The home keyboard key, not browser icon.

He's talking of the forums, some have something like this.

This.
Never recommended to pass the entirety of /mnt/user to any container anyway as it gives it the ability to wipe your entire server, only pass what you need, do multiple mounts if needed...

Unraid's perfectly fine with them, samba maybe not so much. Shouldn't cause any actual issues other than having to check for space on the server itself.

Tools -> System drivers, bottom


And no, it's in bytes. Not like you're changing the amount of RAM every day and need it to auto-adjust.

See this plugin

Doesn't support ZFS native encryption either, right?

Edit /boot/config/go and comment out everything after
#!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp
If that helps you can try putting the rest back from top to bottom...

My guess is it's this
# Start the Monitor Service cp -r /boot/config/monitor/ /usr/local/sbin/monitor/ chmod 777 /usr/local/sbin/monitor/monitor nohup /usr/local/sbin/monitor/monitor >/dev/null 2>&1 &I.e. they added some kind of monitoring service to check drive status and display it on that pretty little LCD, but without considering the implications / being careful not to wake up drives for it.

If you can confirm it's fine with only the first 3 lines of the file then contact Linc and tell them about the problem, it'll be on their side.

That's the whole point, this will make the copy appear as part of the same share (a share is just "any top level folder on any array or pool drive with that name"), so anything accessing the "Photos" share will wake up that pool to list its content as a result.
Make a new share on that drive and copy the contents of the Photos share to that new share on that pool instead.

Current Unraid version is 7.2.3. Anything before 7.1 is deprecated.

Settings -> Global Share settings -> Remove it from exclusion list