- Closed
Hello unRAIDers,
I think there might be a bug with how unRAID starts the array after a disk has been compromised. My apologizes if this has already been addressed. Full disclosure, what I did was reckless by any rational person who values their data, so don't try this on a box with data you care about.
Steps to reproduce:
1. Clean shut down of unRAID v6.8.2
2. Pull a drive out and reformat/repartition it on another box to temporarily use on another computer.
3. When you're ready, put the same drive back into the array and power on. On the main page, unRAID doesn't note that something has drastically changed with the drive and gives the "green light" that the array is ok to start -- No warnings or anything to indicate there's an issue.
4. Not willing to take any chances, I pulled the drive out and let the array start with the missing drive.
5. When I stopped the array and added the drive back in, unRAID then understood that the drive contents needed to be rebuilt from parity.
I doubt anyone would do anything as boneheaded as this, and I'm not sure what would happen had I started the array at Step 3; but maybe there should be some sort of check or a message to the user that the data on the disk has been compromised and needs to be rebuilt?
Anyways, hope this helps.