Re: No drive failures here
anonymous
January 29 2009, 17:07:04 UTC
There seems to be a serious bug in the Drobo which is causing it to mark perfectly good drives as "failed." Maybe DRI is trying to cover it up by obfuscating their diagnostic logs?
When the Drobo detects a "full timeout" on a particular drive, likely due to buggy code on the part of the Drobo, it will record the occurrence of this error on the drive itself -- so even though there's likely nothing wrong with the drive at all, attempts to clone the "bad" drive to another "good" drive will be unsuccessful: the cloned drive will contain this same recording of the error, prompting the Drobo to declare it "failed" upon insertion.
Perfectly good, new drives, are being declared by the Drobo as failed! Their forums are full of reports of harddrives failing, within months of inserting them into the Drobo. These same users report that no diagnostic tool can find anything wrong at all with the drives.
Stay far away from the Drobo unless you want to lose your data or spend weeks begging DRI to actually help you gain access to your perfectly good data that you're being locked out of due to erroneous drive "failures". Support takes so long to resolve any issues that most people just end up giving up and wipe their drives in frustration.
Re: No drive failures hereapplegoddessJanuary 29 2009, 20:39:34 UTC
*shrug*
drives and enclosures and hardware in general fail. if my drobo fails or acts weirdly i'll be a bit ticked off, but I'm not stupid enough to trust it with the only copies of important data I have. most people are weirded out by the way I act when drives fail, but it's what you get for dealing with lots and lots of them.
so far i've had no issues with the drives since the initial incident. i (in retrospect) now know that one of the drives in my original post WAS failing and was replaced by wd. that's all for me.
When the Drobo detects a "full timeout" on a particular drive, likely due to buggy code on the part of the Drobo, it will record the occurrence of this error on the drive itself -- so even though there's likely nothing wrong with the drive at all, attempts to clone the "bad" drive to another "good" drive will be unsuccessful: the cloned drive will contain this same recording of the error, prompting the Drobo to declare it "failed" upon insertion.
Perfectly good, new drives, are being declared by the Drobo as failed! Their forums are full of reports of harddrives failing, within months of inserting them into the Drobo. These same users report that no diagnostic tool can find anything wrong at all with the drives.
Stay far away from the Drobo unless you want to lose your data or spend weeks begging DRI to actually help you gain access to your perfectly good data that you're being locked out of due to erroneous drive "failures". Support takes so long to resolve any issues that most people just end up giving up and wipe their drives in frustration.
Reply
drives and enclosures and hardware in general fail. if my drobo fails or acts weirdly i'll be a bit ticked off, but I'm not stupid enough to trust it with the only copies of important data I have. most people are weirded out by the way I act when drives fail, but it's what you get for dealing with lots and lots of them.
so far i've had no issues with the drives since the initial incident. i (in retrospect) now know that one of the drives in my original post WAS failing and was replaced by wd. that's all for me.
Reply
Leave a comment