DroboPro on Snow Leopard.
I do my backups overnight. Went to bed all OK. When I looked at it in the morning the Drobo seemed kind of frozen, the activity light was constantly on not blinking, the disks weren’t doing anything.
I did all your suggestions to no avail. As soon as it connects to the Mac the activity light is solid. No volumes mount and DW or DU can’t help.
I’m in contact with support but given the track record I don’t think I can expect a lot…
How long have you waited for the volumes to (hopefully) appear?
My DroboPro server was acting a little slow yesterday, so I restarted it. Dashboard showed the volume, but it didn’t mount and was not visible in Disk Utilities. I waited a while, and nothing happened, so I restarted again. This time, I happen to notice a lot of processor activity; checking activity monitor I saw that FSCK_HFS was running, using 100% of a processor. (I believe that automatically runs to check volumes which are found to be in incorrect states). It took a long time to finish; maybe 15 minutes. Then the volume eventually mounted.
Quite unnerving, and I’m not sure why it would need to run FSCK after a normal restart.
[quote=“manfredell, post:1, topic:398”]This is going either to ebay or into the trash bin, literally!
Before you do anything else I would DEFINITELY contact DRI support.
An analogy I use at work (no gaffe intended, just a statement - and hopefully you already have contacted support) –
If your house is on fire, would you call the fire department, email the fire department, or post on the forum?
I really hope you can get your data back… I’ve accidentally killed arrays (not on Drobo, but standalone) before and it’s a horrible sinking feeling.
[quote=“manfredell, post:8, topic:398”]Support is going to send me a new unit. Let’s see…
Sounds good. For the time being I’d shut down the Drobo to prevent any future potential damage/corruption/etc.
Hopefully it’s just the Drobo unit itself and your data is safe! fingers crossed
No they didn’t but then I consider mysely a power user, I know when a system is dead. If you wait hours for the system to become responsive, when your dashboard is loosing connection and reconnecting all the time, when the finder and the whole osx become so slow that I can’t work. When all is OK when the dorbo is not connected etc.
And I know when I call it an end, enough of it. I’ve learned from previous Drobo failures that I can’t trust it. I have bought a readyNas just for backup of the Drobo, which I’ve done weekly.
So in the end it was a decision of bugger it and have a life.
From what we figured out now it MIGHT have been a faulty drive, (this would be the 3rd WD 2TB). The Drobo didn’t flag it as faulty but there where items in the log pointing to it.
I have taken out that drive and could format the Drobo, copied the data back to it. Will see what happens from now on.
I’m truly sorry for your data loss. Hopefully you had some kind of an offsite or other backup!
BTE, just for this eventuality, I recommend picking up at least two small, cheap disk drives, 500 GB or less, just to have for spares and test purposes. If you are tying to debug a potentially sick Drobo platform, you don’t need to risk your data – remove those drives and use some replacements instead.