After I rebooted my machine, it would not start the array due to: cache - too many missing/wrong devices

So I found another topic regarding a workaround.
1) Unassign the drive from the current cache pool

2) Make a new pool called temp, and assign the drive to that pool, start the array

3) Stop the array, and re-assign the drive to the original pool
4) Start the array and reboot the machine

 

The macine should now be "in the same state" as before all this started. (appdate, domains and system now on the cache)

Except when I go under the Docker and VMS there is nothing....

 

The data is on the SSD, and as far as I understand it as long as the data is on the share, the docker and vms should "just" find it.  

 

any suggestions?

 

7 hours ago, barnonline said:

any suggestions?

The image files for Docker and VMs is stored in the system share. It may have created new ones on the array which will be empty. 

 

Have a look to see if you have two image files for each one on the cache and one on the array.

 

The docker image file is not in the system share, but on top level of the cache drive.

I just went into the docker tab, and clicked on "add container" and then abandoned it without adding anything, and I can see on the modify time that the docker.img have been touched.

 

Regarding the shares (top level folders) appdata, domains & system only exists on the cache drive, NOT on the array.

 

 

Update:  I noticed that the Default appdata storage location was /mnt/user/appdata/  I have now changed it to /mnt/cache/appdata/  but it made no difference.

Oh well... Sometimes it is faster to redo than to figure out what went wrong.

I opted to install the dockers again, luckily I could pretty much remember all the paths and so on.

I have now also installed the Appdata Backup plugin.