Hi,

I've had a 240gb ssd cache for over 7 years now - time to upgrade as my system would come to a crawl due to the cache being filled up.

I followed the methord of turning everything away from the cache, and just point it to my array and running the mover.

after this i turned the system off, swapped out the drive, turned back on the machine - did NOT turn off my dockers, and wiped the new cache drive to give me 1Tb.

I have switched over ther shared to the new cache, but move does not seem to do anything and and my dockers have not returned.

I can return them manually via the previous install but that does not bring across meta data, such as sabzbd history etc.

I did run ca backup before this but a restore does not seem to work, i can see my docker .img on my array sitting at 120gb

my appdata is also on my array, but im slightly dubious it is not everything.

currently manually building my docker manually - is there any other way i can do this ?

I do have the old drive, and have tried to attach via a unassigned drive but it does not seem readable, it is btrfs.

possibly a mistake i've made and not done enough research for this. i just would like to have meta data of plex, sab etx, which i suspect is what took up so much space on the docker.img.

Thank you,

jgrbb

Edited November 3, 2025Nov 3 by grjbb

so, i could not mount the old cache drive alongside the new one.

I removed the new on, and inserted the old one and started the array, with no cache drive assigned. this has allowed me to mount the drive, and move the data on that drive to the array - hopefully i can rebuild what i need from that.

any advice or tips is greatly appreciated. i presume my mistake was not turning off the cache drive upon starting up the server with the new drive implemented, not allowing the drive to be recreated. its all abit of a mess.

Please post the diagnostics.

6 hours ago, JorgeB said:

Please post the diagnostics.

Sorry, here are my diagnostics - the dockers now load but all history etc is missing and a good majority of them do not load anymore

Edited November 28, 2025Nov 28 by grjbb

Cache is 98% full, and the appdata share has the floor set to 100GB, so it cannot write to the pool. Either free up some space or adjust the floor, or better yet, both, then reboot to clear the logs and post new diags.