I’ve had a Drobo S for about 8 months and been almost pleased with it, my main dislikes being the slow performance, and lack of control or reporting with regards to the disk scrubbing. But another issue is that it won’t put the drives to sleep when connected via eSATA (though it does over USB).
I saw in the Knowledge-base that the drive-sleep issue is known and that it would be fixed in an upcoming firmware update, but the article was written 18 months ago, and firmware has been updated at least once since then (and a recent firmware for the FS specifically said that it fixed the issue for that model). The last officially released firmware for the S (v2.0.1 from earlier this year) didn’t even have this issue listed in its known issues sections of the release notes. So I opened a support ticket asking if the bug had been forgotten about.
I received a reply after 2 business days (which was OK response time since it was a non-emergency) with a link to the v2.0.3 firmware. However, after going through the minor hassle of installing it I found out that the bug exists in that version as well.
So, why was I sent that firmware? Why make a customer take steps to fix a problem only to find out that it’s not a fix at all? Shouldn’t CS already know that v2.0.3 doesn’t fix the issue? I now feel much less confident in DR’s QC and internal reporting than if they had just replied with “we’re still working on the issue”. Then again, the bug has been there for over a year and a half. I’m very disappointed either way.
Fortunately, competition has almost caught up in some features, and dramatically surpassed in other features (such as being able to do manual disk scrubs/consistency checks (which should always be done before doing any optional drive replacement)). And even more fortunate, resale value of Drobos is still strong.