Drobo freezes 10.7 Lion Server

Oi "enough Said" clown, maybe you should read past what you want and read the release notes for 2.0.4 it clearly states all devices spoken about. I have pointed this out to you before in this thread so I suggest this time YOU re-read the release notes.

Custa, there is no need to insult people, even if you don't agree.

Whatever is in the release notes, what counts is that 2.0.4 has not officially been released for the Drobo S. Or do you see it somewhere on the download page? I followed your advise to re-read, but I wasn't able to find the 2.0.4 code for the Drobo S on the download page.

Also, as I have stated more than once, people (including you) need to realize that the 2.0.4 code does NOT include a single fix for any problems related to Firewire, USB or eSATA. The sole purpose of the 2.0.4 release is to fix iSCSI issues. iSCSI is not even available on the Drobo S.

If you do not understand this crucial piece of information or keep ignoring the facts, you can't be helped. You can keep trying to solve iSCSI problems on your Drobo S. Good luck with that.

I've atually never said one way or the other if anything has been fixed for my Drobo by 2.0.4, feel free to go back and read to satisfy your incorrect claim. Mate "clown" is the most polite thing that i could put in a sentence to discuss your carrying on, considering how you are behaving towards people. How about, if you have an iSCSI model and YOUR problem is sorted by 2.0.4 you should move on and leave this discussion, you truely are adding nothing to the conversation now apart from incorrect snippets of information to to drive home your argument, its getting boring now seing your posts.

And what exactly have you been contributing to this thread, Custa? And how exactly are my claims incorrect? Do you have any better technical information on the issues?

Another data point:

MacPro5,1

Drobo S with factory drives connected via FW800

Dashboard 2.0.3.40648

Latest official firmware

Drobo S extremely slow (like, 6 MB/s) then always gets stuck when attempting a large transfer.

So I agree with cryptochrome, looks like Drobo S owners can't use with OS X 10.7.2 until new FW is available.

And before I upgraded to Lion, I checked the Drobo site and relied upon the assurances and followed the instructions found here: http://support.drobo.com/app/answers/detail/a_id/602/~/upgrading-to-mac-os-x-lio n-(os-x-10.7)-faq

So, I find this whole episode to be quite disappointing.

As someone mentioned earlier, the firewire problems don't seem to be specific to the Drobo, with people reporting similar problems with a number of devices, see here:

https://discussions.apple.com/thread/3199793?start=15&tstart=0

Of course, this does not excuse the fact that Drobo have failed to anknowledge there is an issue or to give a warning about it on their site (and the same applies to Apple, too).

Poor show, and I hope someone comes up with a fix soon.

As a matter of interest, has anyone tried with 10.7.2? I've not, but I guess there could be a fix in there somewhere.

I am on Lion Server 10.7.2 with a Drobo 2nd-gen on Mac Mini connected with FW-800. I am still encountering this issue. There's no fix in 10.7.2 unfortunately.

I just connected it via USB instead. I hope this resolves it.

My Drobo S became stable under Lion once I switched from FW800 to USB2. Stable but, of course, slow.

Same problem here with Drobo S

They sent me a replacement

Jesus, That didnt help

Same problem exists with large file trasnfers.

It was working fine since i got this new Mac mini.

Gasp!

My company has been an Apple Developer since the Lisa and we have many current- and recent-generation Mac Pros and many storage devices, including Drobos. I have personally invested quite a bit of time investigating the current situatuion and my determination is that if you have a Drobo S running current firmware (and Dashboard) and you want to connect it to a Mac running OS X 10.7.2, the only safe method for the time being is via USB2.

It will be slower, of course. Here I am getting 25 Mb/s based on a simple test:

$ time dd if=/dev/zero of=/Volumes/Drobo/tmp/tmp bs=1024k count=10240

10240+0 records in

10240+0 records out

10737418240 bytes transferred in 429.457878 secs (25002262 bytes/sec)

real 7m10.220s

user 0m0.016s

sys 0m9.780s

$ time dd if=/dev/zero of=/Volumes/Drobo/tmp/tmp bs=1024k count=16384

16384+0 records in

16384+0 records out

17179869184 bytes transferred in 684.973620 secs (25081067 bytes/sec)

real 11m25.485s

user 0m0.025s

sys 0m15.698s

25081067 bytes/sec

x

8 (bytes to bits)

-----

200648536

divided by 1024 twice from bits to Mbits

-----

191.353355407715 Mb/sec

from your simple test results

Alternatively

25081067 bytes/sec

divided by 1024 twice from Bytes to MBytes

-----

23.9191694259644 MB/sec

For reference from the wiki:

USB 2.0:maximum bandwidth of 480 Mbit/s (60 MB/s)

Correction (with my thanks to ellisonjay):

"Here I am getting 25 Mb/s based on a simple test:" should have read "Here I am getting 25 MB/s based on a simple test:"

Oops.

Bruce