Chris, if I understand his concern correctly, the DroboPro is effectively in an endless reboot. It might take, say, 60 hours to do the rebuild. Whatever drive (drives?) is causing the problem is failing more frequently. His rebuild will likely never complete. That is one problem, as I see it.
On top of that, DRI has told him he has two suspect drives, one worse than the other. However, at any given moment in time he does not know which drive is being rebuilt, especially since he has dual redundancy. For all he can know, given what Drobo tells him, two drives could be playing tag team.
Now, if he replaces a drive based on what DRI told him yesterday, or even a few hours ago, he might be pulling the wrong drive. For that matter there could be a third drive playing tag team. Hold this thought a second.
I have been very critical of, among other things, the lack of direct real time reporting from Drobos. You have continually responded that the solution is to submit logs and get tech support. Now, totally aside from the issue of what DRI’s tech support policy really is, this is a classic case of why “submitting logs” is not a proper solution for a box that provides inadequate user diagnostics. It is, at best, a frequently inadequate workaround.
To put it another way, I don’t see any clear practical way for him to determine, absolutely and positively (his
liife data depending on it) exactly which drive to replace, at any point in time, unless the Drobo itself (and not DRI support) is telling him what drive has failed, even if only intermittently as is the case here.
The only possible way for DRI to (definitively) help would be if he pulls a log, submits it to DRI, they immediately diagnose the log and tell him which drive is rebuilding. From the time he pulls the log, until the time he pulls the drive (per DRI’s instructions) he must watch the Drobo continuously, alert to a reboot. And no potty breaks! If the machine reboots in the interim then the cycle starts over with a fresh log submission.
It should be clear that the above is not very practical. And even if it were practical, it is also possible that two drives are rebuilding at once (having dual redundancy) and that would further complicate things.
Having been a software developer for much of the last 35 years now, also responsible for customer support for 20 years, it is crystal clear to me the flaws in the current “system”. It is just difficult to articulate without such a fine case study as we have here.
From his last post, he appears to have purchased 4 new drives in order to make an independent backup before he proceeds any further (if not for a permanent solution, I guess). If my understanding of the nature of the problem is anywhere near correct, I think he has made a wise and prudent decision.
I don’t know how well I explained rkuo’s specific concerns but I’ve done the best I can to explain what mine would be if I were in his shoes and I would be surprised if there isn’t much in common between our respective concerns.