itimpi

Delete any .cfg files in config/shares on the flash drive that do not correspond to shares you actually have.

There is a write-up here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI that explains this plus what you can do to maximise speeds.

What do you mean by this? There is no such step in the normal process for rebuilding a disabled drive. This is what happens when Unraid thinks you are adding a new drive to a parity protected array, and not when a rebuild is being done. I suspect you may have lost the contents of the drive, but if you post your system’s diagnostics zip file we might be able to work out what really happened and the best way forward.

Technically this is not required unless you want to first carry out a confidence check on the new drive.

If you provide your system's diagnostics zip file we would be able to tell you what drive it relates to.

The Parity Swap procedure is not appropriate for replacing a failed parity drive You should just be able assign the replacement drive and start the array to rebuild parity. The fact it appears to not be showing up to assign suggests an issue at the hardware level. You might want to carefully check power and SATA cabling to the drive. Posting your systems diagnostics zip file might also help with diagnosis.

A bit earlier you were also getting file system corruption reported on disk1 so you may want to check that one as well. Wold not do any harm to check all disks while you are at it

You have corruption on disk 4 so you need to run a file system check on that drive. File system corruption often causes the tort of symptoms you are seeing.

That means you want the files to stay on the cache forever. The help built into the GUI can help with how the settings work, and you can get more detail via the online documentation that can be accessed via the Manual link at the bottom of the GUI.

You need the Use Cache = Yes setting for the share in question. Without your system's diagnostics zip file it is impossible to see if you have already set this and have some other problem.

I think you it is possible you are getting confused between what is in appdata (the containers working sets) and the container settings that you set on the page for a container on the docker tab? The latter are NOT part of the appdata backup but are stored as templates on the flash drive. For instance the way to have got back the deleted Docker would have been via Apps->Previous Apps.

Are you talking about setting up WireGuard VPN or the My Servers approach?

Whatever is currently showing on the emulated disk is what you will end up with on the physical disk after a rebuild.

That will be because the libvirt.img file on the flash drive is empty/damaged. During the boot process it is mounted at /etc/libvirt

You should always have another copy (preferably offline) of any important files. In your case maybe the ones that really matter should be on both servers if you do not have offline backups? The limit is the total of the data drives. Having said that many people like to use dual parity as the number of drives starts getting larger (e.g. 10 drives) as the chance of a second drive failing while recovering from an initial failed drive start going up. It is really a user decision on risk/cost benefits. There are those with a good backup strategy that run without any parity at all. You might find the discussion of parity in the online documentation that can be accessed via the Manual link at the bottom of the GUI useful. One thing about Unraid is if that the number of simultaneous failed drives exceeds the number of parity drives then you only lose the data on the failed drives unlike traditional RAID systems where you lose the whole array. No. You can add such a drive as a data drive, but none of the parity drives can be smaller than the largest data drive (although they do not have to be the same size).

You can find the Parity Swap procedure which handles this scenario in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.

This. you may need to stop - restart the array to make the change take affect if using 6.10.0 rc2 because of a bug.

I am currently working on adding to the Parity Check Tuning plugin an option to Pause if it detects mover is running, and then resuming when it stops running. Will this be of use?

It is covered here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.

I normally reckon on something like 1-2 hours per TB.

It is a known issue that if a pool is having problems it can interfere with the behaviour of User Shares.

No documentation that I know of. It has been frequently stated that the only difference is loading plugins, but I guess it does not mean that there is no other difference (although I have never noticed one). Having said that I believe there is a folder on the cache drive (cannot remember. It’s name - probably something like ‘extras’) that can contain packages that are auto-loaded in normal mode and may not be in Safe Mode. The whole idea of Safe Mode is to avoid loading any software components that are not part of the standard Unraid release.

I just don’t see Limetech getting it out that quickly based on past experience. I would like to be proved wrong

Since the problem seems to have started when you added a new drive are you sure your power supply (and the cabling to the drives) is up to it? A parity check is one time when all drives are in use simultaneously.

The only difference in Safe Mode is that no plugins are loaded. All other functionality works the same.