[email protected] Posted November 12, 2022 Share Posted November 12, 2022 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. Quote Link to comment
JorgeB Posted November 12, 2022 Share Posted November 12, 2022 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. Quote Link to comment
[email protected] Posted November 12, 2022 Author Share Posted November 12, 2022 Thanks for confirming. Syslog attached. Also here is my drive config as you may not see what you need from syslog syslog Quote Link to comment
JorgeB Posted November 12, 2022 Share Posted November 12, 2022 Log is filled with the mover logging, but not seeing anything else of concern, reboot and post new diags after array start. Quote Link to comment
[email protected] Posted November 12, 2022 Author Share Posted November 12, 2022 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 Quote Link to comment
JorgeB Posted November 13, 2022 Share Posted November 13, 2022 You formatted cache again? Quote Link to comment
[email protected] Posted November 13, 2022 Author Share Posted November 13, 2022 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. Quote Link to comment
JorgeB Posted November 14, 2022 Share Posted November 14, 2022 Reboot to clear the logs and post new diags, also a screenshot form "Shares" -> "Compute All" Quote Link to comment
[email protected] Posted November 14, 2022 Author Share Posted November 14, 2022 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 Quote Link to comment
JorgeB Posted November 14, 2022 Share Posted November 14, 2022 You still have appdata in the array, move everything back to cache. Quote Link to comment
[email protected] Posted November 15, 2022 Author Share Posted November 15, 2022 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 Quote Link to comment
JorgeB Posted November 15, 2022 Share Posted November 15, 2022 Appdata is still on the array, enable the mover logging, run the mover, post new diags. Quote Link to comment
[email protected] Posted November 16, 2022 Author Share Posted November 16, 2022 (edited) 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, 2022 by [email protected] Quote Link to comment
JorgeB Posted November 16, 2022 Share Posted November 16, 2022 Diags are not available to download, post again. Quote Link to comment
[email protected] Posted November 16, 2022 Author Share Posted November 16, 2022 media-diagnostics-20221116-2020.zip Quote Link to comment
JorgeB Posted November 16, 2022 Share Posted November 16, 2022 Lots of strange errors, do you use symlinks or hardlinks? Quote Link to comment
[email protected] Posted November 16, 2022 Author Share Posted November 16, 2022 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 Quote Link to comment
[email protected] Posted November 16, 2022 Author Share Posted November 16, 2022 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 Quote Link to comment
Solution JorgeB Posted November 17, 2022 Solution Share Posted November 17, 2022 You'll need to move those manually. Quote Link to comment
[email protected] Posted November 18, 2022 Author Share Posted November 18, 2022 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 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.