JonathanM

There are MANY different implementations of nextcloud, each with somewhat unique environments and quirks. You need to post in the specific support thread for the container you are using, not start new threads randomly. If you click on the nextcloud icon on Unraid's GUI, the dropdown has a "support" item. That should take you to the correct area to get support for that container. Note, not all containers are supported here, some container authors choose to support their containers on discord, or on their github. This general support area is for issues with the core structure of Unraid, not community supported applications.

Try setting export to yes.

When you edit the path, you set the access mode as one of the properties.

Have you tried adding with r/w slave?

Make sure you either source directly from the manufacture for that SPECIFIC power supply, or verify the pinouts with a tester of some sort before attaching any drives. There have been multiple accounts on this forum alone of people frying multiple hard drives with cables that physically fit perfectly but were pinned differently, feeding the drives 12V where they were expecting 5V.

How would you accommodate access from different machines / layouts? I don't want the same layout on my huge desktop monitor that I need on my old laptop.

Is there any way you can use more leads? Preferably 4 pin molex style, they can handle much more current. Each SATA connector can really only handle 2 drives, so if you try to use SATA splitters it's very easy to run out of current. It's much safer to use molex -> SATA splitters if you really have to use splitters at all. Ideally you shouldn't use any splitters, rather source a PSU with enough connections available. Many modular PSU's have extra cables available specifically for them.

What is your plan for getting 10GB link between the different buildings?

Not by choice. Many here are responsible for supporting systems that they weren't involved in the purchasing process, and possibly aren't even involved in the day to day maintenance, only called in when things go very wrong. It can be incredibly frustrating.

How many of the other devices are 10GB successfully negotiating down to 1GB?

Did you browse through or search that thread? I see several references in there to his AdGuard container, if someone hasn't already answered your question there, you can post your question at the end of that thread.

Best to post in the specific thread for the container you are using, click on the icon in the Unraid GUI and select support.

Maybe the power got overloaded? How many drives do you have on each PSU lead? What size is your PSU? Any splitters? What kind? Molex-SATA or SATA-SATA?

The config folder should have all your customizations, so that's the only folder that you need to copy. All those files should be plain text except for the super.dat file which has your drive assignments, so if you take a look at the files you suspect could be corrupt it should be pretty obvious.

Probably not going to get an answer here. Been almost a year since they logged in to the forum.

My best guess is that the "switch" inside the router is cheap. Maybe get a quality 5 port switch and only use a single connection to the router, all other devices get to use the good switch. Decent 5 port GB switches are dirt cheap, won't hurt to try.

I use UrBackup, I'm assuming the exact same way they use veeam. The VM is running the backup agent, so the backup agent has full knowledge and control of the file system. You get a good backup while the VM is up and running, because the backup agent can do shadow copies, cache flushing and other manipulations to ensure backed up files are valid. When the VM is borked, you change the boot iso to the backup software's recovery agent, and retrieve the backup image, overwriting the borked files. If you back up .img files, you have several options, only one of which is ideal. You can shut down the VM so the backup is in a fully consistent shut down state, you can back it up while the VM is running unaware, which means the backup is functionally equivalent to what you would get by pulling the power and crashing the VM, or you can set up the kvm guest agent and use the proper function calls to get the OS to commit changes to the image. Until all the pieces are in place for the last option in Unraid, the only real solution is running the backup agent inside the guest. This solution works now, doesn't need anything extra, and is very reliable, I've moved VM's to a new host using UrBackup. I'm not saying native qemu backup in Unraid isn't a good ask, and it's reasonable to request it, just that it's not the only option, there are many good backup methods for VM's that work now.

Check out the 7. betas.

Before you swap the parity drive, run a non-correcting parity check to be sure everything is stable with all your current data drives.

Do you have a reason to suspect your drives? Unraid parity requires all drives to be successfully read in total, not just the occupied data space. If you have any suspect drives you need to take care of that before changing parity. When was your last parity check with zero errors?

Sure. Stop the array, unassign the 20TB, assign the 18, start the array and let it rebuild parity. You may need to start the array with the parity drive unassigned, then assign the 18TB, I can't remember. If you are paranoid about drive failure while parity is being rebuilt, you can do all this in maintenance mode so the drives don't mount and are unavailable for the duration. This would mean that the 20TB would remain valid until the array was started normally.

How many (and which) cores do you have dedicated to the VM? Keep in mind that the host needs resources (CPU and RAM) to supply I/O and system emulation.

Keep in mind that without a writeable flash, any changes to configuration will be lost. I'd keep the array usage to a bare minimum just to be safe.

Many people make the mistake of trying to keep running as long as possible on UPS. Don't. Set the system to shut down after a minute or two of power out, typically if the power is out a solid couple minutes it's going to be a while before it comes back.

Disk write failure (red X and says emulated) and file system corruption (unmountable) are two different issues, each handled differently. Not to say they can't happen at the same time, but rebuilding an unmountable disk will always result in the same unmountable file system. Parity doesn't know about files, it just emulates and rebuilds whatever is on the disk, regardless of whether it's a valid filesystem or not.