itimpi

Unraid does not need a GPU, but your motherboard might.   Have you checked the motherboard manual?    It could also be a BIOS setting.

This topic is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.

My guess is you have the Dynamix File Manager plugin installed on one server and not the other?
 

Yes - the shares unexpectedly showing as protected have all their files on disk1 and appdata also has some files there.
 
Note that simply changing the primary storage to a pool and removing the secondary storage does NOT automatically transfer files onto the pool.  To get the files into the right location you will need to:
stop docker and vm services under settings as these will stop any files they have open from being moved. for the shares you want to only be on a pool set the pool as primary storage and the array as secondary storage. set the mover direction to be array->pool manually run mover from the Main tab to get files moved onto the pool. when mover finishes you can remove the secondary storage=array as it is no longer needed re-enable docker and/or vm services (optional) enable the option to use Exclusive mode shares under Settings->Global share settings.   This gives better performance for shares with all files on a pool by by-passing Unraid’s fuse layer for such shares.

You need to rerun that check without -n and add -L

You should be able to copy the syslog files without shutting down the syslog server.

That shows something is actively configured to issue the shutdown command, so it is not a crash.
 
Have you checked that you have nothing configured to run at that time?  Feels like it could be a User Script.   One small clue is that is using the ‘powerdown’ command to do this rather than the ‘shutdown’ command.   Have you tried looking at something like /etc/cron.d/root to see if it contains an entry for that specific time?

There is no way to tell what the parity check is doing in terms of any files that might be affected (parity does not understand the concept of files).  It just knows how far through the check it has got and it tells you that in the GUI.
 
Chances are that since disk2 is a new large drive all new files are going to it thus explaining the write behaviour.
 
Probably the best thing to do at this point is to run a check filesystem on all array drives to check there is no corruption at that level, and assuming it all looks good run a parity check with the option to correct errors set.
 

Have you tried unsettling the option in the pool settings to allow it to be used for User Shares?   Nor sure if that would work or not?

Have you rebooted since trying to install the purchased licence key?

Looking at you share settings what you are seeing is expected behaviour.
 
With you largest data drive being 10TB and using high-water allocation method then the points for switch drives occur at the 5GB, 2.5GB, 1.25GB etc points.   You are currently in the 2.5GB zone, and since disk1 is down to 1.25GB free Unraid has switched to disk2.

Each pool can be configured independently both in terms if the number of drives in it, the type of file system and any raid levels.

If you have hard links then the space will not be released until all such links are deleted so there are none remaining for any given file.

For security reasons a password is now mandatory even when logging in locally.    You could always set your browser to remember it.

Try removing the Mover Tuning plugin.    Been quite a few reports recently of it causing this sort of issue.

You could try uninstalling the Mover Tuning plugin and see if then woks as expected.

Leaving a gap is not a problem.
If you want to close the gap then it would involve rebuilding parity to match the new drive assignments which you say you do not want.
 
FYI:  If you only had parity1 then this could have been done without a parity rebuild as parity1 does not use disk number as part of its parity calculations whereas parity2 does.

Yes to Maintenance mode, but no need to use terminal as you can do it from the GUI by clicking on the drive in the GUI as described in the link and this is recommended as less error prone.

You have Export=No which means they are not available via the network.   for security reasons this is the default setting and you have to explicitly set it to one of the other options.

The ‘nobody’ user is normally the correct user.   Have you tried running Tools->New Permissions against a share which has these problems.

Your Split Level setting is too restrictive.  Split Level will over-ride the other settings in the event of contention on selecting a drive.

If you restart in normal mode then the emulated disk should now mount and you can check that it has the data you expect.   When you get around to rebuilding then the contents of the emulated disk will be rebuilt onto the physical replacement drive.

You have a limited number of automated licence transfers per year.    If you need to do more than that then you need to contact support.

Not at the moment as far as I know.   
 
Whether an official API is ever going to appear I have no idea but with the large number of internal changes likely to be needed for the 6.13 release that release is probably Limetech's priority at the moment.

That is expected behaviour.    The potential cutover points are based on the size of the largest data drive.   Since you say this is 8GB the first cutover point will occur when disk1 has 4TB left.    Since at this point no drive has more than 4TB free then disk1 will continue to be used until it has 2TB free.    It as that point you should expect disk2 to be used until it is down to 2TB free, etc
 
This is described in some detail here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.