itimpi

There is not much point normally in backing up the Docker folder as its contents can easily be recreated via Apps->Previous apps

The two actions are independent of each other, although a parity check running will degrade array performance which may make the backup take longer than normal.

Running a parity check does not normally make the server inaccessible. Sounds as if something caused the server to crash. One possible culprit could be inadequate power as a parity check is likely to put maximum load on that so that is definitely worth checking out. you could try enabling the syslog server to see if you can get more information.

In principle all drives count that are attached any time you start the array regardless of whether they are used by Unraid or not. I have all my licenses under the same name/email so that should be fine

I would not have thought there was a problem, but you would need to contact Limetech by email giving those details and the GUID of the flash drive you intend to use with the licence to get a .key file issued corresponding to that flash drive,

Unraid will treat any top level folder on any array or pool drive as though it was a User Share. At some point you must have done something to create top level folders with those names (I suspect because of how you have a Docker container doing downloads configuredI). You can delete any of those .cfg files that do not correspond to Shares you currently have.

Why do you want to use the Parity Swap procedure? If you simply want to upgrade both parity drives then stop the array: Unassigned the current parity drives; start the array to make Unraid ‘forget them’ stop the array; assign the new parity drives; start th3 array to start building the contents of the new parity drives. the array remains available while building the new parity although performance is likely to be degraded. you probably want to keep the old parity drives intact just in case a data drive fails while building the new parity as that gives you a recovery option.

You need to go to the Pools section and add a new pool. The name of a pool can be anything you like - you set at the User Share Level what pool is associated (if any) for that share and whether a pool should be used for caching purposes on that share.

According to that screenshot you have you have not used the New Config tool Did you remember to tick the confirmation checkbox and then hit Apply. Simply pressing Done does nothing as that is the Unraid GUI standard for exiting the current dialog.

As mentioned, use Tools->New Config which will put the array back into a state where you can reassign drives as you want them. When you subsequently start the array the assignments get committed, if a disk has previously been used by Unraid then it’s contents are left intact after using the New Config tool.

Although in theory reallocated sectors are not always a problem I would be concerned if: there were more than a small number. On a new drive I would expect 0 the number was not stable and kept increasing since you say this is a new drive I would be looking to RMA it.

Are you saying you cannot set up port forwarding on your router?

How did you copy it? Depending on the method used then the permissions may be wrong for viewing over the network, and that type of problem can be rectified by running the Tools->New Permissions tool against the share. Not relevant, here but I think that tool should be renamed to something like "Reset Permissions". The "New Permissions" name only really made sense when upgrading to Unraid v5 from earlier releases when the security model changed.

Since all user/ specific settings are kept in the config folder on the flash drive then you could keep a copy for each site on the flash drive and then when you switch sites copy the one for the new site overwriting the live 'config' folder. Since each site will have different drive configurations (I assume) there is not much chance of an error as with the wrong configuration you will not be able to start the array. The one thing you will need to remember is that if you make any configuration changes at either site to then redo the copy of the config folder for that site.

This implies you want to swap the parity for a larger drive for which Parity swap is not appropriate. Parity swap is used for the special case of where you have a failed data drive and want to simultaneously upgrade parity to a larger drive and use the old parity drive as the replacement for the failed data drive. What are you actually trying to achieve?

The moment you format the drive then parity is updated to reflect this. You might find that data recovery software (such as UFS Explorer on Windows) can recover most of the data.

The WireGuard service has been part of Unraid since the 6.9 releases came out. In the 6.9 releases the webGUI enhancements to support configuring WireGuard was a plugin whereas in 6.10 that is now built-in

That suggests you have something configured to use /mnt/cache (typically a docker container). Since you no longer have a SSD at that location then it will be in RAM (and thus non-persistent). You might be able to work out what it is by looking at the contents. It can also be worth rebooting to see if it comes back?

I would not expect 3) to work in most cases, as normally a USB connection is master-slave type, and ln any case it is quite likely that 1) would be faster any way especially as it can be kicked off and left running so that no further manual involvement is required. The problem with 2) is that it requires 2 copies - one to the SSD and then another off the SSD so although each stage might be faster than 1) put together this may well not be the case.

There is nothing needed to be installed as on 6.10.0.rc1 and later it is all built into the standard release.

Looks good Would it also be worth supporting the Use Cache=Prefer item in a similar way?

If you look at the last line it is telling you that it is going to do nothing unless you remove the -n option and run the xfs_repair again. No obvious errors are being reported so it is highly likely the repair will fix things without any data loss. After doing so you should stop the array and restart in normal mode. I would expect the drive to now mount cleanly and all the data on it be intact. Having said that you might want to check for a Lost+Found folder as that is where the repair process puts any files for which it could not find directory information - I suspect you will not have this folder.

If you see the Unraid boot drive appear under Unassigned Devices, then that means that it has dropped offline and then re-connected with a different device Id.

If you do not want to mirror to flash then you can also set the IP of the Unraid server as the target (so that UnRaid is acting as both client and server). This is what I prefer to do.

By default the appdata share is set to not be visible on the network. You can change this in the share settings. However even if you make it visible individual containers set their own specific permissions on files and it is highly likely that a container will have set permissions that will not allow editing over the network. For what you say you want to do the easiest thing to do is to install the Config Editor plugin that by-passes this problem and adds an option to the Tools menu in the UnRaid GUI that supports editing text files on the server.