OrneryTaurus

Hi JorgeB, That would be fantastic! Does the console instructions mirror what v6.8.2 used to do? IIRC in that version, it was simply: - Stop the array - Shutdown the system - Replace one of the cache drives - Power on the system - Replace the cache drive in the pool - Start the array - The drive would be formatted as BTRFS and it would automatically rebuild the cache pool raid - Stopping the array will be greyed out until this process is complete ^ - this method functioned just like replacing a drive in the array and having it rebuild which is definitely what I want haha. Thanks so much!

Greetings everyone, I've been reading through the forum and noticed this FAQ post regarding upgrading cache drives: which lead me to the note regarding it still looking to be broken for v6.9.2 Does anyone know if this still a bug? Does it impact users who only have multiple pools, or does it impact single pools as well? I'm looking to upgrade my two cache drives from 500GB to 1TB drives, one at a time, and just need some sanity checking for when I'm ready to do so given this bug. I'd rather not use the 'move to array' method as I have a lot of data inside of my appdata folder and it would likely take half a day. Thanks in advance!

There might be a better way but this should work: Install the same docker container from community applications on unraid Match the settings between the two installations Copy/Overwrite the appdata folder for the old docker container on the new system's appdata location

This is an excellent idea! Here is an alternative that is already in the US if desired: https://www.amazon.com/StarTech-Motherboard-4-Pin-Header-USBMBADAPT/dp/B000IV6S9S/