CeeJay

Thank you, that was it. But what the hell, I'm pretty sure I never touched that setting, and why would it be set to such a weird value...

A few days ago I tried bringing up a new container but got an error that the cache disk on which the appdata share resides was full. I have 2 SSDs in the cache pool, and they have more than 200 GB free. The appdata share is set to cache only. I've tried making another share that's cache only, but it won't let me because of the same error. I tried formatting the cache disk (by changing the file system and then back to the original one) but no luck either. The shares are all set to 0 KB minimum free space, I tried increasing the limit to 1 GB but nothing. I've also tried rolling UnRAID back to the last version I had saved. What else can I try? Thank you.

Thank you for your help. I just tried what you suggested and it does indeed work. I guess through my router firewall I can block traffic to 192.168.1.10:2345 and I should be good.

Scaling is an issue, since now I have to manage twice as many accounts for the same amount of users.

I have a similar but different issue with my Windows machine. To backup my computer I use Veeam Agent. I also use the UnRAID box as a NAS, so I have a share mapped in Windows Explorer to access my files. The issue is that Veeam gets a "Failed to create or open file error" if I try to login with the same credentials I use to access the NAS from Windows Explorer. The way around this issue is to make a separate account on UnRAID and use that with Veeam, but of course that's not optimal. Any idea how to fix this?

I have my UnRAID box connected to a managed switch which passes it VLAN 1 as untagged and VLAN 30 as tagged. I want most of my containers to run on the untagged VLAN, which is straight forward, I just set the container network type to bridge. However I have a container that must connect to the network on VLAN 30. For that, I can use br0.30, but if I do so my container will get an IP on the LAN, while my goal is to use the address of the server on that VLAN to reach my container, like I do on the untagged VLAN. Is this achievable? Home VLAN: 192.168.1.1/24 UnRAID Box IP (Home): 192.168.1.10 Bridged Container on Home VLAN example: 192.168.1.10:1234 UnRAID Box IP (IoT): 192.168.30.10 Current Bridged Container on IoT VLAN example: 192.168.30.11:2345 (my goal is to have 192.168.30.10:2345 here)

Perfect. How much RAM do you recommend? Is 8 GB enough for my use scenario?

Yeah the only thing I'm afraid of is random data corruption because of no ECC RAM. But the choice for ECC rated motherboards is poor.

Sorry, used the wrong term. Yes I will do disk parity through UnRAID. Do you think the software can run 24/7 with no user intervention?

I'm interested in building an UnRAID server with 2 main functions, weekly backups for 2 Windows machines and as a NVR for UBNT Unifi G3 Cameras. This is the hardware I had in mind: https://pcpartpicker.com/list/QczwXH The SSDs will run in Raid 1, and so will the HDDs. Is the Pentium enough for this kind of load? I'm positive it is, after all it's a dual core with hyperthreading. Is the ECC RAM necessary? I would like to use a microATX/miniITX motherboard but I couldn't find one that supports ECC RAM. Any other advice?