Drobo

bogus 0-byte Vol created, real volume unmountable

My Mac mini Server restarted for some reason (perhaps a brief power outage) and now my DroboPro is presenting itself as TWO separate hardware devices.

The Dashboard still only shows the one volume I had created, and it still reports that all is well–EXCEPT that it has renamed the volume to ‘Drobo’ from what I had named it, and attempts at renaming the volume using Dashboard all fail.

The first of the two hardware devices is reported by Disk Utility and System Profiler as being an unpartitiioned 0-byte device which is, of course, unmountable.

The second device is reported by Disk Utility as my DroboPro with my original, correctly-sized, correctly-named volume, but it is unmounted, unmountable, and Disk Utility cannot repair it. I haven’t located my DiskWarrior CD yet to try that, but this seems like a much more significant issue.

The report from System Profiler is at the end of this message. Any ideas?

    DroboPro:

      Manufacturer: Drobo
      Model: 0x1
      GUID: 0x1A620293040844
      Maximum Speed: Up to 800 Mb/sec
      Connection Speed: Up to 800 Mb/sec
      Sub-units:
        DroboPro Unit:
          Unit Software Version: 0x10483
          Unit Spec ID: 0x609E
          Firmware Revision: 0x10000
          Product Revision Level: 1.00
          Sub-units:

DroboPro SBP-LUN:
Removable Media: Yes
BSD Name: disk2
Partition Map Type: Unknown
S.M.A.R.T. status: Not Supported
DroboPro SBP-LUN:
Capacity: 17.59 TB (17,592,186,044,416 bytes)
Removable Media: Yes
BSD Name: disk3
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
Capacity: 209.7 MB (209,715,200 bytes)
Writable: Yes
BSD Name: disk3s1
Waterschap:
Capacity: 17.59 TB (17,591,842,070,528 bytes)
Writable: Yes
File System: Journaled HFS+
BSD Name: disk3s2

What happens if you go to the “Go” menu in Finder and do “Go to Folder” and put /Volumes.

Sometimes the Mac will mount a phantom volume if there is a crash.

I had this problem happen to me and that is what the problem was.

My volume would mount with a 1 after it and cause all sorts of issues.

I deleted the false mount point in the /volumes folder and rebooted. All was well in the world.