Drobo

Drobo failure

Hi all,

Since today I have serious issues with my Drobo (1st generation):

It started today with the Drobo crashing when plugging it into USB. Since that, it seems to be pretty much dead: all lights are red and Dashboard is telling me that ‘too many disks were removed’, furthermore every disk is shown with its capacity - so my fear is that the disks’ content are damaged.

I managed to decrypt the diagnostic reports, so now I have a bit more information. The log is here: http://cl.ly/1b2i2S0x2Y1g233e1G3p

I’m seeing that yesterday, everything was okay

However… It goes pretty downhill from there:

[quote]Thu Mar 17 14:18:14 2011: SM::ALARM: PACK LOADED, MUST HAVE BEEN AN EARLIER LOAD FAILURE
Thu Mar 17 14:19:18 2011: DPM::hotPlug: SlotNumber = 1, op = REMOVE
Thu Mar 17 14:19:18 2011: DPM::hotplug: LD #3 matches disk in slot 1 WWN=>S1UYJ1RZ500488 SAMSUNGHD203WI 1AN10003
Thu Mar 17 14:19:19 2011: DPM::updateDis: writing 0x83c4899b83c48fa1/4c to LDs #0 2 4
Thu Mar 17 14:19:19 2011: SM: remove physical disk 1 (logical disk 3)
Thu Mar 17 14:19:20 2011: Capacity: Free=0B(0.00%), Used=2.57TiB(100.00%), Total=2.57TiB, Unprotected=0B.
Thu Mar 17 14:19:20 2011: J2::rebootIfCritical: slot #0 IS CRITICAL AND MISSING REBOOTING

drobo Event Log Generated on Thu Jan 01 00:00:53 1970
1970-01-01,00:00:53: ZoneManager UnloadDiskPackReadOnly called
1970-01-01,00:00:53: ZoneManager UnloadDiskPackReadOnly passed
1970-01-01,00:00:53: RegionManager UnloadDiskPackReadOnly called
1970-01-01,00:00:53: RegionManager UnloadDiskPackReadOnly passed
1970-01-01,00:00:53: ZoneManager UnloadDiskPackReadOnly passed
1970-01-01,00:00:53: ELM: Thu Jan 01 00:00:53 1970: DPM::packViable: numDisks = 4, missing = 2, critMissing = 2, update NEEDED
1970-01-01,00:00:53: DPM::packViable: logicalDiskBm = 0x1d criticalDiskBm = 0x0
1970-01-01,00:00:53: <<<< DPM::packViable: PACK IS NOT VIABLE
1970-01-01,00:00:53: ELM: Thu Jan 01 00:00:53 1970: DPM::doColdStart: NO LOADABLE DISK PACK FOUND
enableIoSc: state = 0, serial = 0x0
Interfaces enabled from the RTP … bringing up USB first …
USB interface enabled!
Interface ENABLED via syscall
1970-01-01,00:00:53: Load failure, clearing LEDs
1970-01-01,00:00:53: DISK PACK FAILED TO LOAD! USB IS UP BUT YOU CAN’T WRITE UNTIL PROBLEMS RECTIFIED!
UsbHandleResetInterrupt called
UsbHandleResetInterrupt called
interrupt: Time: THU JAN 01 00:00:54 1970
interrupt: UsbHandleResetInterrupt: INFO: Usb Bus Reset Received
interrupt: Usb DR: UsbDrCh9SetConfig: INFO: Setting Configuration: 1
Usb MS: INFO: MS State at Configure: 7
deinit ep #1-SEND: bit_pos=0x20000, EPCTRLX=0x0, SETUP=0x0, PRIME=0x0, STATUS=0x0, COMPL=0x0
UNSTALL_ENDPOINT: ep=1 SEND
deinit ep #1-RECV: bit_pos=0x2, EPCTRLX=0x880008, SETUP=0x0, PRIME=0x0, STATUS=0x0, COMPL=0x0
UNSTALL_ENDPOINT: ep=1 RECV
USB Connected …
Interface State Change called … interface: USB Down: 0, active: 65535
Ignoring USB interface DOWN state change when we are already down!
0x18c52f0 (UsbMSThread): Usb MS: ParseInterruptRequestEP0: INFO: Bulk Endpoint Initialized. CBW setup.
0x18c52f0 (UsbMSThread): UsbDrPrintCurrentPortSpeed: Running at USB HIGH Speed. Connected to USB 2.0

USB requesting to be the active interface

interfaceMakeActive called with int: USB, active_int = No Interface
Sending stack UP state up to the RTP.
takeDownOtherInterfaces:
Interface USB state is: ENABLED
…USB Interface state changed to ACTIVE
1970-01-01,00:00:54: USBHostRequest::rxCmd: USB Stack Connected
[/quote]

Now a driver of the Dashboard is crashing when I try to generate a diagnosic report. :frowning:

Any idea what I can do to get access to my data?

Thanks, Regards,
Chris

from that, phone support is the best bet (and get to tier 3 as quickly as possible i.e. past the “is it plugged in” type questions)[hr]
have you tried removing and reseating all the disks firmly?

failing that i guess the backplane/some other part of drobo may be failing

hopefuly all of your data would be safe if you plugged your disk pack into a differet drobo

thanks a lot for your response.
Unfortunately I am out of warranty, so support is not an option in my case…

I tried to remove and reseat all the drives. Unfortunately this didn’t help: it’s still all red.
Next, I removed all the drives and started a new diskpack by inserting a fresh 2tb disk. This, however was working fine.
I placed the disk in all of the slots - it worked.

Then, when I inserted the 4 disks of my first diskpack - still red.

It seems to me that the contents of two of the disks are corrupted.

[quote]Thu Mar 17 14:20:46 2011: DPM::packViable: ZM identifies missing disk LD #0 as CRITICAL
Thu Mar 17 14:20:46 2011: DPM::packViable: ZM identifies missing disk LD #3 as CRITICAL
Thu Mar 17 14:21:00 2011: DPM::packViable: numDisks = 4, missing = 2, critMissing = 2, update NEEDED[/quote]

However I can’t get any more logs from the drobo with the 4 disks in it. When I try to do so, the drobo crashes and so does the Dashboard (Drobo’s DDService64d kernel module crashes with a segmentation fault :o).

It seems as if it looks pretty bad for my data. :frowning:
I sent an enquiry to a data recovery service. Let’s see how much a restoration would cost.

im guesing you dont know anyone else with a drobo that you could try your disk pack in?

Please open a support ticket

Is that possible despite being out of warranty?
I have one of the very first drobos (no firewire, noisy fan), warranty is long gone and my support-account has already been deleted.