itimpi

Are you saying that when you clicked on the icon for that container on the Docker tab there was not a ‘Logs’ option in the resulting drop-down menu?

You could do that as with the largest data drive being 8TB you only need 8TB (or larger) for the parity drive(s).
 
You might want to read up on how parity works here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.
 

If you have a parity check starting by itself then you probably have an error in the scheduling for it.    Perhaps you should post a screenshot of Settings->Scheduler->Parity Check so we can see how you have it set.

There should be a format option near the end of the Main tab.

Anyone with a legacy (i.e. pre new pricing model) licence is entitled to updates for life at no additional cost.

I would simply replace the existing parity1 drive with the new one (and keep the old parity1 intact until parity rebuild completes just in case something goes wrong), although if you want to go the parity2 route and then run without parity1 then that is also viable (Unraid does not mind parity1 being missing).
 
Also do not bother with running a preclear on the old parity1 drive.    Simply add it to the array and let Unraid Clear it which is faster.  The only reason normally for running a preclear is to stress test a new drive and since you have been using it as a parity drive this is not needed.

@X-ray-MD  It looks like you are running an old release of Unraid (6.12.3).   You should upgrade to the current stable release (6.12.10) to see if the problem persists.

If you click on the orange icon against the drive on the Dashboard and select acknowledge then Unraid will only inform you again if it increases.

The first thing todo would be to reboot as that would cause Unraid to be loaded back into RAM from the archives on the flash drive and thus set all standard Unraid system files back to the correct values.   After that you can look into resetting permissions on data files, and for that the New Permissions tool would be a good start.
 
 

Those errors do not always indicate a drive problem.   They can also be caused by power/cabling issues to the drive (in particular power as you mentioned it making a noise).   Running the SMART extended test is a good indication as to whether a drive is healthy or not.  The easier step of getting the SMART information after a reboot to get the drive back online might also give an indication.

The settings you have for ‘appdata’ tell mover to ignore this share so any existing files for the share on other drives are left there.
 
If you wanted to use Mover you should first have set the share to be moved to the array; run mover to get the files moved; and then afterwards set the share to be moved to the new cache drive.
 
in you current situation the easiest (and fastest) thing to do is almost certainly going to be to use the Dynamix File Manager to move all the files off the drives where you do not want them to be onto the new location.

You can always use the manual method of upgrading to get onto the latest stable release.

The syslog is the RAM copy and only shows what happened since the reboot.   It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot and waiting for the issue to happen again.  The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

Not off hand I an afraid.    USB connections are known to cause issues if used for drives in the main array as Unraid is not ‘hot plug’ aware and cannot handle such drives disconnecting even if they promptly reconnect again.

If you do have a parity drive then the obvious answer is to use the standard process for replacing a drive to get one of the 4TB replaced by a 10Tb dtive.   Even if something goes wrong with the replacement as long as you keep the 4TB drive intact then you will have that to fall back on for getting your files.

yes you could split it later, but it might make sense to do it now by:
use Tools->New Config to allow you to reset the array return to the Main tab and (optionally)move the HDD to be disk1.   Note that it is also possible to leave disk1 unassigned assign the SSD to be a pool. start the array to commit the change.    Existing data on the drives will be retained. if you are using docker containers you might want to install the appdata backup plugin to make periodic scheduled backups of the appdata share from the pool to the main array.

You can only remove a drive from a multi-drive pool if all aspects of it are set to a RAID1 profile or something similar.   According to your screenshot this is not the case as metadata, etc are set to Single profile.

I am confused - why not simply have a Movies folder on the NVME drive?
 
When you create a folder called Mover then it would normally automatically create a share of that name with default settings.   If you want that to always stay on the cache make sure that the Secondary Storage is set to None.

The fact that you say the same amount of space is used suggests that you have probably managed to put the files somewhere unexpected.   What were you using to do this mass move?
 
When you say you think  files are missing is this browsing over the network or looking locally?  Have you tried browsing the drives using something like Dynamix File Manager?

You should be able to simply do:
Stop the docker container Move the data to its new location. Edit the volume mappings for the container to point to the new location on the host side. restart the container.

Not sure that version is still accurate as it is in the 'legacy' part of the documentation.   The current online documentation for that is here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.  In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. 

The syslog suggests you are getting macvlan related crashes and the syslog has
Apr 26 13:14:13 Nexus root: Fix Common Problems: Error: Macvlan and Bridging found This combination is known to cause instability on many systems.
 
As mentioned some time ago in the 6.12.4 release notes you need to either switch docker networking to use ipvlan or if you want to continue using macvlan then disable bridging on eth0.

Not perfect, but you can select a folder(s) and then use the Calculate button to get the size of the contents of the selection.

Does the server still boot in Safe Mode?   
 
If so then one of the plugins you have installed (or anything left in the /boot/extra folder) is the likely culprit.  Unfortunately sorting out exactly which one is going to be a trial and error exercise of disabling some and then rebooting.   You can disable any particular plugin by renaming its .plg file to have a different extensions and then rebooting.  Reversing the process will re-enable them.   You should probably start by disabling any you know load new binaries that could replace the standard Unraid versions (e.g. NerdTools, Python3) as these are most likely to interfere with Unraid operation.
 
You could also see if a fresh install on another flash drive (no licence needed) will boot.  This would show if there is something inherently wrong or whether it could also be something in the config level.
 
I would also take the opportunity to make a copy of the flash drive while you can to make sure you have a backup if needed.
 
 

If you are not certain of our drive assignments then you may find this section useful from the online documentation accessible via the Manual link at the bottom of the Unraid GUI.  In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.