I was having problems with a single drive. Red blinking light telling me to replace. Instead of doing the smart thing and replacing, I decided to see if this could be repaired.
- I ran SeaTools and SpinRite on the bad drive. Everything came back as passing so I put this back in the Drobo.
- Still showed the blinking red light, I changed positions of the drive thinking it may be a backplane issue. The blinking red followed the drive so it was a drive issue.
- I decided to give the repair route one more try. I upgraded the firmware on the drive and wrote zeros. I got ~60% through (hours of time) and thought this would be enough to try putting the drive back in the Drobo.
My having changed the drive positions… I zeroed the wrong drive (There’s no emoticon for what I’m feeling).
I now have “Bad”, “Mostly Formatted”, “Good”, and “Good”.
I bought new drives (yes, should have been step one) and tried (without luck):
- dd’ing from “Bad” to “New”. “New” now shows as bad as well.
- Moving the HD drive circuit board from a new drive to bad then a new drive to “New”.
Is there anything that can be done besides a good cry, format, and start over.
I believe now the issue isn’t the bad drive as in Hardware Issues, but Drobo sees the “New” as having orphaned files/ corrupt filesystem.
Any way to force a drive to be seen as good so I can at least attempt to run some HFS+ tools on this.
I realize there may be files that were written after the drive was reported as bad, but it wouldn’t be many.
I opened a ticket (online form), and got a call telling me there was nothing that could be done.
This is fine, but I feel like it was a tier one trying to close the case instead of offering options that - while might cost some $$$ or be technically advanced - at least be an option.
Yes I do have backups of the family photos, but I didn’t back up TBs of data that was not as vital - but would still be nice to have.