I unfortunately wasn't a good engineer. I didn't keep track of when I did changes, so I don't know if one of those caused this or not. I'm totally accepting this is a PEBCAK error, but I'm at a loss of what to look for next.

At some point in the past month my cache said corrupt. Not thinking much about it I stopped the array. reformatted the cache , turned the array back on. formatted the drive and everything looked like it was working moved on with my life.

Now my 1Tb NVME drive is just there. I can put files on it via cli. Unraid has labeled it cache. I tried to put system on Cache only to try to move it off the spinning drives but it's not being used. so my everything is super slow.

cerebro-diagnostics-20250712-2156.zip

1 hour ago, TravisMM said:

I tried to put system on Cache only to try to move it off the spinning drives but it's not being used. so my everything is super slow.

may startup with checking all your Shares

A---e shareUseCache="no" # Share does not exist

a---------k shareUseCache="no" # Share does not exist

appdata shareUseCache="yes" # Share exists on cache, disk4

a----------s shareUseCache="no" # Share exists on disk2

b---------e shareUseCache="no" # Share exists on disk1

B-----s shareUseCache="no" # Share does not exist

b--------n shareUseCache="no" # Share exists on disk5, disk6

C-----s shareUseCache="no" # Share does not exist

C---d shareUseCache="yes" # Share does not exist

C-------c shareUseCache="no" # Share exists on disk1, disk2, disk3, disk4, disk5, disk6

D-----------n shareUseCache="no" # Share does not exist

domains shareUseCache="yes" # Share exists on disk1, disk2, disk4, disk5

D------d shareUseCache="no" # Share does not exist

D-------s shareUseCache="no" # Share exists on disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk8

F----y shareUseCache="no" # Share does not exist

F---------s shareUseCache="no" # Share exists on disk1, disk2, disk3, disk5, disk6

i------g shareUseCache="no" # Share does not exist

isos shareUseCache="no" # Share exists on disk1, disk2, disk4, disk5

M---a shareUseCache="no" # Share exists on disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk8

M-------t shareUseCache="no" # Share does not exist

M----s shareUseCache="no" # Share does not exist

M---c shareUseCache="no" # Share does not exist

N-------d shareUseCache="no" # Share does not exist

P----s shareUseCache="no" # Share does not exist

P------s shareUseCache="no" # Share does not exist

P--x shareUseCache="no" # Share does not exist

P--n shareUseCache="no" # Share does not exist

P--------p shareUseCache="no" # Share exists on disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk8

R-----d shareUseCache="no" # Share does not exist

S----s shareUseCache="no" # Share does not exist

system shareUseCache="only" # Share exists on cache, disk4

T---------e shareUseCache="yes" # Share does not exist

T-----a shareUseCache="no" # Share does not exist

T------------p shareUseCache="no" # Share does not exist

t---------------e shareUseCache="no" # Share exists on disk1, disk2, disk5

T-----m shareUseCache="yes" # Share does not exist

TV shareUseCache="no" # Share does not exist

T-m shareUseCache="no" # Share does not exist

U----------------------e shareUseCache="no" # Share does not exist

v----s shareUseCache="no" # Share does not exist

w---h shareUseCache="no" # Share exists on disk1

w----v shareUseCache="no" # Share does not exist

W------s shareUseCache="no" # Share exists on disk3, disk6

w--t shareUseCache="no" # Share does not exist

W-----g shareUseCache="no" # Share exists on disk1, disk2, disk3, disk4, disk5, disk6

there is 1 cache only Share, system, but there is data still on disk4 (ignored then).

proper way would be for /system, stop docker, vm, lxc (if used) Services, set a "cache only" Share 1st to cache >array (former cache prefer), start the mover (to move files from disk/s to cache), when done, set the Share to cache only and start Services again ...changing the setting (cache only, prefer, array only) will be only for new files ... not existing ones.

on your cache drive are (i assume) currently only 2 root folders, /system and /appdata, while /system is misconfigured (see note above) and /appdata is working, but files are also on disk4 ... /appdata is most likely a cache only share (dont forget your backups in case ...) and if you would like to change this, see description before.

/domains (VM's) also most likely are placed on faster (and silent) ssd disks (cache).

so may rather describe, which Shares should be cache > array (new files on cache, mover schedule will move unused files then to array), cache only Shares (new files come to cache ssd and stay there), and so on ... cache prefer is usually a mess and not needed, just for cleaning up "messed" Shares to move back from array to cache.