trurl

No. It's just forcing unRaid to use a particular address to resolve domain names (in this case Google's DNS servers) and bypassing whatever your ISP has chosen to use (in my case, Bell Sympatico's DNS servers are beyond crap) Hey Squid... Love the appdata backup part of this, any chance of adding a /boot backup as well? See here

Auto worked fine on both 6.1.9 and 6.2b21 for me.

And because I figure I already owe him from the extensive use I made of unBalance when setting up my Backup server. +1

Transmission - Editing Configuration Files

rsync exit code 23 - Partial transfer due to error

I don't think those environment variables are intended to be used the way you think. Have you tried just using the defaults?

All writes to disks in the unRAID parity array update parity at the same time, so parity will be OK.

How are you removing the files? This is just for files you delete over the network using SMB.

How did you do the upgrade?

Your appdata share is not set to Use cache disk: Only so it is getting moved. See Docker FAQ

Install Community Applications plugin.

When I said I had seen similar, I meant similar reports on the forum. I have personally never had this with any drive of any kind. And my ideas about the cause is speculation. It's just that another interpretation of that number you reported is -1. That is the way -1 is represented in 32bit.

4294967295 is FFFFFFFF so unlikely to be real. That number is what you would get if you had a 32bit zero and then subtracted one from it. I have seen similar with other attributes, where it looks like something that was 16bit zero got decremented by 2 and so became FFFE (65534), for example. Must be some bug in the drive firmware. Don't know if another preclear cycle would make any difference or not.

Don't have anything to say about your actual question, but I do want to comment on your use of the word format. Formatting a disk when adding it to the array is the expected behavior. Since you said it fails the preclear -t I assume you instead meant that it is trying to clear the disk. Formatting and clearing are completely different and unrelated operations. A formatted disk and a clear disk are very different things. Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. Understanding this can help you avoid mistakes in the future.

This would be great and VM's (I know VM's is not really a part of this but Flash backup would be great) In order to correctly backup the flash drive it is necessary to actually stop the array since the started/stopped status is part of the super.dat file and restoring a backup that shows the array was not stopped will result in an automatic correcting parity check due to unclean shutdown. Also, users need to be aware that restoring a flash backup that does not have the correct and current disk assignments can result in data loss.

Here Also copy your .key

I probably won't try this docker myself, but if you look in the folder where /config is mapped, is the .jar file there? If so you might be able to replace the .jar yourself. I know another java-based docker could be upgraded this way.

Settings - NerdPack. Turn on screen. It will automatically turn on its dependency, utempter. Apply

I guess I should have just said starting the array with the disk unassigned will make unRAID forget it. That would have covered it regardless of the other details.

unRAID never moves files once they have been written to the parity array. It will move cached User Share files from the cache disk to the parity array at the scheduled time. If you need to rebalance you will have to do it yourself. See the unBalance plugin. Most free means the disk with the most free space. The meaning of "least full" seems a little ambiguous to me. Changing the setting will take effect for subsequent writes but will not move any files already written. And split level still takes precedence so if the folders where a write should happen according to split level are already on a disk it will continue to write to that disk. A User Share is really just top level folder(s) on the parity array or cache. The folder(s) will have the same name as the share. Upper/lower case is significant so Movies is a different share than movies. A User Share is the aggregate of all these top level folders named for the share. Conversely, any top level folder on the array or cache are part of a User Share named for the folder. If you create a top level folder it is a share and if you don't make settings for a share it has default settings. The settings for a User Share are mostly about telling unRAID where to put files for the share when it writes them. Even if a disk is not included in the share for writing, it will still be included in the share for reading unless excluded from all User Shares in the Global Share Settings. The unRAID webUI has a Help toggle in the upper right that will turn help on/off for all pages. Share settings are explained in the help though without as much detail about what happens behind the scenes.

Maybe that is what he is asking, but he is asking it in a very roundabout way since he has already proceeded to rebuild to spares and before supplying that information he said he was preclearing the originals. All those extraneous details had me trying to figure out what may have been a simple question.

Still don't understand. Did you or did you not already rebuild or are rebuilding the data onto other disks? Once you successfully start the array without a particular disk unRAID has forgotten all about it. Starting the array, even with missing disks, causes unRAID to update super.dat which is how it remembers your disks.

OK since you have dual parity then everything is fine. I don't understand what the question is then.

Sounds like you have 2 disabled/missing at the same time and you just want to reuse them instead of possibly trying to recover their data since you say you are preclearing them. You will have to New Config, reassign all your drives, and let parity rebuild. Be careful you don't assign a data disk to the parity slot.

Another thing I have found when rsyncing between two servers is that rsync will often create the folders before it writes the files. Depending on your split level, this can result in the destination drive being predetermined before the files are written. Once it has created the folder for a file, the split level can cause it to try to write files to that folder even after the drive is full. I don't know if there is any rsync option to prevent this behavior.