OK, so eventually this was going to happen - I have lots of drives, and one finally malfunctioned so bad that it froze up my system.
Removing the offending drive brought everything back to life, except now I of course have a "missing" drive.
Upon rebooting the machine, I "removed" the "missing" drive.
What should I expect the process to be? Keep in ming this is a 25TB pool with 16 drives, so I know that this is probably a multi day process (the drive that died was a 1.5TB drive).
When I went to bed last night it said "measuring" which I expected. Woke up this morning and the system is "balancing". Would my files that were on the drive that went bad now be listed as "unduplicated" and the reduplicating is part of the rebalancing process?
I've never actually had a drive go bad spontaneously without warning, so never seen what DrivePool goes through to compensate for a drive that is suddenly gone.
Question
rtech73
OK, so eventually this was going to happen - I have lots of drives, and one finally malfunctioned so bad that it froze up my system.
Removing the offending drive brought everything back to life, except now I of course have a "missing" drive.
Upon rebooting the machine, I "removed" the "missing" drive.
What should I expect the process to be? Keep in ming this is a 25TB pool with 16 drives, so I know that this is probably a multi day process (the drive that died was a 1.5TB drive).
When I went to bed last night it said "measuring" which I expected. Woke up this morning and the system is "balancing". Would my files that were on the drive that went bad now be listed as "unduplicated" and the reduplicating is part of the rebalancing process?
I've never actually had a drive go bad spontaneously without warning, so never seen what DrivePool goes through to compensate for a drive that is suddenly gone.
Link to comment
Share on other sites
2 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.