trurl

A clear disk also has no impact on parity2. Same as parity1. All zeros doesn't affect the parity2 result either.

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post

On mobile so not looked at Diagnostics yet. Have you done memtest?

There isn't often a need to do things at the command line, and you mostly shouldn't even be messing around with any paths except those for your disks and user shares. What are you trying to do?

CRC Errors are connection issues not drive issues. The counter won't reset, but you can acknowledge the SMART warning by clicking on it on the Dashboard. You will get another warning if the count increases. Continue with rebuild

What are you wanting to do at the command line anyway?

And make sure you have a current backup of flash. You can download one from Main - Boot Device - Flash - Flash Backup

Post your docker run :

Are you booting from a USB2 port? Recommended.

Your welcome "Member"

I don't think you need that port number. I don't have it and mine is working. proxy_pass http://$upstream_lychee;

None of it. Go to Tools-Diagnostics and attach the complete Diagnostics zip file to your NEXT post.

Do you have a backup of appdata?

Each additional disk is an additional point of failure. If you don't need the capacity of these small disks don't use them. Just wait until you do need capacity and install larger disks. Also, every disk in the parity array is important. In order to reliably rebuild every bit of a failed disk, every bit of parity PLUS ALL remaining disks must be reliably read. I recommend testing all of these disks before trusting them in your server. I would just leave out the 2.5 inch disks completely. So none of these disks are SSDs? As for your question on backup, yes Unassigned Devices can be used to make backups. You must always make sure you have another copy of anything important and irreplaceable. Parity is not a substitute for backups. If you don't have much you consider worth backing up then those small disks might work well for that.

Are these just a bunch of disks you already have? How much capacity do you need? Some of those are too small to waste a slot or port on, unless some are SSDs for the cache pool.

VPN. Wireguard VPN is built in with Unraid 6.8+

Do you mean it doesn't remember the mappings and other settings from the Add/Edit Docker page? Or do you mean each of the applications doesn't remember its settings? Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post.

Save us the trouble of asking for it.

Not sure I understand. Do you mean you aren't using this on Unraid? See the first post in this thread.

Are you sure you don't have something wrong in your Network Settings? How are you manually adding them? It shouldn't be necessary to work at the command line for this.

The Unraid OS, with all of its usual Linux OS folders, is in RAM. It is loaded into RAM from the archives on Flash. You will have to run a script to make any changes to those folders after each boot. The User Scripts plugin will let you set that up.

For future reference, md2 is referring specifically to the disk assigned as disk2 in the parity array, so there was no reason to think doing anything with parity or cache would help.

Cancel the pointless read check. To rebuild a disk to itself, whether parity or data, stop array, unassign disk to be rebuilt, start, stop again, reassign disk to be rebuilt, start again to begin rebuild.

👍

All data goes through memory. That doesn't necessarily mean entire files are ever contained completely in memory. BRiT's point was that if you had more memory, more could be buffered and that would be faster than moving it to cache first. Whichever disk it is on is still going to require the data to be read into memory before it can be used for anything.