trurl

Disk1 mounted and plenty of data. Doesn't look like repair resulted in any lost+found.
 
In future better if you post the results of repair. I assume you did it from the webUI, or at least got the command line correct.
 
SMART for all disks looks fine. Looks like connection problems with disk1.
 
Not related, your appdata, domains, system shares have files on the array.

Connection problems with disks 1 and 2. Stop rebuild, fix connections, try again.

Disk1 is not another disk. It is a disk already assigned to the array.
 
Not at all how things work. Emulated disk4 works just fine as far as Unraid is concerned, and can be read from and written to. Quite possible a lot has been written to the emulated disk and all that would be lost if you don't rebuild disk4 to another disk.
 
Perhaps more concerning, disk4 emulation would probably be broken if you now removed disk1 from the array, and so it wouldn't be possible to rebuild disk4.
 
When I say another disk, I mean a disk not currently assigned to the array.
 
 

https://docs.unraid.net/unraid-os/manual/storage-management/#array-write-modes

Prepare your flash drive as a new install of whichever version and see if that boots. If it boots, copy your config folder from your backup, and see if it will boot in SAFE mode 

contact support

https://docs.unraid.net/unraid-os/getting-started/
 
I would double that 2GB mentioned since upgrade from the webUI requires new version to coexist with everything already on the flash drive including the previous version.

The replacement for disk10 must be at least as large as disk10, but cannot be larger than your old parity drive.
 
Is all of that true?
 

Your docker related shares are all on cache as they should be. Assuming you have all your appdata it should work.
 
Did you delete and recreate docker.img?
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
and reinstall from Previous Apps?
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
 

If anyone does have these problems, first thing is to uninstall Mover Tuning plugin. Next thing is to post your diagnostics to a new thread with a description of your issue.
 
If instead you actually want help with the Mover Tuning plugin, you can go directly to its support page by clicking its Support Link on the Plugins page of your Unraid webUI.

You get to decide what is important and irreplaceable.
 
The issue with disk8 is exactly the same as the issue with parity, requiring the same solution. Except disk8 contains data.
Stop Array. Unassign the disk to be rebuilt. Start the array with nothing assigned to the slot to be rebuilt. This makes it 'forget' the specific disk assigned to that slot, but it remembers there is supposed to be a disk in that slot. Until it 'forgets', it won't know it has been 'replaced'. Stop array. Reassign the disk to be rebuilt. Start array to begin rebuild on the 'newly' assigned disk. You could unassign disk8 at the same time if you want, but don't reassign it if you don't want to rebuild it yet.

Go to Tools - System Devices and uncheck the box for that device.

Unassigned Devices plugin will let you access NTFS disks and/or let you access SMB shares over the network 

Let me summarize just for my own benefit to make sure I haven't missed or misunderstood something since I have looked at a lot of threads this weekend.
 
Yes the drive needed replacing, which was done but rebuild was not successful, so the new disk was formatted so you can copy the data back from the original, which is still having problems but hopefully will work well enough to copy its files.
 
Does that seem accurate?
 
No obvious problems in these latest diagnostics.
 
Dynamix File Manager plugin will let you work with files and folders directly on the server, including that Unassigned Device. Or you can use whatever other method you are comfortable with.
 
Not related, your system share is on disk5. Since your Docker configuration isn't set to use that share I don't know what might be there unless you also use VM Manager. That share would normally be on cache or other pool and configured to stay there, but maybe it isn't really used.

The file is already open by the logger, so you can't edit it.

I never suggested you could do that. Let me know if you need further explanation or more detailed instructions.

Since you didn't New Config and rebuild parity without disk8, it is still part of the array and has been emulated by the rest of the array ever since you removed it. And the emulated disk currently contains over 5TB of data. You will have to rebuild disk8 if you want to keep that data.
 
Since you have dual parity with only 1 missing disk, you still have redundancy.
 
The Shares page has never said anything about emulation.  Mouse-over the red X next to Disk 8.
 
 
If you try to ADD the disk to a new slot, it will let you since you have dual parity. And it will clear the disk so parity remains valid.
 
If you instead assign the disk to the disk 8 slot, it will be overwritten with the contents of the emulated disk. In other words, rebuilt.

Unassigned Devices plugin.
 
However, USB not recommended for array or pools for many reasons.

The way you make it rebuild is to reassign the disk to the same slot and start the array.
 
Check filesystem on emulated disk3. Be sure to use the webUI and not the command line. Capture the results and post them.

Check connections, all disks, both ends, SATA and power, including splitters. Reseat controller card. Ideally no more than 4 disks per power cable.
 
All connections should sit squarely on the connector with no tension in cables that might disturb the connection. Don't bundle data cables.

I have split your thread. Best to keep things separate so there is no confusion.
 
Attach Diagnostics to your NEXT post in this thread.

Sorry, looking at wrong diagnostics again.
 
Your appdata user share should get created when you enable docker.

You can add the new disks as part of New Config, rebuild parity, then format the new data disks. Existing disks will not be changed as long as you keep them assigned as they are.
 
It is very important that you don't accidentally assign any disk with your data to any parity slot or it will be overwritten by parity.
 
https://docs.unraid.net/unraid-os/manual/tools/#new-config

The usual recommendation is to preserve all, then you can change only those assignments you want to change, instead of having to reassign everything. Be very careful when reassigning drives, any disk assigned to any parity slot will be overwritten by parity.

This line in the SMART report for that disk:
 
The normal way of adding disks to the array does not require rebuilding parity.
 
https://docs.unraid.net/unraid-os/manual/storage-management/#adding-disks
 
Since physical disk8 seems to have its data and nothing is wrong with it, I would New Config with that disk assigned as disk8, go ahead and keep disk9 since it is 6TB, leave the others out, and rebuild parity. Personally, I would consider adding parity2 also since you will have so many disks and plan to have more. Of course, it would have to be 20TB parity2 since you already have 20TB data disks in the array. And if you could add it now you could build parity and parity2 at the same time when you New Config.