Kilrah

ZFS doesn't "need" the RAM, it just uses it if some is available and frees it when something else needs it.

You never refer to a bridged container's ip, as you see they're disposable and change. You refer to the server's IP. On br0 you can't select ports since the container always has all of them on that ip, but bridged containers can't reach it unless "host access to custom networks" is enabled, that's also a solution but the former would usually be preferred.

He said the service was disabled... But no it doesn't disable itself. Maybe had uninstalled/reinstalled the plugin at some point and forgot to reenable it?

Most likely unrelated, where are the errors reported? Also check syslog for drive errors. Can be caused by a bad SATA connection and not the drive itself.

The CA preview moved from being a page on the main LT site to being its own site.

Yep. No need to rush about it though.

No change, it's not for use on your server, it's so that people can browse CA without already having an Unraid system. E.g. potential new customers, app devs who want to make a template and check it's there but who are not using Unraid themselves...

How did you downgrade? If you erased the flash drive and did a clean install from the usb creator you should put the Trial.key that got while you were on 7.3.1 back into the config folder.

Make sure that drive is not in the boot sequence in the bios.

You somehow managed to "correct" someone's typos with 9 of your own, 2 being in the exact commands... Maybe just don't answer.

It is random at creation but it won't change. You can see it matches the instanceid in your config.php.

NEXTCLOUD_DATADIR is about specifying another location for the whole "/data" folder so won't help you. You can just add an extra mount to the container for the specific dir you want somewhere else.

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.

He was not asking about the plugin, he was looking for a solution, and I am pointing out that this plugin is probably what he wants.

One day you'll eventually have to either stop updating or replace the card, when that is nobody can know.

You must have a single repo.

rsync got some issues in the version that 7.3.1 includes, not sure if that is the source of your problem. https://github.com/RsyncProject/rsync/issues/915

Another option is user scripts plugin, with script scheduled at array start. Nothing should be mounted within /mnt until after the array is started.

Use the Unassigned Devices plugin to mount remote shares instead of doing it manually, then that'll ensure things are done at the right time.

I don't see a reason why it shouldn't work, but obviously you have to spin up the slicer container you want and there are no templates for them at this point so you have to make your own. EDIT: Yup, works fine.

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.

Will probably have to build on another machine/VM and transfer the compiled result

Why do you want to move from a good RAID1 setup to a single drive? Speed is entirely irrelevant.

Doesn't really need more development in the first place... It'll keep working as it is.