Yesterday, I ran Unbalance to move files over to new drives and remove old drives. Afterwards, it appears that almost all of my shares are showing as not protected by parity. This is even happening on the shares that don't use cache.

 

However, my parity drive is still up and running: 

 

And I ran a successful parity check with 0 errors:

Please post the diagnostics.

28 minutes ago, JorgeB said:

Please post the diagnostics.

unraid-diagnostics-20230116-1132.zip

Thanks for reminding me.

The release you are using has a bug with the diags, please update to v6.11.5 and post new ones.

59 minutes ago, JorgeB said:

The release you are using has a bug with the diags, please update to v6.11.5 and post new ones.

unraid-diagnostics-20230116-1327.zip

appdata                           shareUseCache="prefer"  # Share exists on cache, disk1
C--------------------------------pshareUseCache="no"      # Share exists on disk1, disk2, disk4, cache
domains                           shareUseCache="prefer"  # Share exists on cache
isos                              shareUseCache="no"      # Share exists on disk1, disk2, cache
M---a                             shareUseCache="yes"     # Share exists on disk1, disk2, disk4, cache
S-L                               shareUseCache="no"      # Share exists on cache
system                            shareUseCache="no"      # Share exists on disk1

All the shares, expect system, have files (or at least a folder) on cache, so the warning is correct, you can browse cache to check.

Thanks for your help! Looks like there were files on Cache that weren't supposed to be there. I might have forgotten to deselect the cache when I was running unBALANCE if I had to guess.

 

I marked everything as 'shareUseCache="yes"', ran mover, then put everything as I had it set previously and it appears to be working now.

11 minutes ago, azblurbit said:

everything as 'shareUseCache="yes"'

You want appdata, domains, system shares to stay on cache (prefer not yes) so Docker/VM performance isn't impacted by slower array, and so array disks can spin down since these files are always open