I'm still a little confused as to the order of operations:
1. Drive has sectors unreadable
2. DrivePool has a new 0.00GB file placement limit
3. DrivePool attempting to evacuate data (is this done in my case? How do I interpret that negative number?)
4. Run file scan to "repair data"
5. Pull out failing drive
6. RMA failing drive
Basically the heart of my question is: what do I do now? And when is it safe to pull out the drive and begin RMA?
Thanks
edit: I clicked file scan and it just says the MBR is damaged. Regardless of the issue (I suppose I can see if this is a real drive failure or something a reboot will fix) - has my data been evacuated?
edit1.5: Running chkdsk complained about the disk being RAW - rebooting the machine fixed that issue - so I wonder if this just a false positive or some weird state everything was in.
edit2 (newest): If I can trust that my 2x Duplication works, is it fair to assume that I can simply pull out the drive, let DrivePool re-balance everything with the remaining drives in the pool (there is enough space) - implying that I am temporarily in a state of no duplication for all the files on the drive I just pulled out?
If that is the case, I'm fine with just formatting the pulled-out drive, and investigating further if I need to RMA it - or just throw it back in the pool as a fresh drive.
Question
vfsrecycle_kid
Hi folks,
I've got a drive in a pool that has un-readable sectors (GLOBAL 2x DUPLICATION)
As of right now, it seems Scanner is reporting 4838830 unreadable sectors (2.31GB) after finishing its scan.
I have the option to start a File scan, but I have not started it yet.
---
Meanwhile, on the DrivePool side:
The affected disk has been limited:
There is a red arrow offering: "New file placement limit: 0.00GB"
There is a blue arrow offering: "Duplicated target for re-balancing (-2.04TB)"
A few other drives in the pool have a blue arrow "Duplicated target for rebalancing (XXGB)"
2.2.0.744 BETA x64 Win10
I'm a little confused as to the order I should be doing things here...
DrivePool reports "Duplicating..." and then returns an error related to 2 files, giving me the option to Duplicate. This process seems to repeat.
Looking at this thread:
http://community.covecube.com/index.php?/topic/829-pool-going-to-hell/
I'm still a little confused as to the order of operations:
1. Drive has sectors unreadable
2. DrivePool has a new 0.00GB file placement limit
3. DrivePool attempting to evacuate data (is this done in my case? How do I interpret that negative number?)
4. Run file scan to "repair data"
5. Pull out failing drive
6. RMA failing drive
Basically the heart of my question is: what do I do now? And when is it safe to pull out the drive and begin RMA?
Thanks
edit: I clicked file scan and it just says the MBR is damaged. Regardless of the issue (I suppose I can see if this is a real drive failure or something a reboot will fix) - has my data been evacuated?
edit1.5: Running chkdsk complained about the disk being RAW - rebooting the machine fixed that issue - so I wonder if this just a false positive or some weird state everything was in.
edit2 (newest): If I can trust that my 2x Duplication works, is it fair to assume that I can simply pull out the drive, let DrivePool re-balance everything with the remaining drives in the pool (there is enough space) - implying that I am temporarily in a state of no duplication for all the files on the drive I just pulled out?
If that is the case, I'm fine with just formatting the pulled-out drive, and investigating further if I need to RMA it - or just throw it back in the pool as a fresh drive.
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.