Drobo

Drobo can see data but not read it after accidentally encrypting Time Machine backup

Hi everyone,

A few months back, as I was exploring the settings of my Time Machine backups, I accidentally opted to encrypt the backup, which was stored on my Drobo drive. Realizing what I had done, I somehow aborted it before the encryption was complete. My Drobo dismounted and reappeared. But then at some point, it disappeared again. Now, I can’t get the drive to mount (or read the data on it). My Drobo Dashboard shows that the data is there (3.30 TB of it!), but as it can’t now mount, I can’t get to it. Please help!

My best guess from browsing forums is that my MBR could now be corrupt. But if so, why is Drobo Dashboard able to tell me how much data is stored on the drive? And how do I get the MBR back?

I’m running OS X (10.8.5)
I have a Drobo with firmware 1.4.2 [1.254.50341

I’ve tried using Disk Utility to repair the disk, but get the following errors:

Verifying and repairing partition map for “Drobo”
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loaders
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk4s2: Scan for Volume Headers
Invalid Volume Header @ 8795749047808: unsupported format
disk4s2: Scan for Disk Labels
Invalid Disk Label @ 8795732267008: cksum mismatch
Invalid Disk Label @ 8795736461312: cksum mismatch
Invalid Disk Label @ 8795740655616: cksum mismatch
Invalid Disk Label @ 8795744849920: cksum mismatch
disk4s2 is not a CoreStorage volume
Checking storage system
Checking volume.
disk4s2: Scan for Volume Headers
Invalid Volume Header @ 8795749047808: unsupported format
disk4s2: Scan for Disk Labels
Invalid Disk Label @ 8795732267008: cksum mismatch
Invalid Disk Label @ 8795736461312: cksum mismatch
Invalid Disk Label @ 8795740655616: cksum mismatch
Invalid Disk Label @ 8795744849920: cksum mismatch
disk4s2 is not a CoreStorage volume
Checking storage system
Checking volume.
disk4s2: Scan for Volume Headers
Invalid Volume Header @ 8795749047808: unsupported format
disk0s2: Scan for Volume Headers
disk4s2: Scan for Disk Labels
Invalid Disk Label @ 8795732267008: cksum mismatch
Invalid Disk Label @ 8795736461312: cksum mismatch
Invalid Disk Label @ 8795740655616: cksum mismatch
Invalid Disk Label @ 8795744849920: cksum mismatch
disk0s2: Scan for Disk Labels
Logical Volume Group 1CB4217B-6FCB-4C98-B8E3-CFA37B511D0D on 1 device
Incomplete or inconsistent CoreStorage Physical Volume set
Problems were encountered during repair of the partition map
Error: This disk needs to be repaired. Click Repair Disk.

Then if I re-run, it gives the same report.

I realize I may have left out key info. Please let me know if anything else would be helpful. If anyone knows how to solve this, you would be my hero!

Thanks in advance!
Eric

hi eric,
usually i try to offer some ideas like others, and then to also mention opening tickets etc, but i really do think the best thing would be to contact support (before trying anything else, including more disk repair operations etc)

this is because there has been a known problem if encryption is used in a certain way like whole drive and if there is a way to fix things, there may be particular steps that support might need you to carry out, in a specific order.

(even if you are out of support, there should still be some paid options available for you)

the only other thing i can think of at the moment, (which does have a cost also potentially associated with it) would be to try block cloning all the drives onto matching spares if you have them, and then trying diskwarrior, but, that would mean powering off and it could be that support needs diagnostic logs before the power off so i would try raising a ticket to check first though to be honest.