I have a ZFS Cache Pool that is acting up. qty 4 1tb SSDs, all SSDs are throwing read and write errors (they ran fine for a little over a year before the errors started). I did a zpool clear but the errors came back. This has me feeling all sorts of squidgy. I would like to get rid of the cache pool entirely at this point.

All of my shares that utilize the cache pool have the same share settings, I have attached screenshots of the settings here.

I would like to do the following -

• Ensure all data which was stored on cache is moved to the array

• Remove logical cache pool

• Physically remove cache drives

If any of you lovely people could lend me a hand with what i need to change in my settings to make this happen, I would be eternally grateful. When I set this system up I had SO much more free time. 4 kids vs 2 kids = no more time for me to play with my toys... HA!

1. Stop Docker/VM services from the unraid settings menu.

2. Assign each share so that each share has the secondary storage assigned, then set mover action so that data is moved from cache -> array and run mover. (note the specific order here)

3. once all shares fully reside on the array, you can remove the cache pool by clicking on the pool name from the Main page, and clicking "remove pool" (array must be stopped)

Edited November 3, 2025Nov 3 by MowMdown

12 minutes ago, MowMdown said:

1. Stop Docker/VM services from the unraid settings menu.

2. Assign each share so that each share has the secondary storage assigned, then set mover action so that data is moved from cache -> array and run mover. (note the specific order here)

3. once all shares fully reside on the array, you can remove the cache pool by clicking on the pool name from the Main page, and clicking "remove pool" (array must be stopped)

Should the shares be
Primary = Cache, Secondary = Array

or

Primary = Array, Secondary = Cache

Thanks much!

for this application, it really doesn't matter since the data is moving off of the cache pool.

Setting array as the primary storage is probably the safer choice so that way when the cache pool is removed, it will already be defaulted to array.

The only critical component is the mover action direction. Currently you have many shares pointing to the cache pool, make sure these are corrected. (yellow = bad, green = good)

Edited November 3, 2025Nov 3 by MowMdown