After having some stability issues with Cloud Drives on Google Drive, I thought I'd go a little overboard with redundancy. I created six 10TB drives, pooled them with Drive Pool, then enabled file duplication for the whole pool with three copies of each file. Soon enough I started getting checksum mismatch errors on one of the drives. Following advice found in other topics I mounted the drive ignoring checksum errors and tried to run chkdsk /r on it. It ran for a few days and finally gave up with an error stating "An unspecified error occurred (6e74667363686b2e b34)."
Now, I know I can destroy the drive that's generating errors, create a new one and let Drive Pool rebuild duplication but that's going to take a LONG time. Is there any way to recover from this error using the existing duplication data, just overwriting the bad data with the good from the rest of the pool?
Question
davel23
After having some stability issues with Cloud Drives on Google Drive, I thought I'd go a little overboard with redundancy. I created six 10TB drives, pooled them with Drive Pool, then enabled file duplication for the whole pool with three copies of each file. Soon enough I started getting checksum mismatch errors on one of the drives. Following advice found in other topics I mounted the drive ignoring checksum errors and tried to run chkdsk /r on it. It ran for a few days and finally gave up with an error stating "An unspecified error occurred (6e74667363686b2e b34)."
Now, I know I can destroy the drive that's generating errors, create a new one and let Drive Pool rebuild duplication but that's going to take a LONG time. Is there any way to recover from this error using the existing duplication data, just overwriting the bad data with the good from the rest of the pool?
Link to comment
Share on other sites
8 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.