trurl

In other words, not just the log. Did you read the whole link I gave? It tells you how to get diagnostics even when you can't reach the server over the network. I always use DHCP (the default) and then configure my router to give all my wired connections a MAC reserved IP. That way everything is managed in one place. Are you sure that static IP you have assigned will actually work with the rest of your network now? Nothing changed on your network, nothing else has already grabbed that IP? Everything on that same subnet?

Syslog in those diagnostics indicate 3 minutes boot time.

The "Need Help?" sticky pinned near the top of this same subforum: https://forums.unraid.net/topic/37579-need-help-read-me-first/ Diagnostics preferred if you can get them. What does it say the IP address is (top right of webUI)?

syslog

No clue. I can see about 2 minutes delay at that point in your syslog, mine completes in under a second. Here is a link explaining what that is: https://linux.die.net/man/8/haveged It is apparently using various things in hardware to set up random number generation. So I guess it is something to do with your hardware. Are you sure it hasn't always done this? Do you have any other symptoms?

Maybe for your use case you will just have to reboot more often to clear the logs.

Probably wouldn't have helped with this exact problem, but you are using your UPS wrong. It should initiate shutdown after a short power outage. Typical consumer UPS aren't intended to let you continue running on batteries for an extended time. You don't want to run the battery down. Or if you do, then you don't want to start the computer again until you have recharged the UPS.

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Have you tried these Ryzen tweaks? https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

And an SSD in the array can't be trimmed, so you might not want to use the NVME as that required array disk.

Parity not required of course, but you must have at least one disk assigned to the array in order to start.

The main thing filling your logs seems to be a lot of connect and disconnect to your dockers. Take a look at your syslog and see if you can understand what is going on there. Diagnostics don't really tell us much about your dockers.

Looks like you have a duplicate docker image. Go to Settings - Docker and delete docker image. That will get rid of one of them. Find the other docker image, either on disk1 or on cache, and delete it also. (Don't worry, it is easy to get your dockers back just as they were.) Delete the system folder on disk1. Then post new diagnostics.

You are having problems with cache2. Check connections.

I agree you should get better performance, but you might want to reconsider how you are using cache. Mover works best during idle time, and you don't have to cache everything. My cache is for dockers and VMs, and for DVR since there is some performance advantage when playing and recording at the same time. Most of the writes to my server are scheduled backups and queued downloads, so I don't care if they are a little slower since I am not waiting on them. They all go directly to the array where they don't need to be moved, and where they are already protected. Others will have different use cases of course, but think about it. Some people just cache everything all the time without thinking about it.

Whatever they are using must not be sending the tab. The information for autocomplete is on the server side after all.

You can go directly to the correct support thread for any of your dockers by simply clicking on its icon and selecting Support.

Your shares should be there. Any top level folder on cache or array is automatically a share. So you must have a deeper problem than just empty cache. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

Is everything else still working OK? Are you sure you don't have some deeper problem? Post diagnostics.

You system share is cache-yes so mover won't move it from cache. And mover can't move open files so you have to disable dockers and VMs. Set system share to cache-prefer. Go to Settings - Docker, disable. Settings - VM Manager, disable. Run mover. When it finishes post new diagnostics.

Are you sure it is disk2 that isn't spinning down? Your system share has files on disk1. Since your docker and libvirt image are in the system share I would expect parity and disk1 to spin.

Each additional data disk you add will be additional data capacity. If you add another parity disk (up to 2 are allowed) it won't give any additional storage, but it will provide additional redundancy. Each parity disk must be at least as large as any single data disk. So, you can add a lot more disks, each up to 14TB, and they will have parity protection from that single parity disk. Single parity allows recovery of a single data disk, dual parity allows recovery of 2 data disks. Take a look at this wiki overview for a better idea of how parity works, how user shares work, and many other things about Unraid features: https://wiki.unraid.net/UnRAID_6/Overview

You have 14TB data, and 14TB parity. Parity is not data storage. All 14TB it is showing are from that single 14TB data disk.

Upgrade. There are probably a lot of plugins that don't support that old version.

The user shares are just another view of the disks, but it is a view which spans disks. Each top level folder across all disks in the array or cache pool is a user share. Top level folders with the same name are in the same user share. For most purposes you should just work with the user shares and not worry about the individual disks.

If so there will be no way to recover except from your backups.