I am sorry if this is common knowledge, but I have been trying to find an answer and haven't been able to find one.

 

My 500GB cache drive started spitting out SMART errors so I replaced it with an identical 500GB SSD, but now it is showing 1TB capacity.

Is this a known issue and how can I fix it? Does it even matter?

 

Thanks in advance.

 

Edit: When I swapped it out, I added both to the array at once to mirror to the new one and then removed the old one. It is still plugged in, just not mounted, but it seems like it is still writing to the old one even though it's not mounted?

When I add something to cache, then mount the old drive, the files are there as well.

Edited November 6, 20196 yr by planetsiah905
More information

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

Here is the diagnostics zip

diagnostics-20191106-1743.zip

Old cache SSD (sdb) is still in the pool, despite being unassigned, any important data on cache at the moment? It might be recoverable but if there isn't easiest wait is to re-format cache.

Not particularly. I have appdata and all that backed up. I'll move onto array in case and reformat. Should I reformat both drives?

Cleanest way would be to wipe both (or disconnect old one and just wipe new one), stop the array and then:

 

blkdiscard /dev/sdX

 

replace X with one then the other, then start array and format cache, if old cache gives issues wiping doing it just on the new one should be enough, or disconnect old one.

Seemed to work. Thanks for the help.

I am in the process of moving appdata back to cache, but containers seem to be working fine.