So this is the first time I've had a drive failure while using DrivePool. I'd like to first say I am quite happy with how the software handled the missing drive, locking the rest of the drives from writing when one went missing helped prevent any errors with SnapRAID.
I am now coming across an issue though. As SnapRAID has recreated all of the files on the disk, including the PoolPart folder, everything sees the drive as the same one it replaced beyond its UUID being different which seems to have caused a conflict in DrivePool. More specifically is that the drive "reappeared" in the pool but it also sees the drive as being one it can add.
Question
CharredChar
So this is the first time I've had a drive failure while using DrivePool. I'd like to first say I am quite happy with how the software handled the missing drive, locking the rest of the drives from writing when one went missing helped prevent any errors with SnapRAID.
I am now coming across an issue though. As SnapRAID has recreated all of the files on the disk, including the PoolPart folder, everything sees the drive as the same one it replaced beyond its UUID being different which seems to have caused a conflict in DrivePool. More specifically is that the drive "reappeared" in the pool but it also sees the drive as being one it can add.
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.