new drobo-utils version. DroboPRO testers wanted!
Peter.A.Silva
drobom info options
If the reply makes sense, then try something like:
drobom set UseStaticIPAddress True
drobom set IPAddress 192.168.5.5
drobom set NetMask 255.255.255.0
drobom info options
if that works, then try rebooting, and see what happens.
It may eat your first born. Would love to hear how it goes either
way.
philobyte
It isn't in master on the git repository yet... I switched to git, and
got myself a bit confused,
so the good code is only on r0_6_1 branch for now.
robj
just installed 0.6.1 on my Centos 5 / Drobopro machine.
I'm still trying to get the volume size / partitioning etc set up on a
new set of drives so I've not done much with it yet.
One request, something I also noticed in 0.6.0 -
On the older version I'm using on the machine with the V2, the drive
info is listed one-per-line in a very readable table.
The new (or on the Pro) versions show all the drive info in one very
long, wrapped, line. Can you change this to show one drive per line as
the older one, it would be much more readable.
I'll try some more tests one I get the thing formatted the way I want.
Thanks,
Robert.
Peter Silva
jos...@freivald.com
Does the drobo-talk software work with iSCSI? I tried activating iSCSI and
I get a bunch of connection errors (I think it's a security hand-shake
thing). If the answer is 'yes, it should work' then I'll bother you with
the rest of the details. If 'no, it doesn't do iSCSI', then I'll shuffle
the boxes around and get them within range for FireWire800.
Thanks.
--JATF
On Sun, 18 Oct 2009 08:48:37 -0400, Peter Silva <infor...@gmail.com>
wrote:
Sebastian Sobolewski
Yes it should, I successfully use it over iSCSI without issues, however, you do need to change the Open iSCSI initiator parameters to get it to work reliably.
See: http://www.thirdmartini.com/index.php/DroboPro%2C_iSCSI_and_Linux
-Sebastian
I'm being facetious.
jos...@freivald.com
Okay, thanks.
I will try that this week and report back any issues.
--JATF
Peter Silva
I hope that that is obsolete...check out the first post in this thread. drobo-utils can do that now... at least it might... someone needs to test it !
jos...@freivald.com
I had already done that when I tried it before. I won't get to it
tomorrow, but I hope to get to it by Wednesday.
On a side note, if it does work, can I partition the drobopro with more
than 2tb partitions? The Windows droboapp didn't let me, which was
particularly aggravating because I outfitted it with 8TB of space. Is it
possible to share the drobo between two separate computers, either by using
the same iScsi target on two platforms or by creating 2 partitions with
separate targets?
Sorry if some of the questions are 'newb'. I've use Linux since the mid
90's, but I've never had use for a SAN before - Samba always filled the gap
and performance hasn't been an issue up til now.
Thanks for the great support.
--JATF
On Sun, 18 Oct 2009 20:40:24 -0400, Peter Silva <infor...@gmail.com>
robj
Peter - yep, something like that layout would be great, thanks!
JATF -
The 'does it work above 2TB' question is the big unknown at present.
The older firmware messed up in a big way, but the new one may have
fixed something..
I've just got mine re-partitioned and formatted (to 8TB volume size)
after getting rid of the corrupt leftovers from earlier tests, I will
start loading it up in a few days and see what happens.
Robert.
Peter Silva
Sebastian
On Oct 18, 10:25 pm, <jos...@freivald.com> wrote:
> particularly aggravating because I outfitted it with 8TB of space. Is it
> possible to share the drobo between two separate computers, either by using
> the same iScsi target on two platforms or by creating 2 partitions with
> separate targets?
(1) Split the drobo into N sized chunks/luns (IE 2TB). Then use 1(or
more luns) per PC but only as long as the same lun is not used by
more then 1 PC art a time.. Ext3,ntfs, etc . don't know about each
other so this will result in data corruption if you share the same
lun. ( Technically it should work with partitions as long as the same
rules are followed... but I've personally not tested it)
(2) Use a clustering FS that is designed to use a shared disk ( Then
multiple PCs can see and rewad/write to the SAME lun ). However, the
drawback here is that the LED indicators and capacity status on the
drobo will no longer work. ( Note: this is how VMWare/ESX uses the
drobopro )
In either case for this to work you need to configure your iSCSI
Initiator to discover the Luns on port 3261 ( instead of the default
3260 ). 3261 allows sharing the drobo, but assumes you are doing one
of the 2 options above.
-Sebastian
jos...@freivald.com
Fascinating. Does GFS count as one of these file systems, because that
just sounds absolutely awesome - to have shared LUNS across multiple
machines on an iSCSI platform - and the drobo is in the rack where I can't
see the lights anyway. The drobo space management continues to work the
same way? If I add in several 2TB drives they will auto-magically provide
more space? How do you know if there is a failure?
--JATF
On Mon, 19 Oct 2009 09:36:37 -0700 (PDT), Sebastian <spso...@gmail.com>
wrote:
Sebastian
From my experience expansion works fine, just the LEDs and the
Capacity usage gauge in the dashboard/drobom utilities is what seems
to have issues. ( IE: it never goes down if you delete files .. it
just ends up showing the max used capacity ). Not sure about GFS as
I've only played with the vmfs (ESX) support on it and that works
fine. ( Multiple ESX hosts seeing the same LUN/files )
I would think drive failure reporting should work as well.. though
I've not had a drive fail me yet.
spso...@gmail.com
Adding a node using OCFS was a breeze as well... in all I had 4 Virtual Ubuntu 8.04 servers talking to the same OCFS filesystem and the drobo seemed to handle it ok. ( I did not do any data integrity testing.. but I didn't notice anything odd )
Peter.A.Silva
Would be cool if people with a DroboPRO (where all the optons work)
could check it out, and verify whether the new 'Options' tab works for
them.
Peter.A.Silva
of various levels of fixed ness, I'd rather get some testing done and
release a single, working version. So I need some people to try out
the development branch.
The only new stuff in there is related to option getting and setting,
and a the info listings have been made more readable.
Any drobo pro users out there in particular, it would be really
helpful if you could test out the latest
dev version. It's really easy to do in a "try before you buy" mode,
it will not replace the stable version installed via apt-get/dpkg...
But you need to install the git source code manager.
# on ubuntu or other debian-derived systems... in a shell:
sudo apt-get install git
#
sudo ./drobom info options
To get the stable version of drobom or droboview, just leave out the
'./' in the above.
ElliotA
what exactly would you like tested? We have a drobopro that seems to
be working fine, except it can't reclaim space.
Running under ubuntu hardy server
8TB LUN size, though we'd love 16.
ext3
iscsi
results of the dev version drobom info options:
---------------------------------------------------------
Drobo Name: DroboPro Devices: /dev/sdc
Time: Tue Dec 8 11:09:02 2009
---------------------------------------------------------
query options result:
UseStaticIPAddress True
UseManualVolumeManagement False
YellowThreshold 85
SpinDownDelayMinutes 15
RedThreshold 95
SpinDownDelay True
NetMask 255.255.0.0
DualDiskRedundancy False
IPAddress 169.254.1.1
---------------------------------------------------------
Andrew Chalaturnyk
--
You received this message because you are subscribed to the Google Groups "drobo-talk" group.
To post to this group, send email to drobo...@googlegroups.com.
To unsubscribe from this group, send email to drobo-talk+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/drobo-talk?hl=en.
Andrew Chalaturnyk
Peter Silva
Peter.A.Silva
On Dec 8, 4:01 pm, Andrew Chalaturnyk <aacha...@gmail.com> wrote:
> The set SpinDownDelay True/False does not work (tried via iscsi)
>
> The print diagnostics is unreadable
>
> When the yellow threshold is changed will that change when the drobopro
> starts its slow down
> so you can do a timely storage upgrade?
Red Alert is %full when the slow down starts.
>
> Is there a way to target a machine (have multiple drobopros on the same
> subnet via iscsi)?
>
you can then do
drobom --device=/dev/sdX <cmd>
to target a particular device.
ElliotA
> by Linux (ext3 and ntfs, someone tested hpfs too.) with LUNSIZE > 2 TiB.
Is there a command to tell the drobopro to poll the file system for
free space?
Some other interesting bits (thanks for the great tool by the way)
drobom info luns
# These are actually formatted ext3, but I think someone else pointed
out that was broken.
---------------------------------------------------------
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
Time: Thu Dec 10 14:53:56 2009
---------------------------------------------------------
hoho! multiple partition types! Brave are we not?
lun size (GB) used PTFmt FStype:
0 2199 1059 GPT ['NTFS']
0 0 0 No Partitions ['NTFS']
0 0 0 GPT ['NTFS', 'EXT3']
---------------------------------------------------------
drobom info config:
---------------------------------------------------------
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
Time: Thu Dec 10 14:52:58 2009
---------------------------------------------------------
Configuration maxima: slots: 8, luns: 16, lunsize: 36028799 TB
---------------------------------------------------------
drobom info slots
---------------------------------------------------------
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
Time: Thu Dec 10 14:51:20 2009
---------------------------------------------------------
query slotinfo result: number of slots: 8
slot GB Model Status
0 2000 Hitachi HDS722020ALA330 green
1 2000 Hitachi HDS722020ALA330 green
2 2000 Hitachi HDS722020ALA330 green
3 2000 Hitachi HDS722020ALA330 green
4 0 gray
5 0 gray
6 0 gray
7 0 gray
---------------------------------------------------------
Peter Silva
Peter.A.Silva
drobom info options
drobom set DualDiskRedundancy True
drobom set IPAddress 123.123.123.123
drobom set NetMask 255.255.0.0
drobom set SpinDownDelay 10
drobom set SpinDownDelay True
drobom info options
(yes I know someone reported spindowndelay not working, but with no
clue as to how it failed, the result isn´t useful...)
If someone can run the above, and print the output that would allow me
to cut a release
with the current development version.
> > .
Elliot
ElliotA
in via iscsi:
root@clutch:~/drobom-dev/drobo-utils# ./drobom info options
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
query options result:
UseStaticIPAddress True
UseManualVolumeManagement False
YellowThreshold 85
SpinDownDelayMinutes 15
RedThreshold 95
SpinDownDelay True
NetMask 255.255.0.0
DualDiskRedundancy False
IPAddress 169.254.1.1
---------------------------------------------------------
True
Traceback (most recent call last):
File "./drobom", line 338, in <module>
d.SetOptions( options )
File "/root/drobom-dev/drobo-utils/Drobo.py", line 550, in
SetOptions
if (d["DualDiskRedundancy"]):
NameError: global name 'd' is not defined
root@clutch:~/drobom-dev/drobo-utils# ./drobom set SpinDownDelay 10
Traceback (most recent call last):
File "./drobom", line 338, in <module>
d.SetOptions( options )
File "/root/drobom-dev/drobo-utils/Drobo.py", line 550, in
SetOptions
if (d["DualDiskRedundancy"]):
NameError: global name 'd' is not defined
root@clutch:~/drobom-dev/drobo-utils# ./drobom set SpinDownDelay True
Traceback (most recent call last):
File "./drobom", line 338, in <module>
d.SetOptions( options )
File "/root/drobom-dev/drobo-utils/Drobo.py", line 550, in
SetOptions
if (d["DualDiskRedundancy"]):
NameError: global name 'd' is not defined
root@clutch:~/drobom-dev/drobo-utils# ./drobom info options
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
Andrew Chalaturnyk
To unsubscribe from this group, send email to drobo-talk+...@googlegroups.com.
Peter Silva
I fixed that bug. please git pull, and try again, hope it works now.
>> > > .
>> > > For more options, visit this group at
>> > >http://groups.google.com/group/drobo-talk?hl=en.
>>
>> --
>>
>> You received this message because you are subscribed to the Google Groups
>> "drobo-talk" group.
>> To post to this group, send email to drobo...@googlegroups.com.
>> To unsubscribe from this group, send email to
ElliotA
root@clutch:~/drobom-dev/drobo-utils# ./drobom info options
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
query options result:
UseStaticIPAddress True
UseManualVolumeManagement False
YellowThreshold 85
SpinDownDelayMinutes 15
RedThreshold 95
SpinDownDelay True
NetMask 255.255.0.0
DualDiskRedundancy False
IPAddress 169.254.1.1
---------------------------------------------------------
True
integer overflow masking is deprecated
flags, options["SpinDownDelayMinutes"], rawip, rawnm, "" )
File "./drobom", line 338, in <module>
d.SetOptions( options )
SetOptions
flags, options["SpinDownDelayMinutes"], rawip, rawnm, "" )
File "/usr/lib/python2.5/struct.py", line 63, in pack
return o.pack(*args)
TypeError: unsupported operand type(s) for &: 'str' and 'long'
Peter Silva
try again...
ElliotA
root@clutch:~/drobom-dev/drobo-utils# ./drobom info options
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
query options result:
UseStaticIPAddress True
UseManualVolumeManagement False
YellowThreshold 85
SpinDownDelayMinutes 15
RedThreshold 95
SpinDownDelay True
NetMask 255.255.0.0
DualDiskRedundancy False
IPAddress 169.254.1.1
---------------------------------------------------------
True
/root/drobom-dev/drobo-utils/Drobo.py:562: DeprecationWarning: struct
integer overflow masking is deprecated
root@clutch:~/drobom-dev/drobo-utils# ./drobom set SpinDownDelay 10
integer overflow masking is deprecated
root@clutch:~/drobom-dev/drobo-utils# ./drobom set SpinDownDelay False
integer overflow masking is deprecated
root@clutch:~/drobom-dev/drobo-utils# ./drobom set IPAddress
123.123.123.123
integer overflow masking is deprecated
root@clutch:~/drobom-dev/drobo-utils# ./drobom set NetMask 255.255.0.0
integer overflow masking is deprecated
root@clutch:~/drobom-dev/drobo-utils# ./drobom info options
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
query options result:
UseStaticIPAddress True
UseManualVolumeManagement False
YellowThreshold 85
RedThreshold 95
SpinDownDelay False
NetMask 255.255.0.0
DualDiskRedundancy True
IPAddress 123.123.123.123
---------------------------------------------------------
ElliotA
correctly.
ElliotA
resets changes, at least for RedThreshold, SpinDown and SpinDownMinutes
Andrew Chalaturnyk
Elliot
Andrew Chalaturnyk
Peter Silva
changed code to flip SpinDownDelay on/off based on
SpinDownDelayMinutes setting alone...
ie. >0 causes bit to be set, == 0 , clears.
Please re-test:
drobom set SpinDownDelayMinutes 10
and see if that works.
Andrew Chalaturnyk
Peter Silva
Please test address setting again, as I added a mask to get rid of the warning.
optparse will make it shorter? don't grok, will take a look, samples
and pointers welcome!
On 12/16/09, Andrew Chalaturnyk <aach...@gmail.com> wrote:
> Seems to work.
>
> btw. On a side note, for option parsing did you consider using optparse? It
> would save a lot of coding. (and you could use the -d flag etc anywhere on
> the cmd line)
>
> On Wed, Dec 16, 2009 at 6:16 PM, Peter Silva <Peter....@gmail.com>wrote:
>
>> Great Stuff! Thanks Everyone so far, we are getting there!
>>
>> changed code to flip SpinDownDelay on/off based on
>> SpinDownDelayMinutes setting alone...
>> ie. >0 causes bit to be set, == 0 , clears.
>>
>> Please re-test:
>>
>> drobom set SpinDownDelayMinutes 10
>>
>> and see if that works.
>>
>> --
>>
>> You received this message because you are subscribed to the Google Groups
>> "drobo-talk" group.
>> To post to this group, send email to drobo...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> drobo-talk+...@googlegroups.com<drobo-talk%2Bunsu...@googlegroups.com>
Peter Silva
variety, need to test with both, as there are bit manipulations.
Andrew Chalaturnyk
Elliot
Could you remove the PleaseEraseMyData requirement from "drobom format" since it doesn't actually do the format until you run the script. Alternatively you could make it run the script automatically, though I like that less. Also, any chance you could you change the PleaseEraseMyData to a more standard confirmation yes/no [Y]? I think it would make the app feel a bit more native, and for things like "drobom format" it would mean you could write the script and then offer to run it as a second step.
I'm not a python programmer, so I have no idea if that would be a major re-write or not, but I do think it would be an improvement.
Thanks for your great app.
Peter Silva
endearing... oh well...
I feel crushed by conformism... reminds me of an apple ad ;-)
git pull will give you what you asked for:
by default it prompts (for setlunsize and format)
you can have be non-destructive with -n or totally destructive with -y
the format stuff is now a sub-process, haven't tested how i/o to the sub-process
is handled (if mkext2fs issues a prompt, not sure if the caller gets it.)
if it doesn't work, just run the fmtscript manually after.
Elliot
Thanks for the change though. I won't be able to test the changes immediately, and hopefully not for a long time as we went "production" with our drobo yesterday.
Andrew Chalaturnyk
Peter.A.Silva
> > > On 12/16/09, Elliot <elliotand...@gmail.com> wrote:
> > >> Since Andrew had a suggestion, I guess I'll add mine.
>
> > >> Could you remove the PleaseEraseMyData requirement from "drobom format"
> > >> since it doesn't actually do the format until you run the script.
> > >> Alternatively you could make it run the script automatically, though I
> > like
> > >> that less. Also, any chance you could you change the PleaseEraseMyData
> > to a
> > >> more standard confirmation yes/no [Y]? I think it would make the app
> > feel a
> > >> bit more native, and for things like "drobom format" it would mean you
> > could
> > >> write the script and then offer to run it as a second step.
>
> > >> I'm not a python programmer, so I have no idea if that would be a major
> > >> re-write or not, but I do think it would be an improvement.
>
> > >> Thanks for your great app.
>
> > >> On Dec 16, 2009, at 7:53 PM, Peter Silva wrote:
>
> > >>> Great!
>
> > >>> Please test address setting again, as I added a mask to get rid of the
> > >>> warning.
>
> > >>> optparse will make it shorter? don't grok, will take a look, samples
> > >>> and pointers welcome!
>
> > >>> On 12/16/09, Andrew Chalaturnyk <aacha...@gmail.com> wrote:
> > >>>> Seems to work.
>
> > >>>> btw. On a side note, for option parsing did you consider using
> > optparse?
> > >>>> It
> > >>>> would save a lot of coding. (and you could use the -d flag etc
> > anywhere
> > >>>> on
> > >>>> the cmd line)
>
> > >>>> On Wed, Dec 16, 2009 at 6:16 PM, Peter Silva
> > >>>> <Peter.A.Si...@gmail.com>wrote:
>
> > >>>>> Great Stuff! Thanks Everyone so far, we are getting there!
>
> > >>>>> changed code to flip SpinDownDelay on/off based on
> > >>>>> SpinDownDelayMinutes setting alone...
> > >>>>> ie. >0 causes bit to be set, == 0 , clears.
>
> > >>>>> Please re-test:
>
> > >>>>> drobom set SpinDownDelayMinutes 10
>
> > >>>>> and see if that works.
>
> > >>>>> --
>
> > >>>>> You received this message because you are subscribed to the Google
> > >>>>> Groups
> > >>>>> "drobo-talk" group.
> > >>>>> To post to this group, send email to drobo...@googlegroups.com.
> > >>>>> To unsubscribe from this group, send email to
> > >>>>> drobo-talk+...@googlegroups.com<drobo-talk%2Bunsubscribe@googlegrou ps.com>
> > <drobo-talk%2Bunsu...@googlegroups.com<drobo-talk%252Bunsubscribe@googl egroups.com>
>
> > >>>>> .
> > >>>>> For more options, visit this group at
> > >>>>>http://groups.google.com/group/drobo-talk?hl=en.
>
> > >>>> --
>
> > >>>> You received this message because you are subscribed to the Google
> > Groups
> > >>>> "drobo-talk" group.
> > >>>> To post to this group, send email to drobo...@googlegroups.com.
> > >>>> To unsubscribe from this group, send email to
> > >>>> drobo-talk+...@googlegroups.com<drobo-talk%2Bunsubscribe@googlegrou ps.com>
> > .
> > >>>> For more options, visit this group at
> > >>>>http://groups.google.com/group/drobo-talk?hl=en.
>
> > >>> --
>
> > >>> You received this message because you are subscribed to the Google
> > Groups
> > >>> "drobo-talk" group.
> > >>> To post to this group, send email to drobo...@googlegroups.com.
> > >>> To unsubscribe from this group, send email to
> > >>> drobo-talk+...@googlegroups.com<drobo-talk%2Bunsubscribe@googlegrou ps.com>
> > .
> > >>> For more options, visit this group at
> > >>>http://groups.google.com/group/drobo-talk?hl=en.
>
> > >> --
>
> > >> You received this message because you are subscribed to the Google
> > Groups
> > >> "drobo-talk" group.
> > >> To post to this group, send email to drobo...@googlegroups.com.
> > >> To unsubscribe from this group, send email to
> > >> drobo-talk+...@googlegroups.com<drobo-talk%2Bunsubscribe@googlegrou ps.com>
> > .
> > >> For more options, visit this group at
> > >>http://groups.google.com/group/drobo-talk?hl=en.
>
> > > --
>
> > > You received this message because you are subscribed to the Google Groups
> > "drobo-talk" group.
> > > To post to this group, send email to drobo...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > drobo-talk+...@googlegroups.com<drobo-talk%2Bunsubscribe@googlegrou ps.com>
> > .
> > > For more options, visit this group at
> >http://groups.google.com/group/drobo-talk?hl=en.
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "drobo-talk" group.
> > To post to this group, send email to drobo...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > drobo-talk+...@googlegroups.com<drobo-talk%2Bunsubscribe@googlegrou ps.com>
docfruitbat
(I apologize for this long post in advance. I have many
questions... :-)
I have a newly minted DroboPro loaded with 8x500Gb drives and am using
it via iSCSI.
(I love how quiet and energy efficient this thing is, btw!!)
I have a question concerning partitions that I haven't found discussed
in the drobospace forums, so I'll ask it here first since this
question may only be relevant to ext2 filesystem usage and drobo-
utils.
That question is: can a drobo volume have multiple partitions?
I noticed that Drobo Dashboard (and drobo-utils) seems to create only
one partition (which is the full size of the volume). Is it possible
to, say, create multiple partitions in a volume? I haven't
experimented with this yet (don't really want to break my new
*expensive* toy :-). But, my needs are such that I need 8 separate
"partitions". I was hoping I could create one hugh 16Tb volume and
then create 8 partitions within it, but I don't know if it's supported
or not or what issues this might have.
For this reason, I've manually created 8 volumes via Drobo Dashboard
(installed in a Windows XP instance running under VMware) since drobo-
utils doesn't implement manual volume creation/deletion (yet?
please?? :-).
After creating the volumes (which Dashboard restricted to 2Tb and
NTFS), I used drobo-utils to "format" them as ext2. Now, Dashboard
says the volumes are all filesystem type "unknown". Drobo-utils says
this:
root@gremlin:~# drobom info luns
---------------------------------------------------------
Drobo Name: DroboPro Devices: /dev/sdb:/dev/sdc:/dev/sdd:/dev/sde:/
dev/sdf:/dev/sdg:/dev/sdh:/dev/sdi
Time: Fri Dec 18 09:04:16 2009
---------------------------------------------------------
hoho! multiple partition types! Brave are we not?
hoho! multiple partition types! Brave are we not?
hoho! multiple partition types! Brave are we not?
hoho! multiple partition types! Brave are we not?
lun size (GB) used PTFmt FStype:
0 2199 14 GPT ['NTFS']
0 0 0 No Partitions ['NTFS']
0 0 0 GPT ['NTFS', 'NO FORMAT', 'EXT3']
0 0 0 None ['NTFS', 'NO FORMAT']
0 0 0 None ['FAT32']
0 0 0 None ['NTFS', 'NO FORMAT']
0 0 0 None ['FAT32']
0 0 0 GPT ['NO FORMAT', 'EXT3']
---------------------------------------------------------
This looks very strange to me...is this an indication of corruption?
Do I need to be concerned?
However, each volume partition table looks like this:
root@gremlin:~# parted -s /dev/sdb print
Disk /dev/sdb: 2199GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 2199GB 2199GB primary
I've been successful in mounting each partition and copying data to
them, so I'm presuming the above is just a cosmetic problem (with
drobo-utils)?
Also, I just pulled the latest git version of drobo-utils and it can't
find my drobopro anymore (says "No Drobos discovered")!
I kept the previous version (just in case) and that version *can* find
my drobopro.
Is anyone else seeing this?
Lastly, I have a chicken and egg question. I have my drobopro mounted
via iSCSI. What happens if I do 'drobom shutdown'? Will the iscsi
attached devices hang? Do I need to do 'drobom shutdown' and then
quick logout the iscsi node? Is there a race condition here? I'm
thinking for automated shutdown situations here (say when the power
goes out and the UPS is saying it's out of battery). I'd want to
"shutdown" the drobo (does this really shut it down??), but if the
command is immediate, the iscsi
attachment will hang...won't it? Is there a way to delay the shutdown
operation long enough to logout the iscsi node?
Anyway, just wanted to chime in as another fellow drobopro owner and
say "thanks" for creating drobo-utils!!
Since this is still a new toy for me, I'm happy to test whatever you
might want, should you need a guinea pig :-)
Peter.A.Silva
i futzed with the luninfo stuff, and the detection. might be all ok
now.
would appreciate seeing
./drobom info luns
fingers crossed.
docfruitbat
root@gremlin:~# drobom -v 16 info luns
examining: /dev/sda
id: (0, 0, 0, 0, 'ATA ')
found a Drobo
appending new lundevs to devices: []
examining: /dev/sdb
id: (0, 0, 0, 0, 'DROBO ')
found a Drobo
appending to lundevs...
examining: /dev/sdc
id: (0, 0, 0, 0, 'DROBO ')
found a Drobo
appending to lundevs...
examining: /dev/sdd
id: (0, 0, 0, 0, 'DROBO ')
found a Drobo
appending to lundevs...
examining: /dev/sde
id: (0, 0, 0, 0, 'DROBO ')
found a Drobo
appending to lundevs...
examining: /dev/sdf
id: (0, 0, 0, 0, 'DROBO ')
found a Drobo
appending to lundevs...
examining: /dev/sdg
id: (0, 0, 0, 0, 'DROBO ')
found a Drobo
appending to lundevs...
examining: /dev/sdh
id: (0, 0, 0, 0, 'DROBO ')
found a Drobo
appending to lundevs...
examining: /dev/sdi
id: (0, 0, 0, 0, 'DROBO ')
found a Drobo
appending to lundevs...
returning list: [['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/
dev/sde', '/dev/sdf', '/dev/sdg', '/dev/sdh', '/dev/sdi']]
trying: ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde',
'/dev/sdf', '/dev/sdg', '/dev/sdh', '/dev/sdi']
cfg: (91, 0, 9846168977766629376L)
settings: (1526726656L, 8, 'OBO DroboPro')
/dev/sda fw[6] is not armmarvell.
No Drobos discovered
Thoughts?
Peter.A.Silva
Andrew Chalaturnyk
--
You received this message because you are subscribed to the Google Groups "drobo-talk" group.
To post to this group, send email to drobo...@googlegroups.com.
To unsubscribe from this group, send email to drobo-talk+...@googlegroups.com.
Andrew Chalaturnyk
Peter.A.Silva
don't really need -v 63 unless the error message is unclear...
sigh... This is going to take a while, because I think the algorithm
for firmware choice has changed.
The spelunking will go on a while...
ElliotA
root@clutch:~/drobom-dev/drobo-utils# ./drobom fwcheck
uh, oh... scsi inquire returned 36, bytes instead of 76 expected.
Traceback (most recent call last):
File "./drobom", line 338, in <module>
tuple=d.PickLatestFirmware()
File "/root/drobom-dev/drobo-utils/Drobo.py", line 790, in
PickLatestFirmware
inqw=self.inquire()
File "/root/drobom-dev/drobo-utils/Drobo.py", line 765, in inquire
raise DroboException
Drobo.DroboExceptionProblem accessing a Drobo: Unknown
root@clutch:~/drobom-dev/drobo-utils# ./drobom status
/dev/sdc:/dev/sdd:/dev/sde /drobo/1:/drobo/2:/drobo/3 DroboPro 25%
full - ([], 0)
root@clutch:~/drobom-dev/drobo-utils# ./drobom fwupgrade
uh, oh... scsi inquire returned 36, bytes instead of 76 expected.
Traceback (most recent call last):
File "./drobom", line 347, in <module>
if d.updateFirmwareRepository():
File "/root/drobom-dev/drobo-utils/Drobo.py", line 949, in
updateFirmwareRepository
(fwarch, fwversion, hwlevel, fwpath ) = self.PickLatestFirmware()
File "/root/drobom-dev/drobo-utils/Drobo.py", line 790, in
PickLatestFirmware
inqw=self.inquire()
File "/root/drobom-dev/drobo-utils/Drobo.py", line 765, in inquire
Andrew Chalaturnyk
Peter Silva
Andrew Chalaturnyk
pull again, it should fail later now..
Peter.A.Silva
fixed 32 instead of 36.
pull and no -v needed... just the traceback is enough.
On Dec 21, 3:14 pm, Andrew Chalaturnyk <aacha...@gmail.com> wrote:
> btw. info is broken now if used by itself (no args) (and toprint is not
> initialized)
> this a different machine (the other is being formatted)
> ./drobom -v 8 -d /dev/sdg fwcheck
Andrew Chalaturnyk
Peter.A.Silva
I'd like to see the output of:
./drobom -d /dev/sdb info firmware
The problem is that the algorithm for comparing the current fw against
the vendor repository
has changed. That was a messy heuristic in the first place.
Detection of firmware for downloading
and uploading firmware are two separate (but obviously related!)
problems. Detection is a pain.
If you want to just test firmware loading, then just do:
wget http://www.drobo.com/support/updates/firmware/DroboPro_Firmware_v1-1-4.zip
peter@boule:~/drobo/drobo-utils/dpfw$ unzip
DroboPro_Firmware_v1-1-4.zip
Archive:
DroboPro_Firmware_v1-1-4.zip
inflating:
v1.1.4.tdz
peter@boule:~/drobo/drobo-utils/dpfw$
./drobom -d /dev/sdc fwload v1.1.4.tdz
that stands a chance of working... Drobo's are really good about
firmware safety.
It will either work, or it will not. Drobo's load the new version
into a secondary location,
and on boot they try the new, and fallback to the old. So the worst
thing that can happen is that
you boot your existing firmware.
That would be a very cool test.
> > drobo-talk+...@googlegroups.com<drobo-talk%2Bunsubscribe@googlegrou ps.com>
Andrew Chalaturnyk
To unsubscribe from this group, send email to drobo-talk+...@googlegroups.com.
Andrew Chalaturnyk
Peter Silva
Andrew Chalaturnyk
Andrew Chalaturnyk
Peter Silva
Andrew Chalaturnyk
Peter.A.Silva
otoh...
If I have a Drobo with 2 LUNS, I partition the first as EXT3, and the
second as EXT3,
then ./drobom info LUNS reports 'EXT3'. If I re-write the partitions
of the second LUN and create an NTFS partition and file system.
Drobo's bits say: No
On Dec 15, 7:03 aroot@pepino:~/drobo/drobo-utils# ./drobom set lunsize
1
/dev/sdf - Drobo disk pack 00% full - ([], 0)
You asked to set the lunsize to 1
WARNING: Ready to Destroy all you data. Continue? (y/n) y
set lunsize to 1 TiB
Done... Drobo is likely now rebooting.
In a few minutes, it will come back with the new LUN
size.
root@pepino:~/drobo/drobo-utils# ./drobom status
/dev/sdf:/dev/sdg - Drobo disk pack 00% full - ([], 0)
root@pepino:~/drobo/drobo-utils# ./drobom info luns
---------------------------------------------------------
Drobo Name: Drobo disk pack Devices: /dev/sdf:/dev/sdg
Time: Wed Dec 31 19:01:32 1969
---------------------------------------------------------
lun size (GB) used PTFmt FStype:
0 1099 0 No Partitions ['NO FORMAT']
1 1099 0 No Partitions ['NO FORMAT']
---------------------------------------------------------
root@pepino:~/drobo/drobo-utils# more /tmp/fmtscript
#!/bin/sh
parted -s /dev/sdf mklabel gpt
parted -s /dev/sdf mkpart ext2 0 100%
parted -s /dev/sdf print; sleep 5
mke2fs -j -i 262144 -L Drobo01 -m 0 -O sparse_super,^resize_inode /dev/
sdf1
parted -s /dev/sdg mklabel
gpt
parted -s /dev/sdg mkpart ext2 0
100%
parted -s /dev/sdg print; sleep
5
mke2fs -j -i 262144 -L Drobo01 -m 0 -O sparse_super,^resize_inode /dev/
sdg1
root@pepino:~/drobo/drobo-utils# sh -x /tmp/
fmtscript
+ parted -s /dev/sdf mklabel
gpt
+ parted -s /dev/sdf mkpart ext2 0
100%
+ parted -s /dev/sdf
print
Model: TRUSTED Mass Storage
(scsi)
Disk /dev/sdf:
1100GB
Sector size (logical/physical): 512B/
512B
Partition Table:
gpt
Number Start End Size File system Name Flags
1 17.4kB 1100GB 1100GB ext2
+ sleep 5
+ mke2fs -j -i 262144 -L Drobo01 -m 0 -O sparse_super,^resize_inode /
dev/sdf1
mke2fs 1.41.9 (22-
Aug-2009)
Filesystem
label=Drobo01
OS type:
Linux
Block size=4096
(log=2)
Fragment size=4096
(log=2)
4194304 inodes, 268435430
blocks
0 blocks (0.00%) reserved for the super
user
First data
block=0
8192 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
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 32 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
+ parted -s /dev/sdg mklabel gpt
+ parted -s /dev/sdg mkpart ext2 0 100%
+ parted -s /dev/sdg print
Model: TRUSTED Mass Storage (scsi)
Disk /dev/sdg: 1100GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 1100GB 1100GB ext2
+ sleep 5
+ mke2fs -j -i 262144 -L Drobo01 -m 0 -O sparse_super,^resize_inode /
dev/sdg1
mke2fs 1.41.9 (22-
Aug-2009)
Filesystem
label=Drobo01
OS type:
Linux
Block size=4096
(log=2)
Fragment size=4096
(log=2)
4194304 inodes, 268435430
blocks
0 blocks (0.00%) reserved for the super
user
First data
block=0
8192 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
Writing inode tables: done
Creating journal (32768 blocks):
done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
root@pepino:~/drobo/drobo-utils#
root@pepino:~/drobo/drobo-utils# ./drobom info luns
---------------------------------------------------------
Drobo Name: Drobo disk pack Devices: /dev/sdf:/dev/sdg
Time: Wed Dec 31 19:16:35 1969
---------------------------------------------------------
lun size (GB) used PTFmt FStype:
0 1099 2 GPT ['EXT3']
1 1099 0 GPT ['EXT3']
---------------------------------------------------------
root@pepino:~/drobo/drobo-utils#
root@pepino:~/drobo/drobo-utils# parted -s /dev/sdg mklabel
gpt
root@pepino:~/drobo/drobo-utils# parted -s /dev/sdg mkpart ntfs 0
100%
root@pepino:~/drobo/drobo-utils# parted -s /dev/sdg print; sleep
5
M
Peter.A.Silva
finger problem triggerred early send... continuing last post:
root@pepino:~/drobo/drobo-utils# mkntfs -f /dev/sdg1
Cluster size has been automatically set to 4096 bytes.
Creating NTFS volume structures.
mkntfs completed successfully. Have a nice day.
root@pepino:~/drobo/drobo-utils#
root@pepino:~/drobo/drobo-utils#
root@pepino:~/drobo/drobo-utils# ./drobom info luns
---------------------------------------------------------
Drobo Name: Drobo disk pack Devices: /dev/sdf:/dev/sdg
Time: Wed Dec 31 19:17:42 1969
---------------------------------------------------------
lun size (GB) used PTFmt FStype:
0 1099 2 GPT ['NO FORMAT']
1 1099 0 GPT ['NO FORMAT']
---------------------------------------------------------
root@pepino:~/drobo/drobo-utils#
So /dev/sdf1 has an ext3, /dev/sdg1 has an NTFS, Drobo reports NO
FORMAT... hmm...
Elliot
root@clutch:~/drobom-dev/drobo-utils# ./drobom info luns
---------------------------------------------------------
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
---------------------------------------------------------
lun size (GB) used PTFmt FStype:
1 2199 0 GPT ['EXT3']
2 2199 0 GPT ['EXT3']
---------------------------------------------------------
Andrew Chalaturnyk
Andrew Chalaturnyk
btw: is every one w/ iscsi using open-iscsi? Are you all using the settings posted by http://www.ezkayak.com/index.php/DroboPro,_iSCSI_and_Linux
Elliot
btw: is every one w/ iscsi using open-iscsi? Are you all using the settings posted by http://www.ezkayak.com/index.php/DroboPro,_iSCSI_and_LinuxIf not, what works for you?
Peter Silva
ElliotA
Is there an easy way to reboot, or do I have to do a shutdown and then
try and reconnect?
root@clutch:~/drobom-dev/drobo-utils# ./drobom status
/dev/sdc:/dev/sdd:/dev/sde /drobo/1:/drobo/2:/drobo/3 DroboPro 27%
full - (['New firmware installed'], 0)
On Dec 21, 6:40 pm, "Peter.A.Silva" <informa...@gmail.com> wrote:
> I'd like to see the output of:
>
> ./drobom -d /dev/sdb info firmware
>
> The problem is that the algorithm for comparing the current fw against
> the vendor repository
> has changed. That was a messy heuristic in the first place.
> Detection of firmware for downloading
> and uploading firmware are two separate (but obviously related!)
> problems. Detection is a pain.
>
> If you want to just test firmware loading, then just do:
>
> wgethttp://www.drobo.com/support/updates/firmware/DroboPro_Firmware_v1-1-...
Peter Silva
To unsubscribe from this group, send email to drobo-talk+...@googlegroups.com.
Peter Silva
Elliot
Thanks!
Peter.A.Silva
if you git pull again, there is a new info option...
./drobom info scsi
if the firmware version picking doesn't work, then it is likely
because of the hardware version
reported by this new option. would need a copy/paste of output (no -v
needed.)
I think the hardware revision on a pro is 2.0
mine (v1) is like so:
peter@pepino:~/drobo/drobo-utils$ sudo ./drobom info scsi
---------------------------------------------------------
Drobo Name: Drobo disk pack Devices: /dev/sdf:/dev/sdg
Time: Thu Jan 1 06:34:07 1970
---------------------------------------------------------
SCSI emulation information:
Vendor: TRUSTED Model: Mass Storage Revision: 1.00
/dev/sdf: bus=scsi12 channel=0 id=0 lun=0 (vendor=TRUSTED ,
version=30527)
/dev/sdg: bus=scsi12 channel=0 id=0 lun=1 (vendor=TRUSTED ,
version=30527)
---------------------------------------------------------
peter@pepino:~/drobo/drobo-utils$
ElliotA
root@clutch:~/drobom-dev/drobo-utils# ./drobom info scsi
---------------------------------------------------------
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
Time: Wed Dec 23 08:25:41 2009
---------------------------------------------------------
SCSI emulation information:
uh, oh... scsi inquire returned 36, bytes instead of 76 expected.
Vendor: DROBO Model: DroboPro Revision: 1.00
Traceback (most recent call last):
File "./drobom", line 392, in <module>
info(d,args[1].split(','))
File "./drobom", line 217, in info
eval( "print" + c + "(d)" )
File "<string>", line 1, in <module>
File "./drobom", line 155, in printscsi
version = dio.version()
File "/root/drobom-dev/drobo-utils/DroboIOctl.py", line 99, in
version
num=struct.unpack("l",k)
File "/usr/lib/python2.5/struct.py", line 87, in unpack
return o.unpack(s)
struct.error: unpack requires a string argument of length 4
root@clutch:~/drobom-dev/drobo-utils#
Peter Silva
Peter.A.Silva
Thanks everyone for their testing resources. This new stable version
is far better than
what was there. I think the PRO works ok. Drobo S is still a
worry. Please try it out!
Elliot
Thanks for the great work. Here's a dump, plus a df that shows usage.
root@clutch:~/drobom-dev/drobo-utils# ./drobom info
---------------------------------------------------------
Drobo Name: DroboPro Devices: /dev/sdc:/dev/sdd:/dev/sde
Time: Sun Dec 27 10:07:36 2009
---------------------------------------------------------
Configuration maxima: slots: 8, luns: 16, lunsize: 36028799 TB
Capacity (in GB): used: 2000, free: 3976, total: 5977
protocol version: 0.11
SCSI emulation information:
uh, oh... scsi inquire returned 36, bytes instead of 76 expected.
Vendor: DROBO Model: DroboPro Revision: 1.00
/dev/sdc: bus=scsi10 channel=0 id=0 lun=0 (vendor=DROBO , version=30527)
/dev/sdd: bus=scsi10 channel=0 id=0 lun=1 (vendor=DROBO , version=30527)
/dev/sde: bus=scsi10 channel=0 id=0 lun=2 (vendor=DROBO , version=30527)
query slotinfo result: number of slots: 8
slot GB Model Status
0 2000 Hitachi HDS722020ALA330 green
1 2000 Hitachi HDS722020ALA330 green
2 2000 Hitachi HDS722020ALA330 green
3 2000 Hitachi HDS722020ALA330 green
4 0 gray
5 0 gray
6 0 gray
7 0 gray
Firmware: 1.1.4
Revision: 2.41 ( 24969 ) built: Nov 25 2009,21:47:33
Features: NO_AUTO_REBOOT,NO_FAT32_FORMAT,USED_CAPACITY_FROM_HOST,DISKPACKSTATUS,ENCRYPT_NOHEADER,CMD_STATUS_QUERIABLE,VARIABLE_LUN_SIZE_1_16,PARTITION_LUN_GPT_MBR,FAT32_FORMAT_VOLNAME,SUPPORTS_NEW_LUNINFO2,feature x0800,LUN_MANAGEMENT,feature x2000 ,SUPPORTS_OPTIONS2,SUPPORTS_SHUTDOWN,leftovers (0x20000)
/dev/sdc:/dev/sdd:/dev/sde /drobo/1:/drobo/2:/drobo/3 DroboPro 33% full - ([], 0)
query options result:
UseStaticIPAddress True
UseManualVolumeManagement True
YellowThreshold 85
SpinDownDelayMinutes 15
RedThreshold 95
SpinDownDelay True
NetMask 255.255.0.0
DualDiskRedundancy False
IPAddress 169.254.1.1
lun size (GB) used PTFmt FStype:
0 2199 2000 GPT ['EXT3']
1 2199 0 GPT ['EXT3']
2 2199 0 GPT ['EXT3']
---------------------------------------------------------
root@clutch:~/drobom-dev/drobo-utils# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdb2 70G 4.4G 62G 7% /
varrun 1014M 60K 1014M 1% /var/run
varlock 1014M 4.0K 1014M 1% /var/lock
udev 1014M 60K 1014M 1% /dev
devshm 1014M 0 1014M 0% /dev/shm
/dev/sda1 3.4T 3.2T 29G 100% /raid
/dev/sdc1 2.0T 607G 1.5T 30% /drobo/1
/dev/sdd1 2.0T 995G 1.1T 49% /drobo/2
/dev/sde1 2.0T 259G 1.8T 13% /drobo/3
Peter Silva
capacity is listed as 5977... close enough for me...
then used data in the three file systems from
the df report is 1861 G's, which ignores fs overhead,
lun labels (partition tables) boot blocks, superblocks, inodes, etc... x 3 for 3 luns. Drobo reports 2000
as usage. sounds OK to me.
2000/5977 = 33.4%.
drobom status reports 33% usage.
So, the overall figures are correct.
I guess your point is that all the used space is
attributed to LUN0, and the others appear empty.
I gather that Drobo allocates space as a pool for all LUNS, it might not report on each LUN individually.
This probably reflects what the Drobo is supplying.
hmm... maybe i should not report that value that way...
Elliot
Thanks again.
-Elliot
Peter Silva
I reproduced it myself, and I posted a query in the forums,
http://www.drobospace.com/forums/showthread.php?tid=772
see what comes of it.
docfruitbat
Just wanted to report that the latest pull of drobo-utils from git
(today) is much improved, though I seem to have to specify '-s DROBO'
for it to properly identify the devices (anyway of making it properly
auto-detect the drobo?). Without '-s' drobom seems to either A) think
my SATA drive (/dev/sda) is a drobo drive, or B) says theres 'No
Drobos discovered'. It's inconsistent in this, and I can't seem to
make happen at will (and It might be related to the specific info
commands I'm using too...not sure). But, as long as I use '-s DROBO'
all is well. Just to reiterate, I'm using iSCSI attached devices.
I did have one question concerning the 'info luns' output. It seems
to attribute all of the 'used' storage to the first lun rather than
how much is actually used by each lun. Eg:
root@gremlin:/# drobom -s DROBO -v 1 info luns
---------------------------------------------------------
Drobo Name: DroboPro Devices: /dev/sdb:/dev/sdc:/dev/sdd:/dev/sde:/
dev/sdf:/dev/sdg:/dev/sdh:/dev/sdi
Time: Fri Jan 22 12:45:34 2010
---------------------------------------------------------
lun size (GB) used PTFmt FStype:
1 2199 0 GPT ['EXT3']
2 2199 0 GPT ['EXT3']
4 2199 0 GPT ['EXT3']
5 2199 0 GPT ['EXT3']
6 2199 0 GPT ['EXT3']
7 2199 0 GPT ['EXT3']
---------------------------------------------------------
Yet, my actual allocations on each partition is:
root@gremlin:/# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb1 2146293576 4234476 2142059100 1% /mnt/drobo/
home
/dev/sdc1 2146293576 927272 2145366304 1% /mnt/drobo/
mail
/dev/sdd1 2146293576 22829060 2123464516 2% /mnt/drobo/
archive
/dev/sde1 2146293576 6537596 2139755980 1% /mnt/drobo/
work
/dev/sdf1 2146293576 330052 2145963524 1% /mnt/drobo/
db
/dev/sdg1 2146293576 46966924 2099326652 3% /mnt/drobo/
web
/dev/sdh1 2146293576 42901504 2103392072 2% /mnt/drobo/
media1
/dev/sdi1 2146293576 5464848 2140828728 1% /mnt/drobo/
media2
Is this just a reporting issue with drobom or is this some indication
that storage is really only being allocated to the first lun? Should
I be concerned? I haven't run into any problems ... yet (knock on
wood :-)
Anyway, want to say 'Thanks' again for drobo-utils and keep up the
good work!
On Dec 20 2009, 6:54 pm, "Peter.A.Silva" <informa...@gmail.com> wrote:
> thanks for your patience... please pull and try again...
>
> On Dec 20, 9:25 pm, docfruitbat <doc...@fruitbat.org> wrote:
>
> > Hmm...pulled latest from git just now, but still no dice:
>
> > root@gremlin:~# drobom -v 16 info luns
> > examining: /dev/sda
> > id: (0, 0, 0, 0, 'ATA ')
> > found a Drobo
> > appending new lundevs to devices: []
> > examining: /dev/sdb
> > id: (0, 0, 0, 0, 'DROBO ')
> > found a Drobo
> > appending to lundevs...
> > examining: /dev/sdc
> > id: (0, 0, 0, 0, 'DROBO ')
> > found a Drobo
> > appending to lundevs...
> > examining: /dev/sdd
> > id: (0, 0, 0, 0, 'DROBO ')
> > found a Drobo
> > appending to lundevs...
> > examining: /dev/sde
> > id: (0, 0, 0, 0, 'DROBO ')
> > found a Drobo
> > appending to lundevs...
> > examining: /dev/sdf
> > id: (0, 0, 0, 0, 'DROBO ')
> > found a Drobo
> > appending to lundevs...
> > examining: /dev/sdg
> > id: (0, 0, 0, 0, 'DROBO ')
> > found a Drobo
> > appending to lundevs...
> > examining: /dev/sdh
> > id: (0, 0, 0, 0, 'DROBO ')
> > found a Drobo
> > appending to lundevs...
> > examining: /dev/sdi
> > id: (0, 0, 0, 0, 'DROBO ')
> > found a Drobo
> > appending to lundevs...
> > returning list: [['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/
> > dev/sde', '/dev/sdf', '/dev/sdg', '/dev/sdh', '/dev/sdi']]
> > trying: ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde',
> > '/dev/sdf', '/dev/sdg', '/dev/sdh', '/dev/sdi']
> > cfg: (91, 0, 9846168977766629376L)
> > settings: (1526726656L, 8, 'OBO DroboPro')
> > /dev/sda fw[6] is not armmarvell.
> > No Drobos discovered
>
> > Thoughts?
>
> > On Dec 19, 1:37 am, "Peter.A.Silva" <informa...@gmail.com> wrote:
>
> > > everybody git pull tonight...
>
> > > i futzed with the luninfo stuff, and the detection. might be all ok
> > > now.
> > > would appreciate seeing
>
> > > ./drobom info luns
>
> > > fingers crossed.
Peter Silva
--