My remaining problem is that while the drive is fully functional in Big Sur, it will not be found by Drobo dashboard. I confirmed the app has Fun Disk Access, rebooted, uninstalled/reinstalled Drobo Dashboard and nothing changes this.
Where did you find the 3.5.2 dashboard update. when I check for updates via my dashboard it says there are none and that I have the latest version of 3.5.1 and when I check the Drobo website, I do not see it there either.
Understanding my problem was quite different than yours, it sounds like you followed my steps just to see if a clean uninstall, reinstall helps you? And it did not. It didn't cause any change in behavior other than the OS now recognizing that something is wrong with the drive. And maybe that's a good thing. Curious, when you uninstalled dashboard, did you use the disk image's Uninstall option? Hopefully so.
I have been working with drobo support since Tuesday evening without success. I have tried turning it on empty, with the drives I have and with brand new drives all with the same result. I have uninstalled the dashboard using the disk image and reinstalled the dashboard multiple times but only when I found your fix did it seem to even give a somewhat different result. I have run so many diagnostics for them as well. right now I am waiting to hear back from support again. I think at this point I am willing to take your other suggestion and start fresh with a new array. if that even works!
Just FYI I had to completely uninstall the existing dashboard first before installing the 3.5.2 update (using the uninstall function on the 3.5.2 dmg) - just installing over the top did not work for me originally.
Windows SMB can be enabled by going to your Windows Start Menu and search windows features then from the windows that open select smb/cifs box and smb direct this will restart your computer for the setting to take place and yout drobo should now appear within the drobo dashboard after the reboot
I have been able to get 2 drobos working now on my windows xp pc, (i had to upgrade the firmware on the new one, which is fair enough), and it worked a treat. managed to copy and paste all the content onto what will become offline / offsite backup ?
The upgrade to the 2.0 Software was a huge improvement over the 1.0 version. A better interface, easier to use features and a more intuitive layout is a big plus for the average guy. There is no reason not to move to this version of the Drobo Dashboard and if you are just purchasing a Drobo, the dashboard should be a tremendous help. Nice work Drobo!
Thanks for making me check the firewall! In my case the dashboard was added as a rule, but allowed only on public networks instead of the home networks. After checking the correct settings it connected to the drobo.
You can use Drobos without any special software. The blue capacity lights willfill up as the disks fill. When it gets too full, Drobo will ask for anotherdrive with its drive lights. Just feed it drives when it asks, and that is all.So what is the dashboard good for?
Drobo-utils is a set of linux tools to query and manage Data RoboticsDrobo storage systems. Fire up drobom view, and it should lookfamiliar to those who have seen the dashboard on other operating systems.Drobom view is built on a little python programmer interface which can be installedon the system and used by other applications as well. For experienced Linux hands,the rest of the command line interface is provided by other sub-commands ofdrobom, and offer the same functionality as the view graphical interface.
Drobo-utils accesses drobos via the same files. The softwarescans those files, and asking each device if it is a Drobo.Unfortunately, the way Drobos respond varies, so not all of them respondin a way that the software understands. Even for the samedevice, different physical interconnects may work with different functionality.There are two levels of access to Drobos: data (being able to read andwrite data, and full meaning that the drobo responds to the fullcommand and control language.
Drobo has made it so much easier to obtain much more secure storage, that some withlittle or no professional storage management experience are getting Drobos.Some have the expectation that Drobos, because they allow for disk failures,replace the need for backups. Sad stories have been told about people puttingdata only on the drobo, and no-where else, and then something happens and theylose the data.
That is the easiest installation method, this method ensures that any packagesrequired are automatically installed on the system as part of the aboveinstallation. On other distributions, or if the version in the repositories istoo old, more complicated methods might be needed. For all other installationmethods, one must ensure the packages that drobo-utils requires are installed.These packages are called Dependencies.
This gives a read-only copy of the source code that can be updated with the latestchanges with 'git pull'. One can also select any stable version of drobo-utils by use of'git branch -r', and 'git checkout'. For details, consult git documentation.
very scary, but my drobo is in bad shape right now... normal result is: []as a status, which means there is nothing wrong. To get all kinds ofinformation about the drobo, try 'drobom info.' Invocationwithout arguments at all which will cause it to print out a list of thecommands available through the command line interface.
as root starts a GUI for each drobo attached to a computer.There are various tabs to allow one to obtain information from the Drobo,and also change its configuration. For example, one can use the Formattab of the GUI to partition the device and create a single file systemfor a given LUN.
The above sets up the drobo as one big partition, with a label that saysit ought to contain an ext3[#mke3fs] file system. For an NTFS file system,write ntfs in place of ext3. The next step is to add the filesystem into the partition. while parted's are instantaneous, the mke2fstakes a while, just have a little patience, itll be fine.The coffee is hot disclaimer is necessary at this point:
By default, Drobo creates a separate 'disk' visible to the computer for every 2Terabytes (TiB) of parity-protected capacity on the unit. The natural usagethat a drobo invites in users is to have a single, large device covering all thedata on device. For example, on Mac OS/X, users often create 16 TB LUNS on HFS.This allows all the storage to fit on one large pool. The downside of largerLUNS has to do with startup time, and the time to perform a file system check.
If everything went well, your drobopro should show up under /dev. Also check /var/log/messages toconfirm that the iscsi device connected successfully. After that, drobo-utils should be ableto detect the Drobo and manage it over ethernet/iSCSI.
Those worried about safety of using this software should know: it wasdeveloped with assistance from the vendor (Data Robotics Inc.), andin every case, based on vendor documentation, and with at least encouragement,if not outright support. For each release, a QA.txt file is built, demonstrating the functionality tests run. There are multiple checksum verifications builtinto the firmware upgrade process, so it is next to impossible to brick a drobousing the tools. Drobo-utils verifies firmware checksums before attemptingto upload the image to the device, and the device checks the firmware againstthe checksums as well. New firmware is loaded into an alternate locationfrom the currently active one, and if activation of the new firmware fails,the drobo will simply boot the old one.
A rational means of configuring the Drobo is as a backup repository.The drobo is destination of the backups. Primary copies are on thedesktops & laptops being backed up. Viewed in that way, backup datais easily recovered in the event of a data loss: just backup the systemagain. Of course the history of backups is lost, but the importantthing is usually being able to recover current data.
To find Drobo on a system, drobo-utils queries all the attached devices for indicationsit is made by Data Robotics. These strings change from product to product.If the (new model) Drobo is not detected, then run the command line interfacewith the hardware detection debugging output turned out. like so:
There is still a great role for Drobo space, in that Tier 3 support analysts(essentially developers.) sometimes look over there. For tier 3 support, onecannot expect guaranteed response time, but one may be able to provide someinput into future products or firmware features. It turns out that theDrobospace forums aren't really for support. but don't take my word for it,here is above was DRI's take (verbatim from a post ondrobospace by MarkF 2008/08/29) on things:
Drobospace.com is a user community and relies on the volunteer efforts of its members to help each other. Because it is run by volunteers response to problems varies. Tier 3 support personel monitor the Drobospace forums -- tiers 1 and 2 are focused directly on customers, and they are not required to read drobospace.com. By design Tier 3 personnel do not immediately respond to each posting in order to allow the community to function. Depending on the nature of the problem, tier 3 may post in the forum or contact the member directly through a private message to facilitate problem resolution.
Droboshare is not directly supported by drobo utils running on a linux host.However, the droboshare itself is a linux host, and it is possible to rundrobo-utils un-modified on the droboshare itself. There is download calledthe Droboshare Augmented Root File system (DARFS), which includes a pythoninterpreter and drobo-utils.
Why isn't there full support in host based drobo-utils itself? DigitalRobotics hasn't released details of the protocol used by the proprietarydashboard to communicate with a droboshare, so it would be a lot of work toreverse engineer that. So support of a droboshare from a linux GUI on ahost system is not likely in the near future.
df19127ead