trurl

yes, that is the way it is intended to be used. You still need license on TPM, or another flash drive, such as your existing licensed flash drive.

And I alway recommend not using USB for assigned drives for many reasons.

Since flash isn't case sensitive, you can't rename it from media.cfg to Media.cfg. You could have renamed it from media.cfg to media.bak, for example, then renamed media.bak to Media.cfg We have done it that way on other threads, but I forgot.

So in some ways, not that different than SSDs, except with SSDs you have a mirrored boot partition, and another mirrored partition assigned as a pool for storage, all on the same pair of SSDs.

The mirrored boot is where the OS archives and your configuration are stored. This is what Unraid loads at boot, and where it saves changes made in the webUI (your configuration). But it isn't where your license is stored. That is either on TPM or a separate flash drive.

Looks like your Downloads share is fixed now. I guess you will have to delete media.cfg file in config/shares on your flash drive, then apply settings to your Media share.

Post new diagnostics

After that did you

There was a fix for this in V7.2, but I'm not sure what the "fix" actually does. https://docs.unraid.net/unraid-os/release-notes/7.2.0/#storage

The settings you are looking at are really the settings for the nonexistent "media" share, and don't apply to your "Media" share. That is the problem.

You can't mirror your flash drive. Internal boot can be mirrored.

As mentioned Since flash isn't case sensitive, it isn't possible to have settings for your Media share since there is already settings for a share named "media"

downloads is not empty. It has files on disk1

You have a similar problem with your Media share, but in this case, you only have settings for a share named "media" which has no contents so doesn't exist. The Media share has files on cache, but since it has no settings, mover ignores it. After you have fixed those things about Downloads I mentioned, go to the User Shares page and click the CLEAN UP button, then make settings for your Downloads and Media shares.

As you can see in your screenshot, you have 2 "downloads" shares, one named Downloads, and one named downloads. Linux is case-sensitive, so these are different shares. You probably used the wrong case when you specified a path, maybe in one of your container mappings. The flash drive, where your configuration is kept, including settings for each share, is NOT case-sensitive. So it isn't possible to have settings for both of those shares. You should fix whatever created the wrong case, and consolidate those into one share. However, neither "downloads" share has any files on cache currently.

Start your own thread with your diagnostics

Why does your syslog start in Nov 19 if you just rebooted?

Be sure to check power to the drive also. Do you have any power splitters?

Depends, maybe not long unless it has to search for secondary superblock.

Was hoping the array wouldn't be too out-of-sync with physical disk1, and you could New Config it back into the array, disable disk5 and try to rebuild it instead. But doesn't seem likely that would work now. Do you have a disk you can use to clone disk5? Even better, do you also have a disk you can use to rebuild disk1 to, and so keep existing physical disk1 as it is until we can see the results of rebuilding disk1? Or maybe just clone disk5, New Config physical disk1 back into the array, possibly check filesystem on either disk to repair if necessary, hope for the best, and accept whatever data loss results.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/

Format is a write operation. It writes an empty filesystem to the (in this case, emulated) disk. Unraid treats this write operation just as it does any other in the parity array, but updating parity. So parity agrees the emulated disk has an empty filesystem, and an empty filesystem will be the result of rebuilding. The correct thing to do when you have an unmountable disk, whether disabled/emulated, or not, is check filesystem. The only thing I see in that is syslog where you attempted to mount the unmountable unassigned drive. Did you read the check filesystem link? And please, screenshots, not photos. Check filesystem on the unassigned disk and post a screenshot of the output from check filesystem.

SMART for disk6 looks fine. Emulated disk6 is mounted and very full, as are all of your array drives. You really should keep some free space on each in case you ever need to check filesystem. Should be OK to rebuild on top if you fix the connection problem.

My guess is that you formatted it then something created those folders after the format. You can check filesystem with Unassigned Devices.