I've just upgraded my cache drive following these instructions found here

• Stop all running Dockers/VMs
• Settings -> VM Manager: disable VMs and click apply
• Settings -> Docker: disable Docker and click apply
• Click on Shares and change to "Yes" all cache shares with "Use cache disk:" set to "Only" or "Prefer"
• Check that there's enough free space on the array and invoke the mover by clicking "Move Now" on the Main page
• When the mover finishes check that your cache is empty (any files on the cache root will not be moved as they are not part of any share)
• Stop array, replace cache device, assign it, start array and format new cache device (if needed), check that it's using the filesystem you want
• Click on Shares and change to "Prefer" all shares that you want moved back to cache
• On the Main page click "Move Now"
• When the mover finishes re-enable Docker and VMs

 

When I re-enabled Docker, it was empty.   I say a comment on another thread that you can just re-add them via CA previous apps.  I tried this with a single docker and after the reinstall, the docker was running the default config not the config it was running before the upgrade.

Before I try anything else and possibly make things worse does anyone have any wisdom that could get me out of this hole.

 

I'm generating the diagnostics now, does it normally take a long time?  Been running about 30 minutes so far.

39 minutes ago, [email protected] said:

Been running about 30 minutes so far.

If it's taking that long it won't generate them, get the syslog at least:

cp /var/log/syslog /boot/syslog.txt

Then attach it here.

Thanks for confirming.

 

Syslog attached.

 

Also here is my drive config as you may not see what you need from syslog

 

syslog

Log is filled with the mover logging, but not seeing anything else of concern, reboot and post new diags after array start.

I've run the diagnostics from the command line instead of the web GUI which are now attached.  This was before the reboot.

 

and I've also completed the reboot and attached the new syslog.

media-diagnostics-20221113-0153.zip syslog

You formatted cache again?

No, happy to try that if you think it will help.
DO I set all drive back to cache Yes, run mover , format, than cache to Prefer or No, run mover.

Reboot to clear the logs and post new diags, also a screenshot form "Shares" -> "Compute All"

Hi @JorgeB,
Thanks for the continued help on this.

I did change the shares to Cache Yes and Ran mover.  So the logs and screenshots are after doing that change.

New logs attached

 

and screenshot as requested.

media-diagnostics-20221115-0039.zip

You still have appdata in the array, move everything back to cache.

I've done the same as last time, and set appdata and system shares to Cache = yes and run Mover.

 

I've rebooted and grabbed latest diag.

 

and here is the current shares

Is an option to replace the Docker image with the one from the old Cache drive as I do still have the old smaller drive?

 

media-diagnostics-20221115-1734.zip

Appdata is still on the array, enable the mover logging, run the mover, post new diags.

I've rerun Mover with logging now enabled.

New diagnostics attached

The share is still showing some appdata content on array disks. but only a few bytes on 1 drive and a few KB on the other.

There are a few SVG files deep in the Krusader directory, a cookie file in the QdirStat dir and a mongodb-27117.sock file under unifi controller.  Could I manually move these files over manually?  TBH, other than maybe the unifi controller file, the rest are not important and I can redeploy those later if needed.

 

 

media-diagnostics-20221116-2020.zip

Edited November 16, 20223 yr by [email protected]

Diags are not available to download, post again.

media-diagnostics-20221116-2020.zip

Lots of strange errors, do you use symlinks or hardlinks?

I've not changed anything from the out of box setup from Unraid in that regard. I'll check when I'm back home if there are any symlinks within the appdata location

Looks like appdata have alot of symlinks including some of the files that are not moving.

I couldnt find a command to list all files with hardlinks within a directory

You'll need to move those manually. 

I've moved all the files not on cache manually.

I rebooted then turned docker back on and Boom, all my containers were back and working.

Thanks for all your help JorgeB