trurl

Set the share Security to Private

Same for me

Working for me.

The "same issue" referred to is this thread: https://forums.unraid.net/topic/87378-server-fails-to-start-after-update Since the specific details are likely to be very different, and we should let that other thread be dedicated to supporting its OP, I went ahead and split this hijack into its own thread. I will ask some of those same questions from that thread though:

Just for completeness, there is also a share anonymized as t--t. That share is cache-no and has files only on disk1.

I don't see a share named SuperFastTest. There is a share anonymized as F------t. It is set to cache-yes and has files on cache and disk1. Possibly you wrote the test file to that share before setting it to cache-yes, so the file went to disk1, and any attempt to replace it or read it would be to the existing file on disk1. There is another share anonymized as S------------e, could this be the one you mean? It is cache-only and has files only on cache. See if you can clarify your description and perhaps repeat the test taking this information into account.

What is the name of the share?

Hotswap isn't really that useful in Unraid, since you can't replace a disk without stopping the array anyway.

Probably best if you don't attempt to use USB for your Unraid disks. Unreliable connections will be a constant cause of disabled disks and parity failures. Maybe if you wanted to run without parity you could get away with it.

The reason it's not news is because all of that is already explained in the thread for the plugin. So anyone using that plugin should already know that.

I should have split this off immediately since it was a hijack and since it didn't really serve @asopala where it was anyway. I don't think there is anything in that other thread that is really relevant to this one but I link it here anyway: https://forums.unraid.net/topic/87378-server-fails-to-start-after-update So now we can start by asking some of the same questions we asked the OP in that other thread:

Filling docker image is about the settings within an application that causes it to write to a path that isn't mapped. If you use Transmission for example, and within the Transmission application you set it to downloading torrents to /download, but the container mapping is /Download, then that is going to write into the docker image, because Linux is case-sensitive and /download and /Download are different paths. Or, if you tell it to write to download instead of /download, then that is going to be in the image also, since it is not an absolute path. Taking them one at a time as suggested is the way to get this figured out. Which dockers do you use?

Still doesn't look like your user shares are working. Shutdown, put your flash in your PC and let it check disk. While there, make a backup. Then go into your flash drive and delete the config/shares folder so it can be recreated based on your actual disk contents. Then put flash back in your server, be sure to use a USB2 port, boot up, and post a new diagnostic.

Do you have any spare disks to test with?

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

Earlier you posted diagnostics and a screenshot that showed you had no user shares, presumably because you had corrupted cache and broken user shares. As I said before Did you ever get your cache setup again, or at least removed, so your user shares are working again? I suggest you forget completely about your dockers and wait until we agree that your system is setup well enough to allow your dockers to work. Post new diagnostics.

Go to Main - Array Operation and Stop the array, then do New Config as explained.

Tools - New Config will let you assign the disks as you want. Then start the array and let it build parity. You will have to format the new data disk, either during or after parity build.

And you should forget about that 2TB in cache pool. That was a bad idea. Just start over with cache and that single SSD

Have you fixed your cache issue yet? Probably pointless to worry about restoring cache until you get a working cache pool. Since your user shares didn't seem to be working before then probably CA Backup can't access the path you set for the backup.

Your array disks and their data should be fine. Your docker problems are because dockers are on cache by default. If you remove cache and start the array the user shares on your array disks should be accessible. You have possibly the largest number of files in config/shares on flash that I have ever seen. Did you really have 188 user shares? Did you intend to have that many?

User Shares are the preferred way. They are folders that span drives. Each user share is a top level folder on one or more disks with the same folder name. Each user share has settings that control access and how Unraid uses the disks for that share. Each array disk is an independent filesystem that can be easily read on any Linux. Each file exists completely on a single disk. Folders can span disks as explained above. Just add a new disk to a new slot. Or you can increase storage by replacing a disk with a larger disk and letting it rebuild the contents. Each data disk can be no larger than any single parity disk. Just replace the disk and its contents will be rebuilt to the new disk. Yes, the Unassigned Devices plugin. Cache was originally used to speed up writes to the server, since they are not affected by parity update speed. Then during scheduled idle time the cached writes are moved to the array. Cache is now used in other ways, to increase performance of dockers and VMs for example, with some things meant to stay on the faster cache. Each user share has settings for how it uses cache. If you mean in some sort of failover role, no. In fact, I see no point in having another "boot" flash plugged in since it could confuse things and can't be used as failover anyway. Better to just keep a backup of flash on another computer. You can download a zipped backup at any time, and there are plugins to automate flash backup. Then you can prepare a new flash from the backup. Have you read the Product pages linked at the top of all forum pages? Here is a link to the wiki Overview: https://wiki.unraid.net/UnRAID_6/Overview

Long story short, in case you are still unsure. No reason to move the data. Just rebuild the disk and the data will be on the rebuild.

Unassigned Devices plugin

You can only rebuild as many disks as you have parity disks, so no you can't do 3 at once. Parity doesn't contain any of your data and can't rebuild any of your disks by itself. It requires data from the other disks to do the calculation. Really it's best to only try to replace them one at a time so you still have some redundancy during the whole process.