trurl

Does it show up in your BIOS?

Can you provide more details on how you are trying to access your shares?

The file from the lowest numbered disk is the one that shows up in the Photos user share. No problems otherwise.

The default for multiple cache pool is btrfs raid1 mirroring, so if you have more than one drive in a pool then it has redundancy. Use the CA Backup plugin to backup appdata, virt.img, and flash. Flash is the other piece of the puzzle you will need to restore your dockers if there is a problem, since their templates (the mappings, etc.) are on flash. And finally, you don't want appdata, domains, system shares on the array, because docker/VM performance will be affected by slower parity updates, and because they will keep array disks spinning due to open files.

On second thought, post new diagnostics since this is a change from the previous diagnostics.

Also, your docker image is 75G. Why have you made it so large? Have you had problems filling it? 20G should be more than enough and if it grows you have some application misconfigured. I recommend reducing that to 20G.

Currently, your appdata, domains, and system shares are all on cache where they should be, and where they should stay. But it seems you have configured them to be moved to the array. Change these shares back to cache-prefer immediately.

I am a bit confused by the settings you have for Minimum Free on your shares. Can you post a screenshot of the Settings for you Movies share?

Sorry, I see I already have your diagnostics. Reviewing them now.

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

That sounds fine, and is similar to what I do. So what exactly is the problem you are having that makes you think you need to move anything?

Are you planning to use the user shares feature at all? If so, it would be better if you forget about the disks. User shares allow folders to span disks, allows caching, and other benefits. You can restrict the disks used by specific user shares, and that is really the best way to get things on specific disks.

Not likely to happen unless you do something wrong before getting to the bottom of this issue. Can we work on that now?

OK, I went looking for your other thread. Absolutely you should not remove array disks and try to access them in some other way. I also don't understand why you are trying to You can let Unraid worry about which disk files are on. That is what user shares is all about. And if you really want to move things from one disk to another then it would be faster to work with the disks directly on the server instead of over the network, but I suspect that would require some further learning. Since it seems you are working with disks, you also absolutely MUST avoid mixing user shares and disks when moving or copying files, or you can lose data. This is one of many reasons you should not even share the individual disk on the network.

Unless you Mount the disk in UD you can't Unmount it in UD so I am still confused by your description.

And here do you mean you clicked Mount (instead of unmount) in UD?

Also, post a screenshot of Main, and read this wiki while waiting on further advice: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

Could you explain in more detail exactly what you mean by that? I suspect you are using the word "unmount" in some way other than its technical meaning.

Also, I see from one of your previous threads that pfsense is involved in your network. Can you temporarily eliminate that to see if it helps anything?

I am another one of many who had no problems with that version (which has been out for 5 months now). The fact that downgrading also didn't help you makes it even more likely that something is wrong on your end. My guess would be a corrupt flash drive though that isn't apparent in your syslog. Those diagnostics were taken without the array started. Can you start the array and post new diagnostics? Also, a screenshot of Main might help. Have you tried booting in SAFE mode? Do you have a backup of flash?

Get your appdata and system shares all on cache where they belong. They have files on the array where they will have performance impacted by parity, and where they will keep array disks spinning. Settings - Docker, disable Main - Array Operation - Move Wait for it to complete and post new diagnostics.

Are you sure the share you are transferring to is cached? The default is NO.

Is your Community Applications plugin up-to-date?

Why? Are you not using Unraid?

Do you have or plan to have cache?