- Closed
I am running unRAID 6.11.5
I just replaced the mobo/cpu in my server, and while I was at it, I switched an M2 drive that I had connected to a BTRFS cache pool via a USB enclosure directly to an M2 port.
In doing so, the ID of the disk changed, and unRAID won't recognize it as part of the cache pool. When I do a `btrfs fi show` on the other disk in the pool, BTRFS correctly recognizes the disk that now has a new ID (while unRAID does not).
When I try to switch the disk under the new ID into the cache pool from the unRAID web UI, it gives a red X and says "Wrong".
If I start the array up in this state, will it treat the disk as a new disk and wipe it out?
Update: I went ahead and started the array. It shows the disk as "New", and is going through the rebuild process as if it was a new disk. No data was lost since it was set up as RAID1. So, just a waste of time/processing power.