trurl

That last line in your photo suggests you have additional things to be concerned about. Force reboot then Attach Diagnostics ZIP to your NEXT post in this thread.

Unraid Connect doesn't backup appdata. You have appdata backup plugin installed for that. This might be useful to you:

If you shutdown manually then reboot, is it also unclean? Here is how unclean shutdown is detected: https://forums.unraid.net/topic/69868-dealing-with-unclean-shutdowns/page/5/#findComment-1087704 More useful information in that same "sticky" thread pinned near the top of this General Support subforum: https://forums.unraid.net/topic/69868-dealing-with-unclean-shutdowns/

@mmm77 Are you sure this isn't the cause?

Just noticed this plugin. Some comments: This is fine (and even recommended) if the user share is exclusive to a pool. No need to map containers directly to cache or pool. Probably the most common cause of array disks not spinning down is Docker/VM related shares - appdata, domains, system - with files on the array. Better if these shares are all on cache or other pool since these files are always open. Nothing can move open files so you have to disable Docker and VM Manager in Settings before these shares can be moved.

In binary this is 1000000000000000010000000000000000000000 If you flip that most significant bit it is a more reasonable 4194304 in decimal = 4 x 1024 x 1024 = 4 MB Do memtest before anything else.

Try this command line: unraid-api restart

Is your Connect plugin up-to-date?

FYI Parity has no filesystem so is not mountable.

It is always OK to remove one of the parity disks without rebuilding the other parity disk if you don't change any other assignments. If you add or remove an array data disk that isn't clear you must rebuild any parity still assigned. As long as you don't add or remove an array data disk that isn't clear, you can change the slot assignments of the data disks without rebuilding parity, but changing slot assignments requires rebuilding parity2.

The linked documentation for shrinking the array has 2 methods. The 2nd method preserves parity by zeroing the disk to be removed while it is still in the array. This has the effect of updating parity at the same time as the disk to be removed is being zeroed, so at the end, parity agrees the disk is clear so removing it has no further effect on parity. Then it is OK to New Config/Parity Valid and avoid the parity rebuild since parity is already valid without the removed disk.

Or you can use the File Manager to look at the contents of cache:

prefer cache is the old terminology from before 6.12. The link does discuss versions before and after, and how to work with 6.12 and above. prefer cache is the same as Primary:cache; Secondary:array; Mover action:array->cache. What do you get from command line with this? ls -lah /mnt/cache

The clearing disk isn't added to the array until after it is clear. The clearing operation has no effect on parity, just as the cleared disk has no effect on parity when it is added.

Here is a link in the official docs that also discuss this: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/cache-pools/#moving-files-between-a-pool-and-the-array

Your docker.img and domain.img specify user shares (appdata, domains, system), not specific drives or pools, so it does work automatically if you set those shares to be on the array, and as long as you haven't specified a particular drive or pool for any docker or VM. Then you set them back to prefer cache to get them moved back as explained at that link.

Attach Diagnostics ZIP to your NEXT post in this thread.

You must have edited the host paths instead of the container paths. Then the host paths were created by the container and became new user shares because any folder in /mnt/user is automatically a user share.

Click on the icon for sabnzbd and select Stop. That will let us work on cleaning things up without anything else happening. Then post a screenshot of your User Shares page.

Is sabnzbd the only application doing downloads?

Before you dig a deeper hole Attach Diagnostics ZIP to your NEXT post in this thread.

Still not seeing any drive that might have been disk5. How is that disk plugged in to power?

There wasn't a user share named dwnlds, and the mappings in your containers didn't specify that either. It was Dwnlds. Do you mean you don't have a user share named Dwnlds now?

According to your earlier diagnostics, there was only one share named as if for downloading, anonymized in Diagnostics as D----s I assume this was the user share with the host path /mnt/user/Dwnlds as seen in each of your containers. So where is Dwnlds in this list?

Probably just creating more confusion by having multiple folders for your downloads. And I suspect that isn't what you intended anyway, and just created them by accident. Attach Diagnostics ZIP to your NEXT post in this thread.