trurl

Have you tried accessing it by IP?

corrupt docker.img. Why do you have it set for 80G? 20G is often more than enough. Have you had problems filling it? Making it larger won't fix filling it, it will only make it take longer to fill. The usual cause of filling docker.img is an application writing to a path that isn't mapped.
 
https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file
 
https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

Nov 17 13:31:57 freesuper kernel: ------------[ cut here ]------------ Nov 17 13:31:57 freesuper kernel: WARNING: CPU: 3 PID: 28384 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Nov 17 13:31:57 freesuper kernel: Modules linked in: macvlan xt_mark xt_nat veth xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat nf_tables vhost_net tun vhost vhost_iotlb tap xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod iptable_mangle ipmi_devintf ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding igb i2c_algo_bit dm_mod dax sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel ipmi_ssif crypto_simd cryptd glue_helper rapl intel_cstate isci i2c_i801 i2c_smbus aacraid intel_uncore libsas nvme ahci i2c_core wmi acpi_ipmi input_leds nvme_core led_class scsi_transport_sas ipmi_si libahci button [last unloaded: i2c_algo_bit]  

It is just telling you that it is going to rebuild parity. There is a checkbox when you start the array that will let you tell it parity is already valid. In any case, it will not change any of your data disks.

Perhaps a better verb than "add" would have been "assign". You need to assign the disks to new slots, not simply install them.
 
New Config, assign the disks as needed, rebuild parity.

You could use Parity Swap to upgrade one of the parity and rebuild the data disk to that former parity. 

If you are booting UEFI, there is a folder on flash that must be named EFI
If you are booting legacy, that same folder must be named EFI-
Boot from USB2 port.

Correct

Have you tried renaming it again? Maybe without the '.'
 
You can edit config/ident.cfg on flash in your PC.

Put flash in your PC and checkdisk. While there make a backup. You will at least have to replace the config/go file with one from a fresh download.

No point unless you just want to exercise your hardware. Parity will be built to the new larger disk whether your current parity is valid or not, or even if you had no parity disk before.

Simplest approach is to delete (or rename) config/network.cfg from flash and reboot, so it will use defaults including DHCP. Then you can go from there if you really need anything different.
 
I always recommend DHCP for everything on the network, then if you want any specific devices to have static IP, reserve those by MAC address in the router. That way everything is managed from the one place it really matters, the router.