itimpi

Look into the config/shares folder on the flash drive and check that all the .cfg files have the same capitalisation as the folders on your disks for the share.

There should be a file '/boot/config/share.cfg'.

Try going to Settings->Global Share settings and check there that the values there are what you want. If necessary make a dummy change and then hit Apply and the required file should be generated.

If things still do not work you are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread and mention a share you expect to be moved that is not being moved.
It is always a good idea to supply diagnostics to allow us to see the current state of your system and so we can see logs.

A point to note is that Unraid recognises disks by their serial number - not by how they are connected so (as long as you are not using a RAID disk controller). You can reply them to different physical connectors without affecting your Unraid configuration.

A much faster process to achieve what you describe would be:
stop array and replace both iTB parity disks with the 10TB drives you plan to use to replace them.
Start array in Maintenance mode to rebuild both parity disks in parallel. Keep the old parity disks intact at this point to give you a recovery scenario if one of the data drives fails before parity is rebuilt.
Stop the array and unassign 2 of the the 6TB drives you want to replace.
Start the array and confirm that Unraid mounts the ‘missing’ drives by emulating them using the remaining drives + the new parity drives. Check the contents look OK.
Stop the array and assign the old 8TB parity drives in their place.
Start the array in Maintenance mode to rebuild their contents onto the 8TB drives. No need to clear these drives first as the rebuild overwrites every sector anyway. Keep the old 6TB drives intact for now
Stop the array and Unassign the remaining 6TB drive.
Start the array to check it is being correctly emulated.
Stop the array.
Assign another 10TB drive in place of the just removed 6TB drive.
Start the array to rebuild the contents of the old 6TB drive onto the 10TB drive
You can then follow the standard process for adding the last 10TB drive as a new data drives.
BTW: the documentation has not been removed - it has just been reorganised. Array operations are covered here

As long as you do it maintenance mode (so no data writes happen) you could change both parity disks in the same step. Just keep the old parity1 intact until parity is rebuilt in case a data drive fails while building parity as that leaves a recovery option available.

Your current step 4 involves rebuilding parity again as you are removing a drive so maybe omit step 4 at this point and leave current disk4 in place until you are ready to replace it?

As far as I can tell looking at the diagnostics you have no shares that are configured to move files from cache to array that actually have files on the ‘cache’ pool. Perhaps you should give the name of a share that you think should have files being moved by mover and for which this is not happening.

It was a requirement in earlier Unraid releases. The ability to use only pools and have no main array was new with Unraid 7 so probably the post was referring to a workaround for an older release.

In my experience if anything it is safer than doing the GUI update.

Make sure that the timeout for VMs (under Settings->VM Manager (advanced view) is sufficient to allow your VMs to shutdown, and that the Shutdown timer for the disks (under Settings->Disk Settings) is larger than the VM value.

This can happen if you ever get the same filename duplicated in multiple locations/drives (which is not meant to happen). When this happens Unraid will only show the first one. However an action such as delete or rename on that first copy would then reveal the second copy giving the symptoms you describe. The commonest cause of this is when manual copying between drives on the server has been done. Whether this could apply to you I am not sure.

Are you sure that none of the disks were used to replace a disk that had failed (and been originally formatted in an earlier Unraid release). A rebuild always restores the original file system exactly.

Follow the process for reformatting a drive as documented here. Do it twice, the first time selecting something other than what you want to finish up with, and then a second time setting it to XFS (which will automatically now be v5).

Your diagnostics shows
appdata shareUseCache="prefer" # Share exists on cache, disk7 system shareUseCache="yes" # Share exists on disk6, disk7Both of these will impact performance as you want them entirely on the cache for best performance.

To rectify this:
Disable the Docker and VM services under Settings
Change the 'system' share so that it has the mover direction as array->cache
Run the mover to get the content of these shares moved to the cache
Once the move has completed you can remove the Secondary storage location for both shares so that they become "cache only" shares
Go to Settings->Global Share settings and enable the Exclusive shares option. This helps performance by by-passing the Unraid Fuse layer for cache only shares.
Stop and then restart the array to activate the Exclusive share option for the 'appdata' and 'system' shares.
You can now re-enable the docker and VM services.
You should now have Docker optimised for best performance.

As was said you cannot have two flash drives with the label ‘UNRAID’ plugged in. If you want to use one in a VM it has to be labelled something else as described in the documentation for running Unraid in a VM here.

This is typical of a LAN cable where not all 4 twisted pairs make end-to-end contact. The 100Mbs speed only requires 2 of them to be operational so you can see a silent degradation from the expected 1Gps to 100Mbps. If it is not the cable itself that is faulty then it can be an issue if the socket the cable plugs into is not connecting all pins.

Not sure if there is a failure mode of the LAN card/chips that can cause similar symptoms.

What you want is not supported.

However if you have no parity drive, then writing to array drives is reasonably fast anyway although limited by individual drive speed, and also you can write multiple drives in parallel without them impacting each other's speed.

You might want to check that the capitalisation of the .cfg files for each share on the flash drive in the config/shares folder matches that of the actual share folders on the drives.

Do NOT use New Config because as the warning said you could then not rebuild the array drive.

click on the ‘cache’ pool on the Main tab and select the option to Remove Pool. You should then be able to start the array to begin the rebuild.

For mover to do anything you need to have both Primary=pool, Secondary Storage=array, and the mover direction pool->array to achieve getting the files moved off the pool and onto the array. You should also have Docker and VMs disabled in Settings as they can hold files open and stop them being moved..

Looks like the S3 sleep plugin is actively shutting down the server. I suggest either disabling it or removing it. Not even sure that plugin is compatible with recent Unraid releases.

You can connect via USB for the Preclear. However doing so will make no difference to the rebuild which ignores the Preclear so the only purpose would be to stress test the drive before using it in the Unraid array.

Yes.

I would say that the obvious answer is to set the Logging setting back to its default of disabled. The Help for that setting does warn you that the log is being written to RAM.

You appear to have a corrupt docker image.

You should really push the full diagnostics zip file as then you are more likely to get useful feedback.

Your data should be fine.

Since you have the licence key file then you can follow the procedure described here to get your drives sorted.

If at any stage you have questions feel free to ask them

The rebuild process works at the raw sector level and has no idea of the meaning of the contents of any sector. It therefore rebuilds a disk exactly as it was preserving hard links.