trurl

How is this possible if he formats the USB drive? Following with these and reading @trurl what is the way to make a backup of the flash disk? keep a copy of: config/super.dat (and you won't have to assign your drives)( if you've changed your array or parity since you backed up that super.dat restoring it could result in data loss) config/*.cfg (files you want to keep the settings from) config/shares/*.cfg (files you want to keep user share settings from) Anything else? Thankyou Gus I think itimpi was just leaving out some details. Perhaps he should have said I usually backup my flash to my PC over the network. super.dat that I mentioned also tracks whether the array is started or stopped. You don't want to restore a copy of that file that was taken while the array was running or unRAID will think you are booting from an unclean shutdown. The flash share can still be accessed even if the array is stopped, so stop the array and then make the backup. And as others mentioned, you definitely don't want to restore super.dat that doesn't have your current drive configuration.

If you start with a fresh install you will just have to reassign all your disks. Be sure you don't assign a data drive to the parity slot or it will get overwritten with parity. Then make any other settings you want in the webUI Alternatively, keep a copy of the config/super.dat and you won't have to assign your drives. Also, you can copy any config/*.cfg files you want to keep the settings from and also the config/shares/*.cfg files you want to keep user share settings from.

Limit in what way. Speed? Size? Dropbox syncs all contents of the client folder by design.

Are you really using 6.0? I don't think anything but 6.1+ has been available for download for quite some time.

As wgstarks said, allocation method controls where files are written, but after written unRAID will not move them. If you want to move them yourself the unBalance plugin might help. Okey, Thanks wgstarks and trurl. I see I have the standard "High-Water" option chosen. But I will buy 1x new 4TB and remove my 2x 500GB drives, is the best way to do this by shrinking the array (removing the 2x 500GB disks) first and then add my new 4TB as normal? http://lime-technology.com/wiki/index.php/Shrink_array This one might be more appropriate: Replacing Multiple Data Drives with a Single Larger Drive

As wgstarks said, allocation method controls where files are written, but after written unRAID will not move them. If you want to move them yourself the unBalance plugin might help.

By clicking the Log button

Check out the unBalance plugin.

Yea, I just prefer to cut and paste so that if something goes wrong in the middle of it I don't have to figure out what was copied, what wasn't, and where the partially written file is to overwrite. Well I guess that is one way of looking at it. Another way of looking at it is if something goes wrong you have deleted the original files.

Empty and/or format has absolutely nothing to do with rebuild. The only way rebuild should have occurred is if the drive was missing or replaced. Can you tell us more about what you have done?

Midnight Commander is builtin and it shows progress. Oh, right, I forgot. But is there a webui plugin for it or is it just through the terminal? I can deal if there isn't. It will just be easier to monitor remotely if there is. You mean like telnet? I run totally headless most of the time and so my "terminal" is just any PC on my network running PuTTY.

Midnight Commander is builtin and it shows progress.

It wouldn't surprise me if most use it like I do, but since my use case is very simple it doesn't get a lot of discussion. I just use it to plug in external drives to copy to/from my server. This is how I create backups of critical files for offsite storage, for example.

As always a pertinent question is "What version of Unraid are you using?" I took a quick look at the code in question, and it makes absolutely no sense. As an example, one of the lines in question was supposed to do an operation on an array. But the error was from it trying to do the operation on a string. However, the line previous checked if the variable was an array before doing anything. Net result is that I would think that its either a completely corrupt download that somehow managed to pass the md5 checks or there's weird memory issues in his system. javascript in browser cache perhaps?

Not really answering your question, but your talk of deleting the original after transferring to unRAID makes me wonder whether you have backups. unRAID is not a backup unless it is used to store additional copies of files you have elsewhere.

Go to Settings - Docker and restart the Docker service. Dockers cannot see anything that was mounted after the docker service starts.

nano is builtin. Also mc (Midnight Commander) is builtin and has its own editor.

I had preclear fail on post-read once due to bad memory. You might try a memtest just to eliminate that possibility.

I think you must have meant /mnt/user/appdata and not /mnt/appdata in your explanation above. /mnt/appdata would actually be a RAM location and not on any disk.

Hard Drive SMART Stats

Sounds like you may have some misconceptions about parity. Parity by itself won't allow you to recover any of the data from a failed drive. Parity plus all the other data drives are needed to rebuild a failed data disk. And parity doesn't actually contain any of your data, but a data disk does. So actually parity is slightly less important than a data disk.

The typical symptom of the "User Share Copy Bug" is a lot of zero length files. Search for it for more details of what causes it. Basically Linux doesn't know that user share files and disk files may actually be the same file so it will start off the copy/move by creating a zero length file, then when it tries to copy/move the data to that file, it has already truncated the data. Disk shares are turned off by default to prevent you from doing this over the network, but there is nothing to protect against it from the command line.

And be sure you don't move from /mnt/user/appdata to /mnt/cache/appdata. You must move from each disk to cache, like /mnt/disk1/appdata to /mnt/cache/appdata.

Parity validity and file integrity are such different categories that you might as well say they are unrelated. It will notify you

Make a backup copy of the needo plex appdata (shouldn't need it) and then point this plex to the same plex appdata.