Hey Everyone - looking to see how others are handling their configuration for an issue I have had twice. Last night my docker img got corrupt and it locked up the entire unraid box. The box would respond to ssh commands, like to shutdown but never actually perform the command or shut down. I was forced to hard shut down the box. As expected, because this happened last time, this hard shut down caused my cache pool to corrupt as well and require a wipe. No big deal as I backup my AppData folder via Backup/Restore every Saturday. I restored from the backup but obviously anything that was done in NextCloud over the last week didn't show up. For files, because they are stored in the array and not in appdata, I was able to get them to show back up with the occ scan files command. However, calendar and contacts changes were gone for good. Anyone have a solution for losing this data except for running daily backups?

4 minutes ago, MavAce said:

Last night my docker img got corrupt

You probably have larger issues not related to this thread.

 

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

 

I may split this into its own thread after taking a look.

Your system share has files not on cache, and your docker image is very much larger than needed. Creating a large docker image is often a sign that the user has had problems filling docker image so they increase the size. Increasing the size of the docker image will not fix the problem, it will just make it take longer to fill.

 

 

6 minutes ago, trurl said:

Your system share has files not on cache, and your docker image is very much larger than needed. Creating a large docker image is often a sign that the user has had problems filling docker image so they increase the size. Increasing the size of the docker image will not fix the problem, it will just make it take longer to fill.

 

 

Thanks for looking into this. So should I delete my docker image and set it to something like 20G instead? Also not sure how a file in the system share got on disk 5, it is set to Cache Only. Is it typical for a forced hard shutdown to cause issues with a cache pool? I have only ever had to do it twice (the box is on a UPS to handle normal power blips) but both times it has corrupt the cache. 

2 hours ago, MavAce said:

Thanks for looking into this. So should I delete my docker image and set it to something like 20G instead? Also not sure how a file in the system share got on disk 5, it is set to Cache Only. Is it typical for a forced hard shutdown to cause issues with a cache pool? I have only ever had to do it twice (the box is on a UPS to handle normal power blips) but both times it has corrupt the cache. 

You probably created files in system share before adding cache, so they got created on the array, and won't be moved because you have it cache-only and couldn't be moved even if you had it cache-prefer since mover can't move open files.

 

Disable VMs, delete docker image and recreate it at 20G, set system share to cache-prefer, run mover, reinstall your dockers using the Previous Apps feature on the Apps page.

 

Overfilling cache disk or overfilling docker image (a virtual disk) seems to cause corruption, probably more than a hard shutdown would. The reason for needing a hard shutdown really needs to be investigated though. Perhaps overfilling docker image or cache is the cause of your multiple problems.

 

Splitting these posts since they seem unrelated to the nextcloud thread.