trurl

Stop the array to change 

Linux "repaths" the file onto the same disk, known behavior and nothing to be done about it. Copy from source to destination then delete from source.

You could start with 6 data +  2 parity until you have more experience. Then later you could convert parity2 to data to get more capacity after you are confident you know how to work with your hardware and with Unraid.
 
If you have a lot more data disks then I would say you should have dual parity, but single parity is probably OK for as many disks as you are thinking about, as long as you are diligent (setup Notifications to alert you immediately by email or other agent as soon as a problem is detected) and careful (always test new disks before trusting them in your array, and always double check all connections when mucking about inside).

Both docker.img and cache are readonly due to corruption. You can recreate docker.img after you fix cache. You may have to copy what you can from cache and reformat it.
 
Have you done memtest recently?

As long as you don't remove or add data drives parity is valid. Parity2 has to be rebuilt if drives are reordered. 
 
New Config, preserve all, change assignments as needed, unassign parity2. When starting the array check the parity valid box.
 
Then stop, assign parity2, start to begin parity2 build 

Your earlier diagnostics showed parity build in progress. Does autostart work after you let parity build complete?

flash drive has disconnected and reconnected as a different device so it is no longer mounted.
USB2 ports can be more reliable, is it USB2?

What luck. If that's all that happened the contents should look pretty good.
 
rebuild to the new drives.
 

When you removed the drive did you shrink the array?
 
Attach diagnostics to your NEXT post in this thread.

Unassigned Devices plugin has a rootshare feature don't know if it will help or not 

Create a new install on the original flash drive and see if that boots to GUI. If so, you can copy your config folder from your flash backup which will get your license and all of your configuration back.

No it didn't do that.
 
Rebuild only writes to the replaced drive. New Config only writes to the parity drive. All other array disks are only read, and all other array disks are independent filesystems that can be read without any of the other array disks.
 
Looks like you have 9 data disks in the array, all are mounted and have contents. And you have 3 pools, all mounted and with contents.
 
Something has just broken user shares. For example
 
Connection problems on multiple disks. Looks like some of your drives are external. USB connections are not recommended for array or pools.
 
Also, you should always double check all connections when you are mucking about inside.
 
Post a screenshot of Main - Array Devices, and another screenshot of Main - Pool Devices.
 
 
 
 

Do you mean your server can reach the internet? Or do you just mean other devices on your network can?
 
Your network.cfg isn't using DHCP but has no DNS specified. Best approach is to use DHCP with IP reservations by MAC address in the router.
 
 

The total capacity of all data drives in the array is the total capacity of the array. Parity contains none of your data and by itself can recover nothing.
 
https://wiki.unraid.net/Manual/Overview#Parity-Protected_Array

Since flash was disconnected it was no longer mounted so not accessible to Unraid.
 
Put flash in PC and checkdisk. While there make a backup. Try booting again.

That setting is in config/ident.cfg on the flash drive

You don't need to have any missing disks. Just go ahead and assign the replacements to those slots and the exact disks as before to all other slots.
 
Then, when you check parity valid box (so it won't rebuild parity) and check Maintenance Mode (so no disks are mounted), then start the array, disk assignments will be recorded, but nothing will be read or written to any disks (because no data disks are mounted and parity is valid). At that point, no disks will be disabled, which gets us disk1 back so it can be used with your dual parity plus all other disks to rebuild the 2 replacements.
 
Then, you stop the array, unassign the replacement disks, start the array in normal mode, and see if the emulated missing disks mount. It should show you on Main how much space they have if they mount. You can even take a look at the files on the emulated disks, even though the replacement disks are not assigned and even though those replacement disks don't actually contain any of the data. Their data is emulated by calculating it from parity plus all other disks. This is what parity is all about.
 
If that all looks good, stop the array, reassign the replacement disks, and start the array to begin rebuilding the emulated data to those disks.
 
Ask if you have any questions or if something doesn't seem to work as explained, and please don't deviate at all from what I have described.

Looks good.

Your earlier diagnostics showed disabled/emulated disk4 mounted with more than 6TB of contents. You can examine the emulated contents if you want. The emulated contents is exactly what will be rebuilt.
 
Assuming that is still the case, you can rebuild the disk to itself. Or you can rebuild to a spare if you have one and keep the original as is in case there are problems with rebuild. But should be OK to rebuild on top.
 
Looks like you let google find an old wiki link. The current documentation is linked at the top and bottom of the forum, and in the manual link at lower right in your Unraid webUI.
 
https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

I moved your post to a better subforum. The one you posted in was about plugins, not dockers. Have you read any of the Docker FAQ pinned near the top of this subforum?
 
 

No, it just means parity could not have recovered anything if you had lost a disk, since you already had a missing disk.
 
That is the only way to get parity back in sync with your array so you have parity protection again.
 
Post new diagnostics after you start the array.
 
 
 
 

You would set it to use pool Only to get new files to stay on the pool and be ignored by mover. Yes means move to the array and Prefer means move to pool.
 
In addition to that setting, you also need to specify which pool to use. I assume you already have a pool named "cache", create additional pools named as you wish and set the share to Only use the desired pool.
 
If the share already has files on the array they will stay there because Only is ignored by mover.
 
All files on all pools are part of user shares just like array disks are.
 
https://wiki.unraid.net/Manual/Storage_Management#Pool_.28cache.29_Operations

You also have to add in the other 2 column totals. Looks like scrutiny logs are pretty large, see if you can do anything about that.
 
Since you have so many containers it wouldn't be unreasonable to increase docker.img allocation, but growth needs to be dealt with.
 
 

It was.
 
That will let you assign any disks as you want and optionally (by default) rebuild parity. You must let it rebuild parity. Be sure you don't assign any data disk to any parity slot.

BIOS sometimes tries to "help" by choosing a boot device when you make any disk changes. Make sure it is still set to boot from the Unraid flash.