I replaced a failing cache SSD - It was awkward
I spotted a big, red warning yesterday and discovered a 70% full log and my cache SSD was in read-only mode.
This wasn't surprising. My cache SSD is one of a pair I bought around 2013. A 256GB OCZ Vertex 4. It's been in constant deployment in my unRAID server for probably 6 years and in daily driver devices prior to that. It's seen some use.
What *was* surprising (to me) was the process of replacing it. Mainly the fact that it's not a straightforward process in the UI. At one point I found posts on the forum and in this subreddit talking about dropping to the command line to get things done.
I had a 2TB Intel NVMe ready to be a replacement, so my first idea was to just hot-plug that... by first putting it into an external USB enclosure and copy the files across to that drive, before powering down to remove the failing drive and permanently fit the replacement.
Experienced unRAID folk probably know why that was a bit of a non-starter. Something about filesystems.
My next thought was "I could just install the new drive and add it to the cache pool, where it will RAID1 with the existing drive".
Before I did that, I took the precaution of changing my share settings so that the mover would shove everything back to the array. That took a while. THe process went ahead probably at an average of 10MB/s for 99% of the time with literally 2 sprints up to 400+MB/s and some frequent dips into 1MB/s. Thankfully, there was less than 30GB of in-use cache anyway. My unRAID server does very light duties (but I do still benefit from a cache SSD).
Good job on the precaution, because of course you can't simply add a drive to the cache pool, have it RAID1 and then retire the old drive.
After a few permutations of trying this, I followed the "just remove all cache drives and delete the pool and then start and stop the array".
... which got me to "unsupported or missing filesystem!"
... which got me to "just use unassigned devices to clear the drive" (because "Erase" doesn't do the thing you think it might do)
... which got me to "go into settings to enable destructive mode"
... which got me to "well, duh, of course you have to install the unassigned device plus plugin first".
... which then worked.
This process reminded me of when I got my Commodore 64 as a kid. It was amazing. It did cool games. It did fantastic music and sound effects! The thing is, there was no way to make use of the cool bits because Commodore BASIC didn't include any commands to do cool graphics or sound. You were limited to fudging around with obscure POKE commands to get anything remotely "cool graphics" or "any sound at all" to happen. Back then, this was *just how things were* and I had no idea there could have been a better way.
That's the relevance to what I was doing yesterday, except I knew there could (and should!) be a better way. There should have been some cool little wizard process where I can tag a drive as "I want to remove this" (for any reason, not just "it's failing") and the UI should guide me through it with options like "do you want to replace it with a new drive or remove the cache pool altogether?", with the appropriate process after that... "do you want to move the cache data to an unassigned device?"... probably, because power-cycling my server with a failing drive could have resulted in it's read-only status becoming "lol I'm dead" status.
tl;dr I'm starting to fall out of love with unRAID and if I get a hint that any other software does it even somewhat close to what I think the process should be, at some point I'm going to make the move.