JonathanM

It's not that simple. To figure out the correct (for you) size for a UPS you need more information. Critical parts of the whole picture are... 1. Idle power draw in watts (not critical to measure accurately, more just good info) 2. Max continuous draw with all drives spinning and actively being accessed, parity check with all typical VM's and containers running is a good time to measure. 3. Instantaneous surge when transitioning from idle with no drives spinning to a parity check. (Hard to measure without really special equipment, but still important to estimate) 4. Unattended shutdown time. How long does the machine take from fully active to powered off if you stop the array then power down, assuming everything is running like it normally does, no fair preemptively stopping VM's or containers. 5. Typical outage length. Do you have multiple 5 minute outages? Or just 5 second or less blinks? If the power is out for at the 1 minute mark, how likely is it to still be out hours later? For power draw measurements, you really need a meter, something relatively cheap and simple should work fine. I can't tell what part of the world you are in from that amazon link, but here is something like what you need. link The max capacity of your PC power supply has little if anything to do with actual draw, you really must measure how much it pulls from the wall to figure out what you need. Keep in mind that if the UPS uses SLA batteries (almost all do), they really dislike being discharged below 50%, it's not good for their lifespan, so after you get your real load numbers you should try to stay in the first 50% of the runtime chart for the full shutdown time. The UPS you linked may be overkill, or just right, or too small. No way to tell without finding actual usage figures.

Thanks for your effort, I used screen for many years. I'm now a tmux convert, perhaps you could look into that? https://www.howtogeek.com/671422/how-to-use-tmux-on-linux-and-why-its-better-than-screen/

This. Agree. Maybe your current effort to allow multiple containers access to the forwarded port will be usable with other containers besides this one? Unfortunately I'm not enough of a network guru to know if this is feasible, but how about redirecting the changeable vpn port forward to a static port inside your container network?

That's because the absolute path you are using isn't correct. You are mapping /data to /mnt/user/Total_Library/Downloads/, so if you want the completed downloads to go there, the absolute path is /data and for incomplete downloads, the absolute path is /data/incomplete mapping is path substitution. container side = visible inside container. host side = where those files appear on the host.

So in the eventual future, do you see independent VPN and application containers as the norm? Not to get too far ahead of you, but I'd love to see the possibility of multiple VPN endpoint containers, each able to support multiple of your application containers. For example, VPN1 with a PIA port forwarded connection, torrent and other file sharing containers pointed there, VPN2, a PIA or whatever, with various downloader apps assigned there. Some downloader apps get upset with out of area connections, it would be nice to easily set up 2 tunnels, one foreign, one local.

Try changing the base folder to /data instead of /config

Are you planning on shucking those and using them as internal drives? USB is unreliable for server connections, and if you use USB for the parity array it's likely to cause issues.

Are you sure? I didn't hear that in the podcast you posted.

I highly recommend NOT using water cooling in a server, especially since you are new to building. Liquid cooling is fine for a gaming machine that is only on when someone is sitting right there with it and can react to any issues. I'm not saying liquid cooling is unreliable, just that the consequences of pump failure or leaks are much more drastic than a normal fan failure. A regular heatsink with fan can operate with a failed fan for a long time because of the thermal mass of the heatsink, and natural air convection.

When I restored my lsio backup to this container, all my credentials were transferred. See if this thread helps https://community.ui.com/questions/Migrate-From-UDM-Pro-to-UXG-Pro-and-Windows-Controller-Advice-Needed/4ec2f4fd-b7d2-4cf2-b756-bcef632b0c5a?page=2

They have three different pool names, correct?

Yes, if you write to a pool name that does not exist, you will end up writing to RAM, which is gone after a reboot. exactly

/mnt/cache is the pool named cache /mnt/disk1 is the disk in slot 1 of the classic array /mnt/user is the combined view of the root folders on the participating disks and pools What is the pool name that it is assigned to?

Have you checked to see if there is an update available for the card? IIRC silverstone is one of the few vendors that offer updated firmware for their cards.

Forgive me if this is a stupid question, but are you planning on VPNifying this like you have other peer to peer apps?

Parity error addresses are in the syslog, but there is no easy way to correlate them to files or what they might corrupt. Determining whether you can safely ignore them is a very technical process, I gave the 10,000ft overview. If you aren't comfortable with that explanation, no, you can't safely ignore them. It's not the Asmedia chip that seems to be the issue, more the implementation on the specific model of card. I would start by replacing the card with a different brand version of the same chip.

Set the checkmark for Sorted to be the reference, then check the selection for all files, and only the files in "All" will be selected for deletion. (ps. using folder names All and Sorted makes explaining this very confusing)

Depends. If the errors are always in the same addresses, and those addresses aren't critical to any of the files or filesystems, then you can ignore them. If not, then you need to replace parts until the parity check is always clean. Another consideration is normalizing parity errors. Typically you would alert on any parity errors, currently you have to examine the logs every time to see if all the errors are "expected" or you have new ones which need attention. Personally I wouldn't feel comfortable running like that.

Keep in mind that those connections are subject to vibration, and the connector is under spring tension to make the connection, so eventually the pin will reestablish the connection. Murphy's law states this will occur at the most inconvenient time possible. The proper solution is polyimide tape, commonly called kapton tape. It's much better suited to this scenario.

Does it act the same way with a docker image instead of using docker directory?

Which antivirus software suite are you running on the local PC?

Why does that preclude testing with another account temporarily? Just add a user, and log in with those credentials.

Can the RDP port of this VM be reached from WAN? Sounds a little like someone or something is trying a brute force or denial of service attack. Another thought, see if it's linked to that specific user account, set up another account and use it for a bit and see if the same thing happens.

Many many different options. VPN, nextcloud, many other secure applications available in apps.

Export Site is only enabled if there are multiple sites defined in your install.