well. all 5 drives in my FS have been running about 6 weeks now just fine. i physically relocated the drobo from a desktop to a shelf, moving it only several feet, while it was powered off. i re-seated the drive and it was recognized as a fresh new drive and the drobo took off rebuilding on its own. i wouldn’t say the drive failed. i may not have been the most gentle moving it over, but i certainly didn’t drop it either.
actually when i initially populated my drobo some of the drives (2) were not immediately recognized. i think the connectors in back might be a little tight or something. re-seating both got them set properly and they worked. this was bays 2 and 3 (from the top). my failure yesterday was the bottom most bay.
what concerns me most is the auto-recovery that kicked in after reseating the drive. as i said, with my linux server, this would not have happened, i would have had to initiate a rebuild. re-seating the drive and powering up again as i did with the drobo would have recovered from the error without any loss or rebuild. but linux-raid would have recognized the re-attached drive as part of my md set and all would be well.
i understand drobo tries to automate most of the administration functions of managing a raid set, to make it very easy on the user. but on the other hand, this is dangerous behavior that could result in data loss in a situation where there should be no loss.
the worst part, you can’t even protect yourself from it. unless you watch the bays when you restore power after a move and immediately shut down if one drive does not light up. you might not realize what is going on until the unit is on-line and the drobo app issues its warnings. in my experience, it was already too late by then.
and if 3 drives became loose. would it be irrecoverable? better be very careful. as i said, i have no plans on moving my drobo physically again until this issue is addressed.[hr]
the drive was not bad. i know it was unseated because the bay had no light on, so it must not have been making physical contact. so the drobo assumed it had physically failed out entirely.
where does the documentation state not to move the unit with drives in it? yes. i moved it with the drives in it, a distance of all of 5’. as i said, i didn’t treat it like an egg, but i certainly didn’t abuse the unit either. it went from a hard (desk) surface to a hard (shelf) surface. it was not powered up at the time.
as for time, this all occurred within a 15 minute window at most. i powered it down. moved it. powered it up. when it came up i immediately got alerts. looked over at the drobo. saw the bottom bay was not lit up at all. powered it down again. reseated the drive, and powered it back up.