I can't see my Raid (Drobo) on my desktop with OSX Mavericks

Getting the same problem with a 2nd Gen Drobo on a late 2008 MBP that was just upgraded to Mavericks, a brand new 1 day old Macbook Air (just upgraded to Mavericks).

Will test it out on a 5 day old MBP on Mountain Lion to see if its just the OS.

My Drobo shows up on disk utility but refuses to mount. Drobo desktop can see the Drobo.

You might want to do a Search Communities (upper right) for drobo. There have been several discussions of it with respect to Mavericks.

Phil

I've tried pretty much every option shown in the communities and the options found doing google searches which includes using the terminal, mounting using disk utilities and powering off the machine.

What I've noticed is that my Drobo will eventually show up on my desktop, but I can no longer write to it.

The data is there but it does not mount like it used to before Mavericks was installed.

I upgraded to 10.9.1

Update, I tried the Drobo on my late 2008 MBP, a brand new Macbook Air 13 inch, a brand new 13 inch Macbook Pro.

Worst case is the Drobo won't mount in finder but it can be seen by disk utilities. Best case it mounts, can be seen on the desktop finder, but cannot be written. It can only be read.

This is frustrating.

I am having same problem after upgraded to 10.9.1.

Mac mini (2012) with 2nd gen Drobo, FW800 cable.

Can't mount it, Can't repair it with DiskUtility.

I just shut it off drobo now... What should I do..?

Update:

I've tried another utility based on suggestions on the web: Cocktales for Mac OSX Mavericks. The app did not work and could not even see the Drobo.

I will copy all data and reset the Drobo as a last ditch resort if 10.9.2 does not fix this.

Apple, please coordinate with Drobo! I asked the same of Drobo. I've got three new Macs that can't read my external (Drobo) hard drive! I've purchased more Macs than Drobos and it frustrates me that an OS upgrade killed the connection.

The net seems to suggest this may have something to do with the Mavericks firewire issue, so I'll try to be a bit more patient. If a firewire fix is released and my Drobo is still not writable I'll do the backup and format route.

I hope Apple is able to fix this soon.

I find it an unreasonable solution that I would have to spend another $1000+ US dollars for tera hard drives to copy my 12 tera worth of data, then just format my Drobo which I've already spent $1,500 worth in array and drives just because a free OS killed the connection on new Macs worth $4,000 dollars.

Hopefully Apple fixes this in 10.9.2 or sends me a new RAID system LOL.

FWIW, I've managed to corrupt 3 different Drobo arrays by connecting them to a machine with 10.9.1...

Drobo gen.2 via firewire

Drobo Pro via iSCSI (and then via USB2 when iSCSI connectivity unexpicably failed - drobo RMA in process)

Drobo 5D via Thunderbolt (and via USB2)

Yes, I've been foolish enough to buy three Drobos over the years... I admit it.

My point, I don't think it's particular to any specific hardware transport layer... whatever the problem is, it's more general and wide-spread.

I've tried connecting these arrays back to a 2011 MBP running 10.8.5, and they're still completely flakey now. Drive Genius 3.2 says it's repaired the file system, but the drives mount and soon become inaccessible. Finder just spins until I navigate to another volume. Try too many things and the whole system locks up, presumably waiting for filesystem I/O from the array which never occurs.

Currently, my Drobo gen.2 is connected via firewire and appears mounted, but is non-functional and non-responsive. The array has even spun-down the disks and fan. Lights are green, but nobody's home.

Something is seriously wrong.

My primary array (5D), and two backups (Pro and gen.2) are all totally screwed now. over 50 TB of storage unusable from any computer.

Apple, Drobo... hello?

Just an update February 26, 2014

I've updated my laptops and desktops (about 5 Mac, two were spanking brand new when they released mavericks) and my Drobo still does not work.

APPLE YOU SCREWED UP MY BACK-UP DRIVE. I BOUGHT VERY EXPENSIVE LAPTOPS AND DESKTOPS AND I NOW HAVE TO SPEND THOUSANDS MORE CAUSE YOU MESSED UP A PERFECTLY FINE WORKING SYSTEM.

My disk utility can't repair my Drobo. Now I'll have to follow what the previous poster said, I'm going to have to buy thousands of dollrs worth of drives to back-up my Drobo, format my Drobo and copy things back.

BOOOO APPLLEE YOU SCREWED A VERY LOYAL FAN THATS BOUGHT A LOT FROM YOU!!!!!

I had a issue with my Drobo Pro on 10.9.2 not mounting, but in the Dashboard it showed it had the correct data size on the Capacity tab, but would not show amount used on the Volumes Tab.

Would not mount using DIsk Utlities, and gave me the Red errors when I ran DIsk Repair telling me to back up the data off of it

I ended up buying DiskWarror for about $110 bucks and it fixed it about 5 minutes...

Als I plugged in via firewire from iSCSI, to fix and then back to iSCSI

Apple doesn’t routinely monitor the discussions.

Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.

Feedback

found this

With the help of Drobo's technical support who pointed me to this MacRumors thread, I've resolved the issue. It turned out that somehow my drive got set to "invisible", which is a filesystem attribute. I don't think this setting is settable via the Finder, so I'm not sure how it got set like that.

To confirm the issue, I had to install Xcode and then install the command line tools, then run this Terminal command:

GetFileInfo /Volumes/Drobo/

where

/Volumes/Drobo/

V

To fix it:

SetFile -a v /Volumes/Drobo/

with a lowercase v, to remove the invisible attribute.

After a reboot, everything was back to normal.

Note: depending on the drive and your permissions, it's possible you will need to run these commands with

sudo

shareimprove this answer

answered Jan 20 '13 at 19:24 http://apple.stackexchange.com/users/661/henry-jackson Henry Jackson 18817

With the help of Drobo's technical support who pointed me to this MacRumors thread, I've resolved the issue. It turned out that somehow my drive got set to "invisible", which is a filesystem attribute. I don't think this setting is settable via the Finder, so I'm not sure how it got set like that.

To confirm the issue, I had to install Xcode and then install the command line tools, then run this Terminal command:

GetFileInfo /Volumes/Drobo/

where

/Volumes/Drobo/

V

To fix it:

SetFile -a v /Volumes/Drobo/

with a lowercase v, to remove the invisible attribute.

After a reboot, everything was back to normal.

Note: depending on the drive and your permissions, it's possible you will need to run these commands with

sudo

shareimprove this answer

answered Jan 20 '13 at 19:24 http://apple.stackexchange.com/users/661/henry-jackson Henry Jackson 18817