File: README.html

package info (click to toggle)
drobo-utils 0.6.1%2Brepack-2
links: PTS, VCS
area: main
in suites: buster, stretch
size: 1,000 kB
ctags: 172
sloc: python: 1,705; sh: 229; makefile: 65
file content (839 lines) | stat: -rw-r--r-- 33,734 bytes
parent folder | download | duplicates (2)
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" />
<title>Drobo Utils README</title>
<style type="text/css">

/*
:Author: David Goodger (goodger@python.org)
:Id: $Id: html4css1.css 5196 2007-06-03 20:25:28Z wiemann $
:Copyright: This stylesheet has been placed in the public domain.

Default cascading style sheet for the HTML output of Docutils.

See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
customize this style sheet.
*/

/* used to remove borders from tables and images */
.borderless, table.borderless td, table.borderless th {
  border: 0 }

table.borderless td, table.borderless th {
  /* Override padding for "table.docutils td" with "! important".
     The right padding separates the table cells. */
  padding: 0 0.5em 0 0 ! important }

.first {
  /* Override more specific margin styles with "! important". */
  margin-top: 0 ! important }

.last, .with-subtitle {
  margin-bottom: 0 ! important }

.hidden {
  display: none }

a.toc-backref {
  text-decoration: none ;
  color: black }

blockquote.epigraph {
  margin: 2em 5em ; }

dl.docutils dd {
  margin-bottom: 0.5em }

/* Uncomment (and remove this text!) to get bold-faced definition list terms
dl.docutils dt {
  font-weight: bold }
*/

div.abstract {
  margin: 2em 5em }

div.abstract p.topic-title {
  font-weight: bold ;
  text-align: center }

div.admonition, div.attention, div.caution, div.danger, div.error,
div.hint, div.important, div.note, div.tip, div.warning {
  margin: 2em ;
  border: medium outset ;
  padding: 1em }

div.admonition p.admonition-title, div.hint p.admonition-title,
div.important p.admonition-title, div.note p.admonition-title,
div.tip p.admonition-title {
  font-weight: bold ;
  font-family: sans-serif }

div.attention p.admonition-title, div.caution p.admonition-title,
div.danger p.admonition-title, div.error p.admonition-title,
div.warning p.admonition-title {
  color: red ;
  font-weight: bold ;
  font-family: sans-serif }

/* Uncomment (and remove this text!) to get reduced vertical space in
   compound paragraphs.
div.compound .compound-first, div.compound .compound-middle {
  margin-bottom: 0.5em }

div.compound .compound-last, div.compound .compound-middle {
  margin-top: 0.5em }
*/

div.dedication {
  margin: 2em 5em ;
  text-align: center ;
  font-style: italic }

div.dedication p.topic-title {
  font-weight: bold ;
  font-style: normal }

div.figure {
  margin-left: 2em ;
  margin-right: 2em }

div.footer, div.header {
  clear: both;
  font-size: smaller }

div.line-block {
  display: block ;
  margin-top: 1em ;
  margin-bottom: 1em }

div.line-block div.line-block {
  margin-top: 0 ;
  margin-bottom: 0 ;
  margin-left: 1.5em }

div.sidebar {
  margin: 0 0 0.5em 1em ;
  border: medium outset ;
  padding: 1em ;
  background-color: #ffffee ;
  width: 40% ;
  float: right ;
  clear: right }

div.sidebar p.rubric {
  font-family: sans-serif ;
  font-size: medium }

div.system-messages {
  margin: 5em }

div.system-messages h1 {
  color: red }

div.system-message {
  border: medium outset ;
  padding: 1em }

div.system-message p.system-message-title {
  color: red ;
  font-weight: bold }

div.topic {
  margin: 2em }

h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
  margin-top: 0.4em }

h1.title {
  text-align: center }

h2.subtitle {
  text-align: center }

hr.docutils {
  width: 75% }

img.align-left {
  clear: left }

img.align-right {
  clear: right }

ol.simple, ul.simple {
  margin-bottom: 1em }

ol.arabic {
  list-style: decimal }

ol.loweralpha {
  list-style: lower-alpha }

ol.upperalpha {
  list-style: upper-alpha }

ol.lowerroman {
  list-style: lower-roman }

ol.upperroman {
  list-style: upper-roman }

p.attribution {
  text-align: right ;
  margin-left: 50% }

p.caption {
  font-style: italic }

p.credits {
  font-style: italic ;
  font-size: smaller }

p.label {
  white-space: nowrap }

p.rubric {
  font-weight: bold ;
  font-size: larger ;
  color: maroon ;
  text-align: center }

p.sidebar-title {
  font-family: sans-serif ;
  font-weight: bold ;
  font-size: larger }

p.sidebar-subtitle {
  font-family: sans-serif ;
  font-weight: bold }

p.topic-title {
  font-weight: bold }

pre.address {
  margin-bottom: 0 ;
  margin-top: 0 ;
  font-family: serif ;
  font-size: 100% }

pre.literal-block, pre.doctest-block {
  margin-left: 2em ;
  margin-right: 2em }

span.classifier {
  font-family: sans-serif ;
  font-style: oblique }

span.classifier-delimiter {
  font-family: sans-serif ;
  font-weight: bold }

span.interpreted {
  font-family: sans-serif }

span.option {
  white-space: nowrap }

span.pre {
  white-space: pre }

span.problematic {
  color: red }

span.section-subtitle {
  /* font-size relative to parent (h1..h6 element) */
  font-size: 80% }

table.citation {
  border-left: solid 1px gray;
  margin-left: 1px }

table.docinfo {
  margin: 2em 4em }

table.docutils {
  margin-top: 0.5em ;
  margin-bottom: 0.5em }

table.footnote {
  border-left: solid 1px black;
  margin-left: 1px }

table.docutils td, table.docutils th,
table.docinfo td, table.docinfo th {
  padding-left: 0.5em ;
  padding-right: 0.5em ;
  vertical-align: top }

table.docutils th.field-name, table.docinfo th.docinfo-name {
  font-weight: bold ;
  text-align: left ;
  white-space: nowrap ;
  padding-left: 0 }

h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
  font-size: 100% }

ul.auto-toc {
  list-style-type: none }

</style>
</head>
<body>
<div class="document" id="drobo-utils-readme">
<h1 class="title">Drobo Utils README</h1>

<p>Drobo-utils is a set of linux tools to query and manage Data Robotics
Drobo storage systems.  If you fire up droboview, it should look pretty
familiar to those who have seen the dashboard on other operating systems.
Droboview is built on a little programmer interface which can be installed
on the system and used by other applications as well.</p>
<p>For experienced Linux hands, there is a command line interface, drobom,
which offers the same functionality as droboview.   For real hackers, fire
up a python interpreter, 'import Drobo', help(Drobo), and you are off to
the races...  Command-line access is also bundled into a set of improvements
to a standards droboshare called 'Droboshare Augmented Root File System' (DARFS)</p>
<div class="contents topic" id="contents">
<p class="topic-title first">Contents</p>
<ul class="simple">
<li><a class="reference internal" href="#installation" id="id1">INSTALLATION</a><ul>
<li><a class="reference internal" href="#requirements" id="id2">REQUIREMENTS</a></li>
<li><a class="reference internal" href="#installing-pre-requisites" id="id3">INSTALLING pre-requisites</a></li>
<li><a class="reference internal" href="#install-from-package" id="id4">Install From Package</a></li>
<li><a class="reference internal" href="#install-from-source" id="id5">Install from Source</a></li>
<li><a class="reference internal" href="#try-out-the-cli" id="id6">Try Out the CLI</a></li>
<li><a class="reference internal" href="#try-out-the-gui" id="id7">Try Out the GUI</a></li>
<li><a class="reference internal" href="#try-out-the-python-api" id="id8">Try Out the Python API</a></li>
<li><a class="reference internal" href="#building-debian-ubuntu-packages" id="id9">Building debian &amp; ubuntu packages</a></li>
</ul>
</li>
<li><a class="reference internal" href="#setup-drobo-with-linux" id="id10">Setup Drobo with Linux</a><ul>
<li><a class="reference internal" href="#getting-source" id="id11">Getting Source</a></li>
<li><a class="reference internal" href="#multiple-luns" id="id12">Multiple LUNS</a></li>
<li><a class="reference internal" href="#drobo-pro" id="id13">Drobo Pro</a></li>
</ul>
</li>
<li><a class="reference internal" href="#drobo-firmware" id="id14">Drobo Firmware</a><ul>
<li><a class="reference internal" href="#safety" id="id15">SAFETY</a></li>
<li><a class="reference internal" href="#compatibility" id="id16">Compatibility</a></li>
</ul>
</li>
<li><a class="reference internal" href="#known-bugs" id="id17">KNOWN BUGS</a></li>
<li><a class="reference internal" href="#droboshare-support" id="id18">Droboshare Support</a><ul>
<li><a class="reference internal" href="#darfs" id="id19">DARFS</a></li>
<li><a class="reference internal" href="#darfs-installation" id="id20">DARFS Installation</a></li>
<li><a class="reference internal" href="#enable-sftp-support" id="id21">Enable SFTP Support</a></li>
<li><a class="reference internal" href="#building-droboshare-applications" id="id22">Building Droboshare applications</a></li>
<li><a class="reference internal" href="#droboshare-firmware" id="id23">Droboshare Firmware</a></li>
</ul>
</li>
<li><a class="reference internal" href="#credits" id="id24">Credits</a></li>
<li><a class="reference internal" href="#administrivia" id="id25">Administrivia</a></li>
</ul>
</div>
<div class="section" id="installation">
<h1><a class="toc-backref" href="#id1">INSTALLATION</a></h1>
<p>Drobo utils installation.</p>
<div class="section" id="requirements">
<h2><a class="toc-backref" href="#id2">REQUIREMENTS</a></h2>
<p>Drobo-utils was developed on pre-release version of Kubuntu (Hardy, Intrepid,
and now Jaunty) Any similarly recent distro ought to do.</p>
<p>To get drobo-utils running, you need packages something like (these are
ubuntu packages, names may vary on other distros):</p>
<dl class="docutils">
<dt>essential::</dt>
<dd><p class="first">python      -- interpreter for python language
parted      -- partitioner, usually included with the distro.</p>
<dl class="last docutils">
<dt>if using RHEL, which has python 2.4...</dt>
<dd>python-ctypes -- module for C-interface</dd>
</dl>
</dd>
<dt>for the GUI:</dt>
<dd>python-qt4  -- the python bindings for version 4 of the QT toolkit</dd>
</dl>
<p>To get a complete list, it is best to use a shell window to grep in the
Debian package control file (which defines what the dependencies are for the
build system):</p>
<pre class="literal-block">
peter&#64;pepino% grep Depend debian/control
Build-Depends: debhelper (&gt;= 5), python2.5-dev, python-docutils
Depends: ${shlibs:Depends}, ${misc:Depends}, parted
peter&#64;pepino%
</pre>
</div>
<div class="section" id="installing-pre-requisites">
<h2><a class="toc-backref" href="#id3">INSTALLING pre-requisites</a></h2>
<p>On ubuntu, it would typically look like so: Open a shell window. Enter the following package installation commands:</p>
<pre class="literal-block">
% sudo aptitude install python-qt4 parted
% sudo aptitude install debhelper python2.5-dev
% sudo aptitude install python-docutils
</pre>
<p>If you have received a pre-built binary package,then you only need the
first line.  If you want to build from source, then you need the second line.
The third line install what you need to build documentation.</p>
<p>On redhat/fedora distros, it would more likely be 'yum' instead of 'aptitude'
and some of the package names will change.  A typical difference is that
packages for developers have the -devel suffix on Redhat derived
distributions, instead of the -dev favoured by debian derived ones.</p>
<p>here is an example from fedora 7 (courtesy of help4death on the google group):</p>
<pre class="literal-block">
% yum install python
% yum install PyQt4
% yum install python-devel
</pre>
<p>NOTE: if X or QT is missing, it will only disable the GUI.  Line mode will work without issues.  the package should work fine on headless servers using only the command line.</p>
</div>
<div class="section" id="install-from-package">
<h2><a class="toc-backref" href="#id4">Install From Package</a></h2>
<p>Point your browser at: <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=222830">http://sourceforge.net/project/showfiles.php?group_id=222830</a>
where current packages are available.  after downloading a .deb, it is simply a matter of:</p>
<blockquote>
dpkg -i drobo-utils-&lt;version&gt;.deb</blockquote>
<p>done!</p>
</div>
<div class="section" id="install-from-source">
<h2><a class="toc-backref" href="#id5">Install from Source</a></h2>
<p>See DEVELOPER.txt</p>
</div>
<div class="section" id="try-out-the-cli">
<h2><a class="toc-backref" href="#id6">Try Out the CLI</a></h2>
<p>Assuming you have all of the above parts, in the directory where you
downloaded the source, you should be able to invoke the command line
interface as follows:</p>
<pre class="literal-block">
drobom status
</pre>
<p>see if something sensible happens... on my system with a drobo
the following happens:</p>
<pre class="literal-block">
% sudo drobom status
/dev/sdz /drobo01 100% full ( ['Red alert', 'Bad disk', 'No redundancy'], 0 )
%
</pre>
<p>Note: drive changed to sdz to avoid copy/paste errors.</p>
<p>very scary, but my drobo is in bad shape right now... you should just get []
as a status, which means there is nothing wrong.   To get all kinds of
information on your drobo, try 'drobom info.'  You can then invoke it
with no arguments at all which will cause it to print out a list of the
commands available through the command line interface.</p>
</div>
<div class="section" id="try-out-the-gui">
<h2><a class="toc-backref" href="#id7">Try Out the GUI</a></h2>
<p>Once the command line stuff that is working, and assuming you have python-qt4
installed, try:</p>
<pre class="literal-block">
% droboview
</pre>
<p>which should start a GUI for each drobo attached to your machine, that
you have permission to access (depends on the setup, usually USB devices
on desktops are accessible to users, so you can see them.</p>
</div>
<div class="section" id="try-out-the-python-api">
<h2><a class="toc-backref" href="#id8">Try Out the Python API</a></h2>
<blockquote>
See DEVELOPERS.txt</blockquote>
</div>
<div class="section" id="building-debian-ubuntu-packages">
<h2><a class="toc-backref" href="#id9">Building debian &amp; ubuntu packages</a></h2>
<blockquote>
See DEVELOPERS.txt</blockquote>
</div>
</div>
<div class="section" id="setup-drobo-with-linux">
<h1><a class="toc-backref" href="#id10">Setup Drobo with Linux</a></h1>
<p>One can use the Format tab of the GUI to partition the device
and create a single file system for a given LUN.</p>
<p>NOTE:  mke2fs takes a very long time to run, on the order of ten minutes
per Terabyte. the display format button just turns red while the format
is in progress,and you have to wait until it finishes.  Have not
determined a method to monitor progress yet.  other file systems are
much more quickly created, so less of an issue.</p>
<p>I actually prefer to use the system tools manually, as described below:</p>
<p>Drobos with firmware 1.1.1 or later work well under linux with ext3.
You can, of course set up an NTFS or HPS+ or FAT32 if you really want,
but it seems actively counter-intuitive on Linux.  Have not tested
HPS, but ntfs-3g worked fine initially.  However, unless you are
going to physically move the disk to between systems, the native (ext3)
format has many advantages.  The ´coffee is hot´ disclaimer is
necessary at this point:</p>
<pre class="literal-block">
WARNING: THE FOLLOWING 4 LINES WILL ERASE ALL DATA ON YOUR DROBO!
WARNING: NO, IT WILL NOT ASK ANY QUESTIONS!
WARNING: ASK YOURSELF, before you start: ARE YOU SURE?
WARNING: AFTER THE SECOND LINE, YOU ARE TOAST.
WARNING: BEST TO BACKUP YOUR DATA BEFOREHAND...
</pre>
<p>If you didn't use the GUI, Here is what you have to type:</p>
<pre class="literal-block">
# drobom -d /dev/sdz format ext3 PleaseEraseMyData
You asked nicely, so I will format ext3 as you requested
if you are really sure, go ahead and do: sh /tmp/fmtscript

# cat /tmp/fmtscript
#!/bin/sh
parted /dev/sdz mklabel gpt
parted /dev/sdz mkpart ext2 0 100%
parted /dev/sdz print; sleep 5
mke2fs -j -i 262144 -L Drobo01 -m 0 -O sparse_super,^resize_inode /dev/sdz1
</pre>
<p>The above sets up the drobo as one big partition, with a label that says
it ought to contain an ext2 file system.  If you want an NTFS file system,
then write ´ntfs´ in place of ext2.  The next step is to add the file
system into the partition.  while parted's are instantaneous, the mke2fs
takes a while, just have a little patience, it´ll be fine.</p>
<blockquote>
sh -x /tmp/fmtscript</blockquote>
<p>(If you want an ntfs file system, then mkntfs -f -L Drobo01 /dev/sdz1
ought to work too... )</p>
<p>On my system the process looked like this:</p>
<pre class="literal-block">
root&#64;alu:~# parted -i /dev/sdz
GNU Parted 1.7.1
Using /dev/sdz
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel gpt
(parted) mkpart ext2 0 100%
(parted) quit
root&#64;alu:~# fdisk /dev/sdz
GNU Fdisk 1.0
Copyright (C) 1998 - 2006 Free Software Foundation, Inc.
This program is free software, covered by the GNU General Public License.

This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.  See the GNU General Public License for more details.

Using /dev/sdz
Command (m for help): p

Disk /dev/sdz: 2199 GB, 2199020382720 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdz1               1      267350  2147488843   83  Linux
Command (m for help): q
root&#64;alu:~# mke2fs -j -i 262144 -L Drobo01 -m 0 -O sparse_super,^resize_inode /dev/sdz1
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=Drobo01
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
8388608 inodes, 536870886 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
16384 block groups
32768 blocks per group, 32768 fragments per group
512 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
root&#64;alu:~#
root&#64;alu:~# mount /dev/sdz1 /mnt
</pre>
<div class="section" id="getting-source">
<h2><a class="toc-backref" href="#id11">Getting Source</a></h2>
<p>See DEVELOPERS.txt</p>
</div>
<div class="section" id="multiple-luns">
<h2><a class="toc-backref" href="#id12">Multiple LUNS</a></h2>
<p>LUN is an abbreviation of 'Logical UNit'. The origin of the term is SCSI terminology.
When RAID units became too large for support in the past, and were sub-divided
to present smaller units the operating system.  The default LUNSIZE on Drobos
is 2 TiB (adjustable using the tools.) If more disk space (after
allowing for parity/redundancy) than LUNSIZE is installed in a
unit, Drobo will show a second (or even third) LUN.  Each LUN
shows up in Linux as a separate disk (examples if the first
LUN shows up as /dev/sde, the next will be /dev/sdf, then /dev/sdg.)</p>
<p>If you think you should see multiple LUNS and you don't, you
might have a look at some kernel settings:
make sure that scsi_mod kernel module is loaded, make
sure /sys/module/scsi_mod/parameters/max_luns is &gt; 1.</p>
<p>Droboview will start up one GUI per drobo, regardless of the number
of LUNS.  If asked to format, all LUNS for the device will be formatted.</p>
<dl class="docutils">
<dt>ON LUNSIZES &gt;= 2TB:</dt>
<dd><dl class="first last docutils">
<dt>-- On older distributions, there are a couple of gotchas related to</dt>
<dd><blockquote class="first">
<dl class="docutils">
<dt>linux tools which aren't 2TB ready...  to exceed 2 TB, you need to:</dt>
<dd><dl class="first last docutils">
<dt>-- use GPT partitions, which aren´t supported by older fdisk</dt>
<dd>versions.  Tools based on libparted work fine, mostly.</dd>
<dt>-- gparted fails, and seems to have a 1 TB limit on devices.</dt>
<dd>(bug #524948 reported to bugzilla.gnome.org) It's just the GUI,
as libparted is fine, and other tools based on it
still work.</dd>
</dl>
</dd>
</dl>
</blockquote>
<dl class="last docutils">
<dt>-- on linux kernel &lt; 2.6.24 supposedly, the USB layer won't let one address</dt>
<dd>LUNs/offsets &gt; 2 TB.  For example, Ubuntu hardy (8.04) released in Spring
2008 has a 2.6.24, and so is OK.  I've never been able to test this problem.</dd>
<dt>-- ext3 with 4K blocks is supposed to allow file system capacity of 8 TiB.</dt>
<dd>4K blocks seem to be assigned by default. So I think a good max.
It would be fun to set the LunSIZE to 8 TiB and test it out...</dd>
</dl>
</dd>
</dl>
</dd>
</dl>
</div>
<div class="section" id="drobo-pro">
<h2><a class="toc-backref" href="#id13">Drobo Pro</a></h2>
<p>Drobo-utils depends on the linux generic scsi layer.  I suspect that
there is just a basic ethernet connection now, and you a few additional driver layers
set up before it will work.   You need to configure the iscsi driver to recognize
the device.  Lemonizer on the Google Group 2009/05/16 reported good luck with:</p>
<p>I had to manually configure the ip of the dbpro from the Drobo
Dashboard on my macbook to do this as I'm not sure how to get the
portal ip for iscsiadm. In my case it was 192.168.2.80 port 3260 and
I'll use that ip in the example below</p>
<ol class="arabic simple">
<li>Configure iscsi ip address via drobo dashboard on win/osx</li>
<li>Install open-iscsi (<a class="reference external" href="http://www.open-iscsi.org/">http://www.open-iscsi.org/</a>): sudo apt-get install open-iscsi</li>
<li>Connect the dbpro to host machine via iscsi</li>
<li>Query dbpro's id: sudo iscsiadm --mode discovery --type sendtargets --portal 192.168.2.80</li>
<li>Copy the id string returned by iscsiadm, something like &quot;iqn.2005-06.com.datarobotics:drobopro.tdb091840080.node0&quot;</li>
<li>Connect to the dbpro: sudo iscsiadm --mode node --targetname iqn.2005-06.com.datarobotics:drobopro.tdb091840080.node0 --portal 192.168.2.80:3260 --login</li>
</ol>
<p>If everything went well, your dbpro should show up under /dev. Also
check /var/log/messages to confirm that the iscsi device connected
successfully.</p>
<p>After that, drobo-utils should be able to detect the Drobo and manage
it over ethernet.</p>
<p>(source: <a class="reference external" href="http://groups.google.com/group/drobo-talk/browse_frm/thread/453e02e105e9b41?hl=en">http://groups.google.com/group/drobo-talk/browse_frm/thread/453e02e105e9b41?hl=en</a> )</p>
<p>Some people reported data corruption.  This link claims to fix one such
issue:
<a class="reference external" href="http://www.drobospace.com/forum/thread/13951/Dropped-iSCSI-connections/?page=2#24792">http://www.drobospace.com/forum/thread/13951/Dropped-iSCSI-connections/?page=2#24792</a></p>
</div>
</div>
<div class="section" id="drobo-firmware">
<h1><a class="toc-backref" href="#id14">Drobo Firmware</a></h1>
<p>Upgrading firmware is pretty self-explanatory in the GUI.  the first time you
press the Update button, it checks to see if a new firmware is available.  If
it there is newer firmware, it offer to upgrade, with suitable prompts.
Similarly, the line mode interface has two commands to deal with firmware,
fwcheck will tell you if an upgrade is required.  the fwupgrade
will do the job.  It takes a few minutes, and prints a status
you you can see how it is progressing.  Have patience:</p>
<pre class="literal-block">
root&#64;pepino:/home/peter/drobo/drobo-utils/trunk# drobom fwupgrade

validateFirmware start...
Magic number validated. Good.
484 + 2937552 = 2938036 length validated. Good.
CRC from header: 4260378881, calculated using python zlib crc32: 398201869
yeah, the header CRCs do not match. For now they never do ... ignoring it.
CRC for body from header: 1852877921, calculated: 1852877921
32 bit Cyclic Redundancy Check correct. Good.
validateFirmware successful...
writeFirmware: i=484, start=484, last=2938036 fw length= 488
.
wrote  32768  bytes... total: 33252
wrote  32768  bytes... total: 66020
.
.
.
wrote  32768  bytes... total: 2720228
wrote  32768  bytes... total: 2752996
wrote  32768  bytes... total: 2785764
wrote  32768  bytes... total: 2818532
wrote  32768  bytes... total: 2851300
wrote  32768  bytes... total: 2884068
wrote  32768  bytes... total: 2916836
wrote  21200  bytes... total: 2938036
writeFirmware Done.  i=2938036, len=2938036
root&#64;pepino:/home/peter/drobo/drobo-utils/trunk#
</pre>
<p>when it's done, you can check if it worked using:</p>
<pre class="literal-block">
root&#64;pepino# drobom status
/dev/sdf - 00% full - (['New firmware installed'], 0)
</pre>
<p>If the status is like that, then do:</p>
<pre class="literal-block">
root&#64;pepino:/home/peter/drobo/drobo-utils/trunk# drobom shutdown
</pre>
<p>lights will flash etc... wait until Drobo goes dark.
Wait another five seconds, then un-plug the USB / connector.</p>
<p>Plug it back in, and wait 10 seconds.
it should start up with the latest firmware available for your drobo.</p>
<p>The drobom commands, like DRI's dashboard, will normally
get the latest and greatest firmware and upgrade.  If you have
the need, you can load arbitrary firmware from the CLI with
fwload command.</p>
<div class="section" id="safety">
<h2><a class="toc-backref" href="#id15">SAFETY</a></h2>
<p>Those worried about safety of using this software should know:  it was
developed with assistance from the vendor (Data Robotics Inc.), and
in 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 built
into the firmware upgrade process, so it is next to impossible to brick a drobo
using the tools.  Drobo-utils verifies firmware checksums before attempting
to upload the image to the device, and the device checks the firmware against
the checksums as well.  New firmware is loaded into an alternate location
from the currently active one, and if activation of the new firmware fails,
the drobo will simply boot the old one.</p>
<p>On the other hand, common sense rules do apply.  Setting the LUN size, or
re-formatting a Drobo will erase all your data whether you do it on Linux or
any other operating system.  These are power tools, and they can do some
damage to your data if used without proper care.  For example, the reliability
of any storage unit does not reduce the need for backups it only makes doing them
easier. A Drobo is an excellent place to put backups, but not a substitute for
them.  Backups are the only way to address error 18 (the number of inches in
front of the keyboard the source of the issue lies.) and no storage unit can
protect against fire or flood.</p>
</div>
<div class="section" id="compatibility">
<h2><a class="toc-backref" href="#id16">Compatibility</a></h2>
<p>Drobo has been tested with every old firmware version. Any Drobo should
be upgradable to modern firmware using the dashboard.</p>
<blockquote>
<dl class="docutils">
<dt>NOTE: really need at least 1.1.1 to use Linux &amp; ext3.</dt>
<dd>just use the tools to upgrade your firmware ASAP.</dd>
<dt>1.01  - very old... bad idea to install this, need to write</dt>
<dd>a script to get out, because it isn't in the revision
table.
not much works except firmware upgrade.</dd>
</dl>
<p>1.0.2 - works ok in CLI And GUI to view, and upgrade firmware.</p>
<dl class="docutils">
<dt>1.0.3 - GUI and CLI work OK, can upgrade firmware.</dt>
<dd>Used ntfs3g for a few months under ubuntu 7.10 Linux.
Used 2 TB LUN, with 1.5 TB of physical space available.</dd>
<dt>1.1.0 - dashboard works no issues.</dt>
<dd><ul class="first last simple">
<li>from this point, you don't seem to need to unplug the USB
connector to complete the upgrade.</li>
<li>firmware prior to here deals badly with ext3.</li>
</ul>
</dd>
<dt>1.1.1 - 1.2.4 works without issues.</dt>
<dd>('name' not supported by firmware)</dd>
</dl>
<p>1.3.0 - works without issues.</p>
</blockquote>
</div>
</div>
<div class="section" id="known-bugs">
<h1><a class="toc-backref" href="#id17">KNOWN BUGS</a></h1>
<p>droboview isn't suited to run continuously for long periods,
as it has a memory leak...  total foot print starts out at 32M
with a 15 MB resident set size, of which 10 MB are shared, so only
about 4M of real memory consumed.   but the RSS grows at about
2MB/hour.</p>
<blockquote>
29m  11m S    1  2.9   9:44.50 droboview</blockquote>
<p>best to restart it daily, or use it when necessary, but not leave it
on for days.</p>
<p>After you resize luns, droboview gets confused, you need to exit and
restart.</p>
<p>We have a report that dumping diagnostics does not work over firewire.
Work-around:  connect via USB.</p>
</div>
<div class="section" id="droboshare-support">
<h1><a class="toc-backref" href="#id18">Droboshare Support</a></h1>
<p>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 run
drobo-utils un-modified on the droboshare itself.  In order to do run drobo-utils, you need to build a python interpreter.  A python interpreter has, itself,
a bunch of dependencies.  So you need to install a whack of packages on the droboshare in order to get a working drobo-utils.  This is where DARFS comes in.</p>
<div class="section" id="darfs">
<h2><a class="toc-backref" href="#id19">DARFS</a></h2>
<p>The Droboshare Augmented Root File System (darfs) is a 60 MB or so download
you can get from drobo-utils.sf.net.  There isn't any source code, because,
well, nothing from any of the packages has been modified.  there are
instructions on how to build DARFS in DEVELOPERS.html</p>
<p>DARFS is a standard droboshare root file system, with some packages added:
openssl, openssh, berkeleydb, bzip2, a fairly complete Python 2.6.2.  drobo-
utils is a python app. and it works in line and API mode, natively, on
the droboshare.  for example, I've used it to replace the firmware. no
problem at all.</p>
<p>People un-afraid of the command line can upgrade drobo firmware, query
status, and take diagnositc dumps, from the command line on the droboshare
itself, just as they would on any linux host computer.  But a full GUI
would be too much for the little processor and more importantly the limited
memory in the droboshare, so that is not provided.</p>
</div>
<div class="section" id="darfs-installation">
<h2><a class="toc-backref" href="#id20">DARFS Installation</a></h2>
<p>Download it from drobo-utils.sf.net:
steps:</p>
<blockquote>
<ol class="arabic simple">
<li>copy the tar file onto somewhere on your share.</li>
<li>log in via DropBear ssh as a root user on the droboshare.</li>
<li>cd /mnt/DroboShares/YourDrobo (root of drobo file system, for example)</li>
<li>tar -xzf darfs.tgz (root of drobo file system, for example)</li>
<li>the root directory of the tar is 'slash'.. it will be under YourDrobo</li>
<li>export PATH=&quot;/mnt/DroboShares/YourDrobo/slash/usr/bin:${PATH}&quot;  (which is where python and drobom are.)</li>
<li>drobom status</li>
</ol>
</blockquote>
<p>you're done!</p>
</div>
<div class="section" id="enable-sftp-support">
<h2><a class="toc-backref" href="#id21">Enable SFTP Support</a></h2>
<p>all you need to do is:</p>
<p>ln -s /usr/libexec /mnt/Droboshares/YourDrobo/slash/usr/libexec</p>
<p>Try an sftp from another machine (as root...) and it ought to work.</p>
<p>(explanation: when one tries to sftp to a droboshare, it gives an error
about trying to exec '/usr/libexec/sftp-server'.  Openssh builds the
right binary, but Dropbear doesn't know where to look for it.  the
libexec directory isn't there on the droboshare, so there is no harm
in creating it and linking into DARFS.)</p>
</div>
<div class="section" id="building-droboshare-applications">
<h2><a class="toc-backref" href="#id22">Building Droboshare applications</a></h2>
<blockquote>
See DEVELOPERS.txt</blockquote>
</div>
<div class="section" id="droboshare-firmware">
<h2><a class="toc-backref" href="#id23">Droboshare Firmware</a></h2>
<p>With DARFS, and the third party software you can get from drobospace and
drobo.com, the droboshare is very open and hackable.   However, there
remains one remaining limitation: There is no open source way to upgrade
or modify droboshare firmware.  If you want to re-flash to a factory
original state, you need the vendor dashboard.</p>
</div>
</div>
<div class="section" id="credits">
<h1><a class="toc-backref" href="#id24">Credits</a></h1>
<p>who did what:</p>
<pre class="literal-block">
Peter Silva:    wrote most all of it.
Chris Atlee:    the proper debian packaging.
Brad Guillory:  some help with diagnostics and patches.
Joe Krahn:      lots of inspiration.
Andy Grover:    some elegance cleanups.
</pre>
</div>
<div class="section" id="administrivia">
<h1><a class="toc-backref" href="#id25">Administrivia</a></h1>
<p>version 0.6.1, October 6th 2009.</p>
<p>copyright:</p>
<p>Drobo Utils Copyright (C) 2008,2009  Peter Silva (<a class="reference external" href="mailto:Peter.A.Silva&#64;gmail.com">Peter.A.Silva&#64;gmail.com</a>)
Drobo Utils comes with ABSOLUTELY NO WARRANTY; For details type see the file
named COPYING in the root of the source directory tree.</p>
</div>
</div>
</body>
</html>