Squid

Unlike "typical" RAID solutions, Unraid does not work any better (or worse) with matching sets of drives, so nothing to worry about 

Quick google search said to avoid the card if possible, but what @itimpi was referring to was the internal power connections coming from the powersupply.  All too often people don't consider that every molex splitter is 
Another point of failure terrible quality to begin with, regardless if you paid $1 or $20 for them And also quite often do not consider the power draw on individual rails coming from the power supply vs the amount of components plugged into them
 
Another possibility depending upon how you're connecting the drives is the SATA connected to the drives.  Reseat.
 
Not saying that any of this is your particular problem.

01:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 2008 [Falcon] [1000:0073] (rev 03) Subsystem: Dell PERC H310 [1028:1f78] Kernel modules: megaraid_sas You've got the controller set up in IR mode.  You still have to tell the controller in IT's bios (CTRL-S IIRC) to either switch to JBOD or create 4x RAID pools composed of a single drive each.
 
Since it's a Perc H310, you'll actually have by far the best results on Unraid (or any NAS) for that matter by cross flashing it to be the generic LSI HBA
 
Lots of information on that in the internet (just search H310 crossflash to IT), and a rather long thread here https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/
 

You've got to reseat the cabling to both ST10000VN0004-1ZD101  ZA29CF7E (disk 10),  and ST10000VN0004-1ZD101   ZA2AJ2XJ (disk 11)
 
Sata is finicky at times and it doesn't take much for continual resets to happen on a slightly misaligned cable (or a bad cable)

Restore the USB from a backup (or manually download the OS version and save all of the bz* files in the zip to the flash drive).  Worse case scenario you would have to set up a new boot device

Actually, that display is correct at the time the diagnostics were taken.  The syslog has a total size of 0 bytes.  Have you by chance deleted /var/log/syslog (or doing anything with it)

Jan 16 07:52:26 Potti root: nginx: [emerg] cannot load certificate "/etc/ssl/certs/unraid_bundle.pem": PEM_read_bio_X509_AUX() failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: TRUSTED CERTIFICATE)  
 I suspect that this is the root of your problems.
 
Delete the contents of /config/ssh and /config/ssl on the flash drive and reboot
 
This could be flash drive corruption, as the system isn't reading the key file correctly (or at all), but that shouldn't affect being able to hit the UI
 

Most people use the Parity Check Tuning plugin so that the scheduled checks run in batches during off hours (ie: mine run between midnight (when I go to sleep) and 4 am (when the wife gets up) and resumes the next day until its completed).  But, yes since there's competing bandwidth depending upon how much bandwidth is required by the media, pauses etc may result

Stop the VM service and docker service in Settings (VM Settings and Docker Settings).  Then
mv /mnt/cache/system/libvirt.img /mnt/cache/system/libvirt.img.new mv /mnt/cache/system/docker.img /mnt/cache/system/docker.img.new Restart the VM service
 
Do the VMs show back up again?  If it does (and it should in theory), then 
rm /mnt/cache/system/libvirt.img.new rm /mnt/cache/system/docker.img.new  
Followed by stopping the each of the services again.  Then change the system share's settings to use Cache: prefer, then Main, run Mover.  After its done, restart each of the services.
 
 
Other comments.  The usual setting for use Cache on the appdata share is prefer, for far better performance (and make a backup via the appdata backup plugin)

MCE was issued during processor initialization and affects some combinations of hardware and is safe to ignore

There's no link being detected on any of your NICs.  You sure the cable is plugged in? (Both ends).  Any lights on the NIC or the switch?

Jan 11 21:22:21 NAS kernel: BTRFS: error (device sdk1) in cleanup_transaction:1942: errno=-28 No space left Jan 11 21:22:21 NAS kernel: BTRFS info (device sdk1): forced readonly  
But, the more interesting thing is that you don't actually have a cache pool named "cache" Rather you have a cache pool named cache_1tb_ssd, but was probably a semi-recent change / addition, but at the time of doing that, you left your various shares all referencing "cache" in the select cache pool option.
 
And the share exists on "cache" and on various disks, but since there is no pool named cache, the files all wind up in RAM.  (Also you'll have to manually adjust the various docker templates you've got (show more settings), and see if anything there is directly referencing /mnt/cache/...
 
After you've got all that fixed up, then reboot, and we'll take it from there (with a new set of diagnostics)
 
 

OTOH, revert the changes you made that were in some thread that put the logs to RAM
Jan 7 14:30:01 KingServer docker: RAM-Disk synced and if that solves it ask about it in the relevant thread.

Probably best to include more detail and talk to @SpencerJ or email Limetech https://unraid.net/contact

Yup.  Same non-issue

Yes in real time.

Is SSH Enabled in Management Settings?

Connect the 2.5G switch to the router (or the switch following it if you have one)
 
Everything connected to the 2.5G switch will communicate with each other at 2.5 regardless of what the speed of the router / switch it's connected to is.

It looks like the network stats plugin automatically tries to download the package on every boot, instead of saving it to the flash drive.  In your case, the network isn't completely up at that time and it fails.
 
Ignore the error (it's harmless), Uninstall and reinstall network stats.  And post in the support thread

Yes, with 2 caveats
 
Virtual Machines if you're utilizing passthrough.  This will require you to reconfigure the devices, ACS override settings etc to match your new system If you utilize on either the old system or the new system a RAID controller set to JBOD mode which changes the serial numbers of the drives will require you to reconfigure the drives since the S/N's may change. Can't tell if you fall into #1, and it definitely looks like you won't fall into #2

You've got an old version of the template that had an issue in it.  Edit the file /config/plugins/dockerMan/templates-user/my-homeassistant.xml on the flash drive and the line that says
<TemplateURL>someURLhere</TemplateURL> change it to
<TemplateURL>false</TemplateURL>  and the devices will not come back on updates.

OTOH, give it more cores.  Minimum requirements are dual core, but *technically* you're only giving the VM a single core (with a HT)  Also wouldn't be a bad idea to enable TPM within the BIOS (It tends to be disabled by default) 
 
What is the CPU you're using?

Settings - Date & Time - also set up the NTP servers (time1.google.com, time2.google.com, time3.google.com, time4.google.com)

By design it has to be a remote path in the template.  After the initial download it is saved.
 
If you can't upload (or find) an image you like remotely, then you can manually copy the appropriate file to /var/lib/docker/unraid/images with the correct naming

I think the system is getting confused with the fact that you've got a br0 and a br1 set up, but br0 has no connection.  Not a networking guy, but probably if you delete /config/network.cfg and /config/network-rules.cfg on the flash drive and then reboot (and then in settings change the IP address back to 10.100.1.100 / Gateway 10.100.1.2) it'll start working fine.  (Either that or use the other ethernet port)