1st one telling me a drive had been removed - WTF?
2nd one telling me it cannot protect my data.
3rd one telling me it is rebuilding drive protection - not to remove any drives/power off etc.
So how did a drive go from “being removed” (which is physically not possible as no one is home!) to now being re-inserted and fine (i.e. it’s now fine and is being re-written with data and parity - aka rebuild.
I have to send logs to support to find which drive caused the issue? Shouldn’t I have access to that information from the UI? What do I do at 3am when the support is closed and I have an issue with my Drobo?
A loose connection wouldn’t wash with me (no offense meant) - how would it have moved to become loose suddenly? I would hope this can be safely ruled out.
And if a drive is bad, why re-introduce it to the array? Surely it should be excluded and marked as bad?
I’m astounded by the lack of factual information I get from the UI and device itself - I’m sat here with 3 critical alerts and absolutely no idea what has or is currently happening.
Well its hard for drobo to tell between a drive which has stopped responding it one which is missing
But yes, the UI needs some kind of log / history so you can see what happened and when and what drive caused it
well in some respects the e-mails are kind of like an ongoing event log - all they need to say is “drive 6 failed” rather than “A” drive failed which is about as much use as a snooze button on a smoke alarm