trurl

Reboot, Uninstall My Servers plugin, post diagnostics

I've changed all my hardware more than once, it just recognized my assigned disks and kept going as usual. The reason I mentioned RAID controllers is because they can cause it to not recognize your assigned disks.

Technically, where there is single parity and single data, then they are mirrors just because that's how the calculation works out. And it allows for simpler parity updates that are faster than the usual method. But I don't know why it would ask that question, since the answer is implied by the disk assignments.

You can access the current documentation from links at the top and bottom of the forum, or from the "manual" link in lower right corner of your Unraid webUI.

M--------a shareUseCache="yes" # Share exists on cache, disk1 What is the purpose of this share? Does it have seeding torrents?

That is where they should be if you are doing it right. So nothing to do with the parity swap procedure really. You should disable Docker and VM Manager in Settings until you get cache back in. And post diagnostics before you enable them again. They probably got created on the array and you will need to clean that up first.

I merged your threads since they seemed to be about the same problem but the posts had additional information.

If you are not using a trial key, make sure your basic key is the only .key file in the config folder.

Contact support

Start reading here https://docs.unraid.net/unraid-os/manual/storage-management/#selecting-a-file-system-type

Contact support

Contact support

Have you tried reseating controller? Is it overheating?

yes

Have you filled your log space? Attach Diagnostics to your NEXT post in this thread.

There has been an update to that plugin but I don't know if it is fixed.

You should set that to larger than the largest file you expect to write to the share. Looks like it was set to a calculated value about 1.2T because you had not set it yourself.

Default 20G is probably more than enough for your small number of containers. The usual reason for filling docker.img is an application writing to a path that isn't mapped to host storage. Attach diagnostics to your NEXT post in this thread.

You can toggle the help text for many settings by clicking on its label. You can toggle Help for the entire webUI by clicking Help ( ? ) on the main bar. Highwater is default allocation method for good reason, not Most Free as you seem to expect. Most Free is the least efficient. Split Level takes precedence over other settings. If Split Level says a file belongs on the same disk with other files, that is where it will go. If you want us to take a closer look Attach Diagnostics to your NEXT post in this thread.

@SpencerJ Seems to be other recent threads with similar.

Sorry you went to all that trouble to attach so very many files, but since nobody is going to go to the trouble to download them separately, I have cleaned that up.

Click on the SMART ( 👎 ) warning to acknowledge, and it will warn again if it increases. Parity contains none of your data, so can't corrupt a data disk unless you use it to rebuild one of them.

According to these latest diagnostics: b-----s shareUseCache="no" # Share exists on disk1 b--------n shareUseCache="only" # Share exists on disk1 isos shareUseCache="only" # Share exists on disk1 M--------a shareUseCache="yes" # Share exists on cache, disk1 system shareUseCache="only" # Share exists on cache, disk1 T---------e shareUseCache="only" # Share exists on disk1 u------p shareUseCache="only" # Share exists on cache, disk1 So, you have several shares set to only use the cache drive, but they have files on disk1, including the earlier mentioned "system" share. Merely changing the settings will not move anything. In fact, changing a share to only use cache will guarantee that mover will ignore it, since it is not possible to set a Mover action for shares without Secondary storage. Also, syslog has several entries where mover says the file already exists. Mover won't replace files. And nothing can move or delete open files, so you have to disable Docker and VM Manager in Settings to work with some of these. Might be simpler to clean this up yourself using Dynamix File Manager.

There is always some filesystem overhead even on a newly formatted disk.