JonathanM

The "columns" are 3 sections, the last two flow between being side by side or stacked, depending on your browser width. If you make your browser narrower, the "middle" and "right" stack to become very close to the length of the "left" block. You are just being penalized for expanding the width of your browser past the design intent. 🙂 Seriously though, free placement of all items would be nice, the sticky part is how you handle displaying it to different browser widths. If you open the site in a tall skinny browser like a mobile phone in portrait mode, do you force left right scrolling, or do you flow everything vertical? If the browser is then expanded side to side, do you create more and more columns? (Disclaimer, I am not a web developer, or involved in any way with the layout or design of Unraid. I'm just pointing out that it's not quite as simple as it sounds on the surface to make things look good for multiple layouts simultaneously)

Unclear what you are asking. Checksums are used to verify the file is unaltered. Multipar / Quickpar add extra files with additional data to allow replacement of a subset of the original files. If you have a valid multipar / quickpar set, there is no need for additional checksum utilities.

No, they simply show whether a file has changed since the checksum was originally generated.

Did you redo any custom docker networks that you had set up previously? Those configurations are part of the docker image file.

If you stop VM and Docker services, so the menu items no longer appear in the GUI, you should be able to use Dynamix File Manager to move all the appdata folders onto a single disk. Then set the split level to manual, and it should stay on whichever disk you put it, and you can re-enable the Docker and VM services.

Shares, click on the "compute" link on the appdata line, then take a screenshot of those rows, including all the columns in the appdata row from the left to right, like this.

Semantics. The backup put the key file that belongs to the old USB stick onto the new stick, so you must obtain a new key file that matches the new stick. That's done with the replace key procedure. I realize I'm saying the exact same thing that you said, just wording it differently, if I'm not clear reply back and I'll try to explain better.

Change the /mnt/user mapping to /mnt, but be VERY careful not to go into the /mnt/user folder for finding dupes. It's either / or, and if you open up /mnt you are setting yourself up for a world of hurt if you allow it to search for dupes in /mnt/user AND /mnt/diskX or /mnt/poolname at the same time.

Too many different goals have different requirements. No way to generalize except to set an upper limit that is rational for some situations, keeping a minimum free space of at least the size of the largest single file that is currently on the disk or a few multiples of that. You need free space if you need to run file system checks, if you get corruption too little free space can keep the repair from completing.

Nothing a blanket tossed over the server can't solve. 🤣 Seriously though, maybe set up an old rig with a couple small drives, and cover up the intakes with a piece of cardboard, you know, for science.

Yep. Assuming you mean using the m.2 in question for the VM, then the two options are mutually exclusive.

Sure, at the console type "virsh start <VMNAME>"

Can you monitor the activity from the local console and unplug the network to see if it stops?

Running an iperf test would help narrow the focus.

Does this thread help?

Maybe after you enable it in Settings?

nomachine

virsh commands for VM's https://www.redhat.com/sysadmin/virsh-subcommands docker for containers. https://www.mygreatlearning.com/blog/top-essential-docker-commands/

This guy has many videos encompassing pretty much all Unraid can do, have a poke around and see what you see.

The easiest way is to treat your VM's just like standalone machines on your network, and connect them to user shares with SMB.

Establish a VPN connection between your remote machine and your home network. Whether that's the built in wireguard on Unraid, or some implementation in your router doesn't really matter.

For reasons beyond the scope of this discussion, public beta's are called "Release Candidates". And I have no clue if a RC before the end of the year is in the cards. There is a good reason this thread is called Soon™️

You are thinking of when the container was named "Letsencrypt", but for obvious reasons the letsencrypt project was less than thrilled for a third party package to take their name. Transitioning from the poorly named letsencrypt container to the identical swag was simply a matter of changing the repository name.

Since you are wanting to use Unraid as a guest instead of booting bare metal, I'm moving this post to that part of the forum. Unraid as a guest is not supported, it's not forbidden, but not developed for either. There are a small group of folks that actively run Unraid as a guest, perhaps one of them may have an idea.

No good solutions come to mind. Any software solution MUST be able to monitor the state of the input power of the UPS, and I don't know of a reliably consistent way of doing that without adding some piece of hardware to the mix. Any indirect monitoring like checking the status of an unrelated piece of equipment is fraught with issues, the most obvious being that if any part of the communication chain fails, you either shut down unnecessarily, with lots of problems getting things back up because the script will keep trying to shut you down, or you fail to catch a real event, causing uncontrolled shutdowns. The UPS monitoring and action scripts are already proven, why reinvent the wheel? The small UPS's are barely bigger than a fat power strip, and can typically be wall mounted, so attaching it to the back or side of the desk may be an option.