I think I messed something up on one of my main unraid servers. I noticed that my appdata was unprotected so I thought I would fix it by designating the array as my secondary storage. When I did that I started to get the warning message in my fix common problems scan when I ran that a few days later. On top of that, the appdata folder on my cache drive still showed "unprotected" so I decided to revert the appdata config back to only the cache drive. Here is the problem. I still have the folder on the array.. What do I do with that data on the array ? Is there any active data in there after I switched back to the cache drive ? Im sure others have done this before, do I use unballance to move it somewhere ?

Edited October 29, 20241 yr by Dooz Owings

Files being "Unprotected" means you do not have a Raid1 or Mirror cache configuration(parity for cache basically).

 

First you can use mover to try and move the files back to the Appdata share on the cache but if there are any duplicate files, mover won't move them because it will not override files of the same name.

 

To do this, under the Appdata share settings, assign the primary storage to your cache pool, set the secondary storage to the array, set the mover option "Array --> Cache." Stop the entire docker service from the settings menu and run mover. Once you're done, set the secondary storage option back to "None"

 

 

If you have files left over you need to decide how you want to proceed further.

 

 

Edited October 29, 20241 yr by MowMdown

1 hour ago, MowMdown said:

Files being "Unprotected" means you do not have a Raid1 or Mirror cache configuration(parity for cache basically).

 

First you can use mover to try and move the files back to the Appdata share on the cache but if there are any duplicate files, mover won't move them because it will not override files of the same name.

 

To do this, under the Appdata share settings, assign the primary storage to your cache pool, set the secondary storage to the array, set the mover option "Array --> Cache." Stop the entire docker service from the settings menu and run mover. Once you're done, set the secondary storage option back to "None"

 

 

If you have files left over you need to decide how you want to proceed further.

 

 

Well , for what its worth... Mover is greyed out so I assume it is running and may take a long while to move stuff. I'll keep an eye on it to see how it goes. Thanks for the pointer...

8 hours ago, Dooz Owings said:

Well , for what its worth... Mover is greyed out so I assume it is running and may take a long while to move stuff. I'll keep an eye on it to see how it goes. Thanks for the pointer...

Update: This was the solution. Everything back online and Fix Common Problems no longer shows the issue and everything is back on the cache drive and running great. Thank you for the assistance.