Yesterday, I got the dreaded notice from DP that a disk had dropped out of the pool. After a reboot, the drive reappeared, so I started the removal process. About 10% in, the drive dropped out again. Rebooting seems to revive the drive, but now it only gets to 0.3% before it drops out. Only the percentage figure shows progress (up to the aforementioned 0.3%) - the actual byte report remains static, which makes me suspicious that any data is genuinely being transferred.
What really sucks is that this drive (a 4 TB WD Red) was almost full. I didn't RAID anything, so it's just a simple JBOD pool.
I'm old and probably going senile, so I have no clue on how to proceed. I'd really like to get the data off the drive (if possible), but I'd rather not spend $1,000+ to do so. I suppose I could contact an outfit like Rossmann Repair Group since they're now doing PC drive recovery, but I don't know if the resultant data structure would even be usable and could be reintegrated back into the pool.
Oh, also of note is that this drive didn't throw out any SMART errors. I know SMART isn't 100% reliable at indicating bad or soon-to-be-bad drives, but it's still weird and irritating. I doubt it's the controller, as there are other drives attached doing just fine. The case's backplane could also be a point-of-failure, but that strikes me as unlikely.
Anyway, I'd really appreciate some pointers. Should I throw the drive into a freezer covered in uncooked rice? If I pull the drive now in its crippled state and try reading it on another Windows machine, what will come up when doing a simple dir or ls? Can I try putting it in another drive bay (I have several free) or will that make DP go bonkers?
And lastly, if worse comes to worst and I have to trash the drive, how can I remove its presence from DP without upsetting the rest of the pool?
I'm using the latest version of DP (2.2.4.1162) on a Windows 10 machine. Thanks in advance.
Question
fleggett1
Yesterday, I got the dreaded notice from DP that a disk had dropped out of the pool. After a reboot, the drive reappeared, so I started the removal process. About 10% in, the drive dropped out again. Rebooting seems to revive the drive, but now it only gets to 0.3% before it drops out. Only the percentage figure shows progress (up to the aforementioned 0.3%) - the actual byte report remains static, which makes me suspicious that any data is genuinely being transferred.
What really sucks is that this drive (a 4 TB WD Red) was almost full. I didn't RAID anything, so it's just a simple JBOD pool.
I'm old and probably going senile, so I have no clue on how to proceed. I'd really like to get the data off the drive (if possible), but I'd rather not spend $1,000+ to do so. I suppose I could contact an outfit like Rossmann Repair Group since they're now doing PC drive recovery, but I don't know if the resultant data structure would even be usable and could be reintegrated back into the pool.
Oh, also of note is that this drive didn't throw out any SMART errors. I know SMART isn't 100% reliable at indicating bad or soon-to-be-bad drives, but it's still weird and irritating. I doubt it's the controller, as there are other drives attached doing just fine. The case's backplane could also be a point-of-failure, but that strikes me as unlikely.
Anyway, I'd really appreciate some pointers. Should I throw the drive into a freezer covered in uncooked rice? If I pull the drive now in its crippled state and try reading it on another Windows machine, what will come up when doing a simple dir or ls? Can I try putting it in another drive bay (I have several free) or will that make DP go bonkers?
And lastly, if worse comes to worst and I have to trash the drive, how can I remove its presence from DP without upsetting the rest of the pool?
I'm using the latest version of DP (2.2.4.1162) on a Windows 10 machine. Thanks in advance.
Link to comment
Share on other sites
20 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.