trurl

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post

Post your docker run command for this new docker as explained at this first link in the Docker FAQ:

Not related but why do you have docker image on disk2 instead of cache? Moves between disks in the array such as you are doing with Unbalance may be slower than just writing since it actually has to delete from the source after copying to destination. Also, looks like Mover was running so that might be competing for the disks. How often do you have Mover scheduled? Mover is really intended for idle time.

Not the cause of this problem, but your system share has files on the array. In fact, you have it set to move files to the array. You want appdata, domains, and system shares to be all on cache and none on array so your docker and VM performance won't be impacted by the slower parity writes, and so they won't keep array disks spinning. Do you actually have any VMs?

Did this problem just start after?

You shouldn't need to run very long to determine whether or not you are still getting those in your syslog. You need to fix it, not keep running it without filling your log.

Looks like OP has moved on so I guess you can have this thread. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

That explanation seems unlikely, but glad you got it sorted.

If the share has files in it then it will still exist. You may have deleted it all but it came back.

Only won't move anything. Preferred is the correct setting to get mover to try to move from array to cache. But it may not be able to as noted.

If I had to guess, I would say you have done that with a docker mapping, so it might be a good idea to disable docker until you get this figured out.

You do have a .cfg file by that name (or similar, can't say for sure due to anonymizing). The file is on flash in the config/shares folder. Diagnostics says that share has no files, but diagnostics might be having trouble with that name also. Delete that file from your flash drive, reboot, and post new diagnostics.

UD shares should not appear in user shares. I think you have something else creating a top level folder by that name on some disk. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

Did you mean it also didn't have internet before you upgraded?

The default settings for network use DHCP. Possibly that would result in a different IP than you were trying. If you have an attached monitor and keyboard you can see what IP results from the default network settings.

I've been using MC since Unraid v4.7. I only install Krusader to get an idea of other user's experience with it.

You might get some clue by checking the timestamps of the templates stored on flash in that folder I mentioned in the link.

You have a completely different problem filling syslog: ... Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: CPU 44: Machine Check Event: 0 Bank 7: cc0357c000010090 Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: TSC 0 Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: ADDR 203fba0600 Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: MISC 152108a86 Mar 24 00:32:24 NASL42 kernel: EDAC sbridge MC1: PROCESSOR 0:306e4 TIME 1585006344 SOCKET 1 APIC 35 Mar 24 00:32:24 NASL42 kernel: EDAC MC1: 3423 CE memory read error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x203fba0 offset:0x600 grain:32 syndrome:0x0 - OVERFLOW area:DRAM err_code:0001:0090 socket:1 ha:0 channel_mask:1 rank:0) ... Is this a new build?

You should have posted the zip file. Just wanted to clarify since we don't want you to post all the files in the zip. Just the zip itself, exactly as downloaded.

Post new diagnostics

If the rebuild completed then it is definitely not emulating the disk you upgraded (unless it became disabled since, of course). Not sure why you might think that.

See this post I made yesterday for more explanation if you want to understand how this works: https://forums.unraid.net/topic/90146-docker-fqdn/?do=findComment&comment=836919

All of that is completely contained within the config folder on flash. Make a backup of that folder and you can put it on a clean install.

Looks good. None of system share on the array. Go to Settings - Docker and change your docker image size to 20G then enable dockers. You can add your dockers back just as they were using the Previous Apps feature on the Apps page. But, just as they were may not be good enough, since you had already filled 20G before. How many dockers do you normally have installed?