trurl

Your first screenshot shows that neither docker was running. Did you stop them or did they crash?

Just to make sure there is no misunderstanding. There is no right-click menu from the Unraid webUI. Many browsers will present a menu if you right-click but that is not related to Unraid. Do you really mean you are doing the normal (left) click?

Says you only have 100M ethernet. Is that expected? Have you done memtest?

And how do you propose to do that? Making it cache is the simplest way to do that. Most of us use cache in just this way. There is no requirement to cache any of your other user shares, and they won't be cached if you don't specifically make them cache-yes. Typically, you will have appdata, domains, and system share as cache-prefer or cache-only, so they will stay on cache for your dockers and VMs to get better performance, and so those won't cause array disks to spin. If you don't want anything else to use cache, don't tell it to.

Since we were repairing the emulated disk, nothing was changed on the physical disk.

Wiki: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Be sure to capture any output in case you need to post it.

Are you entering that in your browser, or is that what results when you click on the icon for the docker and select WebUI?

Have you done memtest? Have you tried the Ryzen tweaks here?

If you feel your post has been overlooked, "bump" the thread by making a new post in it. That way the forum will show the thread is unread again. People often bump a thread just by posting "bump". Many of us read a lot of posts and may not always reply immediately and then we are off to something else or think maybe someone else will take it up. We are all just volunteers here trying to help each other.

Many people think you can recover a formatted disk from parity. You can't since parity is updated during the format and agrees the disk is empty after that. The diagnostics you posted indicate the disks are mounted and the shares have data. And the Array Operations section of the screenshot seems correct. I wonder if this isn't just a browser problem. Have you tried another browser? Do you have any adblockers that might be interfering?

Just thought I should mention. This is not a general recommendation: For future reference, if you get unmountable disks that you think should have data on them, don't format.

The parity drive is not a backup. The concept of parity is pretty much always the same wherever it is used in computing and communications. Parity is just an extra bit that allows a missing bit to be calculated from all the remaining bits. Disk2 is disabled and the emulated disk is unmountable. But, SMART for that disk looks OK. Best approach is to try to repair the filesystem of the emulated disk, then if that is OK rebuild the disk. See here for repairing the filesystem: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Be sure to capture any output so you can post it for further advice.

Not really necessary to physically remove the disk. You just have to start the array with the disk unassigned to get it to "forget" it. So Stop the array. Unassign disabled disk. Start the array with the disk unassigned. Stop the array. Reassign the disk. Start the array to begin rebuild.

Post new diagnostics

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

Wait for it to finish and then we will see if it needs filesystem repair.

See the Cache Pool section of the Unraid FAQ here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-554741

Unraid IS NOT RAID. There is no striping. Each data disk is an independent filesystem which can be read all by itself on any Linux. Each file is completely contained on a single data disk. Any drive not being currently used can be spun down. Because of this, read speed from the parity array is at the speed of the single disk being read. Write speed is somewhat slower due to parity updates. There are 2 methods for updating parity. Each has tradeoffs. One method is faster but still not as fast as writing to a single disk. But because each disk is independent, Unraid allows different sized disks to be used in the parity array, and allows disks to be easily added for more capacity without rebuilding the whole array. There are several ways to use cache. The original purpose was to speed up writes since parity updates are not involved with cache, with that data moved to the parity array during scheduled idle time. The default is daily in the middle of the night, but that can be configured. With the addition of dockers and VMs, cache is also used for better performance of dockers and VMs, allowing these to run without being impacted by the slower parity writes and also so these won't keep array disks spinning. There can be multiple disks in the cache pool, which also provides for some redundancy with multiple btrfs raid models supported for the cache pool. Most people use SSDs for the cache pool. There are literally hundreds of dockers and plugins available to let your server run many different applications, including torrents. Unraid recently added VPN capability builtin with WireGuard. It will allow you to securely access your server or even your whole LAN remotely.

Doesn't look as if the emulated disk was able to mount so rebuilding to it may not give a good result. Since you are already rebuilding it I guess we will just have to wait and see.

The default container settings have the md5 hash of the password 'abc'. The container checks for a match on the md5 hash of the password entry. There are instructions for generating the md5hash for other passwords in the documentation linked in the first post if you want to change the default settings to allow it to use a different password.

What version of Unraid?

Lots of hard resets on connection to disk1. Check all connections, power and SATA, both ends, including any power splitters.

And errors from that SSD have filled your log space. Check connections, rebooting will clear logs. Then post new diagnostics so we can see what it looks like from a clean start.

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

Your settings say appdata and docker image are to be on cache, your shares agree that appdata is all on cache, and your syslog agrees docker image was mounted from cache.