drobo-utils-devel Mailing List for drobo-utils
Brought to you by:
peter_silva
You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(4) |
Jul
(11) |
Aug
(19) |
Sep
(12) |
Oct
(7) |
Nov
(23) |
Dec
(27) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
(46) |
Feb
(18) |
Mar
|
Apr
(8) |
May
(41) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
(2) |
Mar
(7) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Kasper Schramm-H. <kbh...@gm...> - 2019-01-09 13:25:59
|
I'm trying to install drobo-utils on Ubuntu. I've installed; drobo-utils and python-qt4. I've downloaded drobo-utils_0.6.2.2_all.deb. Now I'm trying this; sudo apt install ./drobo-utils_0.6.2.2_all.deb But get this message; Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'drobo-utils' instead of './drobo-utils_0.6.2.2_all.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: drobo-utils : Depends: python-support (>= 0.90.0) but it is not installable E: Unable to correct problems, you have held broken packages. If you haven't guessed already, I'm new to Linux/Ubuntu... ;-) Can anyone help? :-) Thanks! |
From: Marc - A. D. [ A. | W. G. ] <ma...@wo...> - 2010-03-19 13:39:42
|
[this time with list on mailto] Hello Peter, Am Donnerstag, den 18.03.2010, 19:44 -0400 schrieb Peter Silva: > I tested on an Original Drobo (Gen 1), which doesn't support > OPTIONS2... thanks for your tests. :o) > so we need someone with a Gen2, a Pro & an "S" to verify... > sigh... That would be nice. I'm unsure if the fetch of all fields is a good thing to do and to just apply it to the git branch because i can't tell if all currently supported drobo models with OPTIONS2 will allow us to fetch the whole bunch of data from the feature-flags page (which would be grate if it would just work becouse it is simpler code to maintain). Would be nice if we could fetch data from the page beginning on an offset from the start of the page. This would make it less problematic for models which couldn't give the full lenght of informations. The next thing is that i dont know if the MTU value for the first NIC on the DroboPro is supported. It doesn't show the field on the application-prints in the manual... Is there a way to get a sorted output of the feature-falgs with drobom? First-in-first-out would be great. > Where did you get the DUALNIC support & other FEATURE flag values > from? I found a "drobom info firmware" output of a DroboPro in the drobo-talk archives over at google and did an educated guess about what the feature flags could be representing. DroboPro lists x20000 as leftover (and is the first drobo with iscsi). DroboElite lists x40000 and x20000 (and is the first with second nic). Couldn't find any feature flags from the remaining drobo versions in the archives, so my guess might be false but i don't think so because the feature flags were the only flags that got added to this two models and the new functionality on this two drobos must be related to the newly added flags. I posted more details to the bug-record... Marc > peter@pepino:~/drobo-utils$ sudo ./drobom info > --------------------------------------------------------- > Drobo Name: Drobo disk pack Devices: /dev/sdf > Time: Tue Mar 16 12:07:09 2010 > --------------------------------------------------------- > Configuration maxima: slots: 4, luns: 16, lunsize: 8 TB > Capacity (in GB): used: 9, free: 1473, total: 1482 > protocol version: 0.11 > SCSI emulation information: > Vendor: TRUSTED Model: Mass Storage Revision: 1.00 > /dev/sdf: bus=scsi5 channel=0 id=0 lun=0 (vendor=TRUSTED , > version=30527) > query slotinfo result: number of slots: 4 > slot GB Model Status > 0 500 ST3500830AS green > 1 750 WDC WD7500AAKS-00RBA0 green > 2 500 WDC WD5000AAKS-00C8A0 green > 3 500 WDC WD5000AAKS-00C8A0 green > Firmware: 1.3.5 > Revision: 1.252 ( 21110 ) built: Aug 31 2009,18:12:03 > 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_DROBOSHARE,SUPPORTS_NEW_LUNINFO2,feature x0800,feature x2000 > /dev/sdf - Drobo disk pack 00% full - ([], 0) > RedThreshold 95 > YellowThreshold 85 > lun size (GB) used PTFmt FStype: > 0 8796 9 GPT ['EXT3'] > --------------------------------------------------------- > peter@pepino:~/drobo-utils$ > > On Tue, Mar 16, 2010 at 10:14 AM, Marc - A. Dahlhaus [ Administration > | Westermann GmbH ] <ma...@wo...> wrote: > Hello, > > > here is a very early version of option fetch support for the > dorbo > elite. > > Background information is located inside the bug report > #2967328: > > https://sourceforge.net/tracker/?func=detail&aid=2967328&group_id=222830&atid=1056841 > > Can someone provide me with the outputs of 'drobom info > firmware' from an drobo s and a normal drobo with up2date > firmware in place? > I need them to verify that my asumptions of what info the > feature-flags represent are correct. > > What do you think of it? > > I'll try to work on the option set support over the nexte few > days. > > > Marc |
From: Marc - A. D. [ A. | W. G. ] <ma...@wo...> - 2010-03-19 13:38:38
|
[this time with list on mailto] Hello Peter, Am Donnerstag, den 18.03.2010, 19:12 -0400 schrieb Peter Silva: > > > The patch looks like a great first shot! thanks. :o) > Do you want commit access? I'll try to setup a system on which i can use the whole feature-set of git over the next few days. > I think it will be more likely that others test the patch if we just > apply it to git mainline, so that people will get it via a normal > pull. But If I do that, I think you need to be able to patch further, > quickly, if someone reports an issue. > I'm not to worried about breakage, because folks are supposed to use > the QA'd stable versions normally. I need to shave off some edges a bit before we push it out. (more in the next mail... > On Tue, Mar 16, 2010 at 10:14 AM, Marc - A. Dahlhaus [ Administration > | Westermann GmbH ] <ma...@wo...> wrote: > Hello, > > > here is a very early version of option fetch support for the > dorbo > elite. > > Background information is located inside the bug report > #2967328: > > https://sourceforge.net/tracker/?func=detail&aid=2967328&group_id=222830&atid=1056841 > > Can someone provide me with the outputs of 'drobom info > firmware' from an drobo s and a normal drobo with up2date > firmware in place? > I need them to verify that my asumptions of what info the > feature-flags represent are correct. > > What do you think of it? > > I'll try to work on the option set support over the nexte few > days. > > > Marc > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find > bugs > proactively, and fine-tune applications for parallel > performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Drobo-utils-devel mailing list > Dro...@li... > https://lists.sourceforge.net/lists/listinfo/drobo-utils-devel > > > |
From: Peter S. <Pet...@gm...> - 2010-03-18 23:45:01
|
I tested on an Original Drobo (Gen 1), which doesn't support OPTIONS2... so we need someone with a Gen2, a Pro & an "S" to verify... sigh... Where did you get the DUALNIC support & other FEATURE flag values from? peter@pepino:~/drobo-utils$ sudo ./drobom info --------------------------------------------------------- Drobo Name: Drobo disk pack Devices: /dev/sdf Time: Tue Mar 16 12:07:09 2010 --------------------------------------------------------- Configuration maxima: slots: 4, luns: 16, lunsize: 8 TB Capacity (in GB): used: 9, free: 1473, total: 1482 protocol version: 0.11 SCSI emulation information: Vendor: TRUSTED Model: Mass Storage Revision: 1.00 /dev/sdf: bus=scsi5 channel=0 id=0 lun=0 (vendor=TRUSTED , version=30527) query slotinfo result: number of slots: 4 slot GB Model Status 0 500 ST3500830AS green 1 750 WDC WD7500AAKS-00RBA0 green 2 500 WDC WD5000AAKS-00C8A0 green 3 500 WDC WD5000AAKS-00C8A0 green Firmware: 1.3.5 Revision: 1.252 ( 21110 ) built: Aug 31 2009,18:12:03 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_DROBOSHARE,SUPPORTS_NEW_LUNINFO2,feature x0800,feature x2000 /dev/sdf - Drobo disk pack 00% full - ([], 0) RedThreshold 95 YellowThreshold 85 lun size (GB) used PTFmt FStype: 0 8796 9 GPT ['EXT3'] --------------------------------------------------------- peter@pepino:~/drobo-utils$ On Tue, Mar 16, 2010 at 10:14 AM, Marc - A. Dahlhaus [ Administration | Westermann GmbH ] <ma...@wo...> wrote: > Hello, > > > here is a very early version of option fetch support for the dorbo > elite. > > Background information is located inside the bug report #2967328: > > > https://sourceforge.net/tracker/?func=detail&aid=2967328&group_id=222830&atid=1056841 > > Can someone provide me with the outputs of 'drobom info firmware' from an > drobo s and a normal drobo with up2date firmware in place? > I need them to verify that my asumptions of what info the feature-flags > represent are correct. > > What do you think of it? > > I'll try to work on the option set support over the nexte few days. > > > Marc > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Drobo-utils-devel mailing list > Dro...@li... > https://lists.sourceforge.net/lists/listinfo/drobo-utils-devel > > |
From: Marc - A. D. [ A. | W. G. ] <ma...@wo...> - 2010-03-16 14:15:08
|
Hello, here is a very early version of option fetch support for the dorbo elite. Background information is located inside the bug report #2967328: https://sourceforge.net/tracker/?func=detail&aid=2967328&group_id=222830&atid=1056841 Can someone provide me with the outputs of 'drobom info firmware' from an drobo s and a normal drobo with up2date firmware in place? I need them to verify that my asumptions of what info the feature-flags represent are correct. What do you think of it? I'll try to work on the option set support over the nexte few days. Marc |
From: Marc - A. D. [ A. | W. G. ] <ma...@wo...> - 2010-03-03 16:01:26
|
Hello Devs, we have a DroboElite deployed here and configured it with the windows software (and break our strict rule of not using windows in our datacenter, doh! ;oP). We installed drobo-utils 0.6.2.2 on our bacula-backup-server which is using the Elite as storage backend. Looks like "drobom info options" doesn't work on the elite right now (output below). I can help in getting support for the device and test things if someone could guide me a little bit in what to do :o) thanks, Marc [root@backup ~]# drobom info --------------------------------------------------------- Drobo Name: Backup I Devices: /dev/sdc Time: Wed Mar 3 17:27:58 2010 --------------------------------------------------------- Configuration maxima: slots: 8, luns: 0, lunsize: 36028814 TB Capacity (in GB): used: 0, free: 11916, total: 11916 protocol version: 0.11 SCSI emulation information: Vendor: Drobo Model: DroboElite Revision: 1.00 /dev/sdc: bus=scsi2 channel=0 id=0 lun=0 (vendor=Drobo , version=30527) query slotinfo result: number of slots: 8 slot GB Model Status 0 2000 ST32000542AS green 1 2000 ST32000542AS green 2 2000 ST32000542AS green 3 2000 ST32000542AS green 4 2000 ST32000542AS green 5 2000 ST32000542AS green 6 2000 ST32000542AS green 7 2000 ST32000542AS green Firmware: 1.0.1 Revision: 3.13 ( 25426 ) built: Dec 22 2009,18:43:18 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 (0x60000) /dev/sdc - Backup I 00% full - ([], 0) query options result: Traceback (most recent call last): File "/usr/bin/drobom", line 394, in <module> info(d,valid_print) File "/usr/bin/drobom", line 217, in info eval( "print" + c + "(d)" ) File "<string>", line 1, in <module> File "/usr/bin/drobom", line 190, in printoptions for i in options.keys(): AttributeError: 'NoneType' object has no attribute 'keys' |
From: <Sil...@ti...> - 2010-03-01 14:16:09
|
Hi, why calls the fmt script generated by drobom "mke2fs" with the option "-m 0"? I haven't found this in the examples to EXT3 on DRI sites. Is this necessary for proper work of Drobo with EXT3? And if not, can I change this later with tune2fs without any irritations on Drobo site? TIA, Silvio Wanka |
From: <Sil...@ti...> - 2010-03-01 11:48:05
|
inf...@gm... wrote On Behalf Of Peter Silva: > > the documentation is a little out of date. I tried 2.4 on my ubuntu > after an alarming bug report... > > https://sourceforge.net/tracker/?func=detail&aid=2944099&group_id=222830 > &atid=1056841 > > if you use 0.6.2.2, the latest stable version, it should work with > python2.4 in line mode at least. I haven't heard about anyone trying it > in GUI mode. Hi, first THX for your answer, but as I already wrote, the command line works with 2.4 (I use your last release) and Active Python 2.5 if I specify the device - although it tries always to access /dev/sda and gives gibberish infos to this device in the head ;-). Here with debug info's there you can see a "found a Drobo" after both MegaRAID devices: # drobom -v 16 -d /dev/sdc status examining: /dev/sda id: (0, 0, 2, 0, 'MegaRAID') found a Drobo appending new lundevs to devices: [] examining: /dev/sdb id: (0, 1, 2, 0, 'MegaRAID') found a Drobo appending new lundevs to devices: [['/dev/sda']] examining: /dev/sdc id: (2, 0, 0, 0, 'DROBO ') found a Drobo appending new lundevs to devices: [['/dev/sda'], ['/dev/sdb']] examining: /dev/sdd id: (2, 0, 0, 1, 'DROBO ') found a Drobo appending to lundevs... returning list: [['/dev/sda'], ['/dev/sdb'], ['/dev/sdc', '/dev/sdd']] trying: ['/dev/sda'] cfg: (0, 0, 1196268651020288) /dev/sda cfg[0] = 0, should >= 4. All Drobos have at least 4 slots trying: ['/dev/sdb'] cfg: (0, 0, 1196268651020288) /dev/sdb cfg[0] = 0, should >= 4. All Drobos have at least 4 slots trying: ['/dev/sdc', '/dev/sdd'] cfg: (8, 16, 36893496943512124928L) settings: (1267443503, 8, 'DroboPro') found [['/dev/sdc', '/dev/sdd']] cfg: (8, 16, 36893496943512124928L) settings: (1267443505, 8, 'DroboPro') /dev/sdc:/dev/sdd /srv/bakup/Drobo01:/srv/bakup/Drobo02 DroboPro 38% full - ([], 0) or without "-d" options: # drobom -v 16 status examining: /dev/sda id: (0, 0, 2, 0, 'MegaRAID') found a Drobo appending new lundevs to devices: [] examining: /dev/sdb id: (0, 1, 2, 0, 'MegaRAID') found a Drobo appending new lundevs to devices: [['/dev/sda']] examining: /dev/sdc id: (2, 0, 0, 0, 'DROBO ') found a Drobo appending new lundevs to devices: [['/dev/sda'], ['/dev/sdb']] examining: /dev/sdd id: (2, 0, 0, 1, 'DROBO ') found a Drobo appending to lundevs... returning list: [['/dev/sda'], ['/dev/sdb'], ['/dev/sdc', '/dev/sdd']] trying: ['/dev/sda'] cfg: (32, 0, 3035112197066133094400L) settings: (536870994, 8, 'OBO DroboPro') interesting, /dev/sda fw[6] is: trying: ['/dev/sdb'] cfg: (0, 0, 1196268651020288) /dev/sdb cfg[0] = 0, should >= 4. All Drobos have at least 4 slots trying: ['/dev/sdc', '/dev/sdd'] cfg: (8, 16, 36893496943512124928L) settings: (1267443716, 8, 'DroboPro') found [['/dev/sda'], ['/dev/sdc', '/dev/sdd']] cfg: (2, 102, 7344834101550354818048L) /dev/sda cfg[0] = 2, should >= 4. All Drobos have at least 4 slots Traceback (most recent call last): File "/usr/local/sbin/drobom", line 336, in <module> d=Drobo.Drobo(u,debug) File "/opt/ActivePython/2.5/lib/python2.5/site-packages/Drobo.py", line 308, in __init__ raise DroboException # Assert: All Drobo have 4 slots. Drobo.DroboExceptionProblem accessing a Drobo: Unknown BTW, we have tried to use ubuntu 9.10 and there it was not necessary to specify the device. Maybe a problem with Red Had and/or the older kernel. But ubunto can't be used in production (Dell Open Manage and Dell Firmware Patches are only supported for Red Hat and SuSE Ent.). But now again back to the GUI, the problem appears using: ActivePython 2.5.5.7 (ActiveState Software Inc.) based on Python 2.5.5 (r255:77872, Jan 31 2010, 15:31:52) [GCC 3.3.4 (pre 3.3.5 20040809)] on linux2 sip-4.10 (installed using python2.5 configure.py; make install) PyQt-x11-gpl-4.7 (installed using python2.5 configure.py; make install) drobo-utils-0.6.2.2 (installed using python2.5 setup.py install) Here the call with debug infos: # drobom -v 16 -d /dev/sdc view examining: /dev/sda id: (0, 0, 2, 0, 'MegaRAID') found a Drobo appending new lundevs to devices: [] examining: /dev/sdb id: (0, 1, 2, 0, 'MegaRAID') found a Drobo appending new lundevs to devices: [['/dev/sda']] examining: /dev/sdc id: (2, 0, 0, 0, 'DROBO ') found a Drobo appending new lundevs to devices: [['/dev/sda'], ['/dev/sdb']] examining: /dev/sdd id: (2, 0, 0, 1, 'DROBO ') found a Drobo appending to lundevs... returning list: [['/dev/sda'], ['/dev/sdb'], ['/dev/sdc', '/dev/sdd']] trying: ['/dev/sda'] cfg: (32, 0, 3035112197066133094400L) settings: (0, 8, '') interesting, /dev/sda fw[6] is: trying: ['/dev/sdb'] cfg: (0, 0, 0) /dev/sdb cfg[0] = 0, should >= 4. All Drobos have at least 4 slots trying: ['/dev/sdc', '/dev/sdd'] cfg: (8, 16, 36893496943512124928L) settings: (1267444963, 8, 'DroboPro') found [['/dev/sdc', '/dev/sdd']] cfg: (8, 16, 36893496943512124928L) settings: (1267444966, 8, 'DroboPro') Traceback (most recent call last): File "/usr/local/sbin/drobom", line 451, in <module> tb = DroboGUI(d) File "/opt/ActivePython/2.5/lib/python2.5/site-packages/DroboGUI.py", line 774, in __init__ self.__initDeviceTab() File "/opt/ActivePython/2.5/lib/python2.5/site-packages/DroboGUI.py", line 255, in __initDeviceTab devtablayout.setVerticalSpacing(4) AttributeError: 'QGridLayout' object has no attribute 'setVerticalSpacing' Should I create some tickets for these problems? TIA, Silvio Wanka > On Sat, Feb 27, 2010 at 2:22 PM, Silvio Wanka <Sil...@ti...> wrote: >> Hi guys, >> >> I try to use a DroboPro via iSCSI at a Dell server with CentOS 5.4 64bit >> installed. >> >> Because there was a note in the ReadMe of the drobo utils, that Python >> 2.4 is not >> proper supported (development and test only on 2.5 and 2.6) I have >> installed >> additionally ActivePython 2.5 and PyQT4 into the ActivePython tree. >> >> There is one problem independent if I use the 2.4 python of the >> distribution or >> the 2.5 release: >> >> drobom is not able to detect the Drobo, it always tries to use /dev/sda, >> but this >> is an real SCSI RAID 1. >> >> [root@ centos5.4]# drobom status >> interesting, /dev/sda fw[6] is: Traceback (most recent >> call last): >> File "/usr/local/sbin/drobom", line 336, in <module> >> d=Drobo.Drobo(u,debug) >> File "/opt/ActivePython/2.5/lib/python2.5/site- >> packages/Drobo.py", line 308, in __init__ >> raise DroboException # Assert: All Drobo have 4 slots. >> Drobo.DroboExceptionProblem accessing a Drobo: Unknown >> >> >> The real Drobo devices are: >> >> [root@ centos5.4]# drobom list >> interesting, /dev/sda fw[6] is: ???? >> /dev/sda /dev/sdc:/dev/sdd >> >> The special characters looks really so in xterm ;-) >> This is all only cosmetic things because the "-d" option is a proper >> workaround, but >> there must be an incapability between droboview and the last PyQT4 >> release or something >> else (AttributeError: 'QGridLayout' object has no attribute >> 'setVerticalSpacing'): >> >> [root@centos5.4]# droboview /dev/sdc >> interesting, /dev/sda fw[6] is: >> Traceback (most recent call last): >> File "/usr/local/sbin/drobom", line 336, in <module> >> d=Drobo.Drobo(u,debug) >> File "/opt/ActivePython/2.5/lib/python2.5/site- >> packages/Drobo.py", line 308, in __init__ >> raise DroboException # Assert: All Drobo have 4 slots. >> Drobo.DroboExceptionProblem accessing a Drobo: Unknown >> [root@us000622 tmp]# droboview -d /dev/sdc >> interesting, /dev/sda fw[6] is: Ø•r >> Traceback (most recent call last): >> File "/usr/local/sbin/drobom", line 451, in <module> >> tb = DroboGUI(d) >> File "/opt/ActivePython/2.5/lib/python2.5/site- >> packages/DroboGUI.py", line 774, in __init__ >> self.__initDeviceTab() >> File "/opt/ActivePython/2.5/lib/python2.5/site- >> packages/DroboGUI.py", line 255, in __initDeviceTab >> devtablayout.setVerticalSpacing(4) >> AttributeError: 'QGridLayout' object has no attribute >> 'setVerticalSpacing' >> >> I'm really experiences with perl, csh, ksh, vbs etc but Python looks for >> me totally different, so it >> is at the moment no choice for me to find the problems by myself. >> >> TIA, Silvio Wanka >> >> BTW, there is perhaps an mistake in your documentation (ReadMe, >> index.html etc): >> >> - Email - The developers list, one of us will surely answer. >> >> is linked to dro...@so... >> but I got from our mail gateway: >> >> dro...@so... >> #< #5.0.0 smtp; 550 unknown user> #SMTP# |
From: Peter S. <Pet...@gm...> - 2010-02-28 02:43:46
|
the documentation is a little out of date. I tried 2.4 on my ubuntu after an alarming bug report... https://sourceforge.net/tracker/?func=detail&aid=2944099&group_id=222830&atid=1056841 if you use 0.6.2.2, the latest stable version, it should work with python2.4 in line mode at least. I haven't heard about anyone trying it in GUI mode. On Sat, Feb 27, 2010 at 2:22 PM, Silvio Wanka <Sil...@ti...>wrote: > Hi guys, > > I try to use a DroboPro via iSCSI at a Dell server with CentOS 5.4 64bit > installed. > > Because there was a note in the ReadMe of the drobo utils, that Python 2.4 > is not > proper supported (development and test only on 2.5 and 2.6) I have > installed > additionally ActivePython 2.5 and PyQT4 into the ActivePython tree. > > There is one problem independent if I use the 2.4 python of the > distribution or > the 2.5 release: > > drobom is not able to detect the Drobo, it always tries to use /dev/sda, > but this > is an real SCSI RAID 1. > > [root@ centos5.4]# drobom status > interesting, /dev/sda fw[6] is: Traceback (most recent call > last): > File "/usr/local/sbin/drobom", line 336, in <module> > d=Drobo.Drobo(u,debug) > File "/opt/ActivePython/2.5/lib/python2.5/site-packages/Drobo.py", > line 308, in __init__ > raise DroboException # Assert: All Drobo have 4 slots. > Drobo.DroboExceptionProblem accessing a Drobo: Unknown > > > The real Drobo devices are: > > [root@ centos5.4]# drobom list > interesting, /dev/sda fw[6] is: ���� > /dev/sda /dev/sdc:/dev/sdd > > The special characters looks really so in xterm ;-) > This is all only cosmetic things because the "-d" option is a proper > workaround, but > there must be an incapability between droboview and the last PyQT4 release > or something > else (AttributeError: 'QGridLayout' object has no attribute > 'setVerticalSpacing'): > > [root@centos5.4]# droboview /dev/sdc > interesting, /dev/sda fw[6] is: > Traceback (most recent call last): > File "/usr/local/sbin/drobom", line 336, in <module> > d=Drobo.Drobo(u,debug) > File "/opt/ActivePython/2.5/lib/python2.5/site-packages/Drobo.py", > line 308, in __init__ > raise DroboException # Assert: All Drobo have 4 slots. > Drobo.DroboExceptionProblem accessing a Drobo: Unknown > [root@us000622 tmp]# droboview -d /dev/sdc > interesting, /dev/sda fw[6] is: Ø•r > Traceback (most recent call last): > File "/usr/local/sbin/drobom", line 451, in <module> > tb = DroboGUI(d) > File > "/opt/ActivePython/2.5/lib/python2.5/site-packages/DroboGUI.py", line 774, > in __init__ > self.__initDeviceTab() > File > "/opt/ActivePython/2.5/lib/python2.5/site-packages/DroboGUI.py", line 255, > in __initDeviceTab > devtablayout.setVerticalSpacing(4) > AttributeError: 'QGridLayout' object has no attribute > 'setVerticalSpacing' > > I'm really experiences with perl, csh, ksh, vbs etc but Python looks for me > totally different, so it > is at the moment no choice for me to find the problems by myself. > > TIA, Silvio Wanka > > BTW, there is perhaps an mistake in your documentation (ReadMe, index.html > etc): > > - Email - The developers list, one of us will surely answer. > > is linked to dro...@so... > but I got from our mail gateway: > > dro...@so... > #< #5.0.0 smtp; 550 unknown user> #SMTP# > > > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Drobo-utils-devel mailing list > Dro...@li... > https://lists.sourceforge.net/lists/listinfo/drobo-utils-devel > > |
From: Silvio W. <Sil...@ti...> - 2010-02-27 19:38:20
|
Hi guys, I try to use a DroboPro via iSCSI at a Dell server with CentOS 5.4 64bit installed. Because there was a note in the ReadMe of the drobo utils, that Python 2.4 is not proper supported (development and test only on 2.5 and 2.6) I have installed additionally ActivePython 2.5 and PyQT4 into the ActivePython tree. There is one problem independent if I use the 2.4 python of the distribution or the 2.5 release: drobom is not able to detect the Drobo, it always tries to use /dev/sda, but this is an real SCSI RAID 1. [root@ centos5.4]# drobom status interesting, /dev/sda fw[6] is: Traceback (most recent call last): File "/usr/local/sbin/drobom", line 336, in <module> d=Drobo.Drobo(u,debug) File "/opt/ActivePython/2.5/lib/python2.5/site-packages/Drobo.py", line 308, in __init__ raise DroboException # Assert: All Drobo have 4 slots. Drobo.DroboExceptionProblem accessing a Drobo: Unknown The real Drobo devices are: [root@ centos5.4]# drobom list interesting, /dev/sda fw[6] is: ���� /dev/sda /dev/sdc:/dev/sdd The special characters looks really so in xterm ;-) This is all only cosmetic things because the "-d" option is a proper workaround, but there must be an incapability between droboview and the last PyQT4 release or something else (AttributeError: 'QGridLayout' object has no attribute 'setVerticalSpacing'): [root@centos5.4]# droboview /dev/sdc interesting, /dev/sda fw[6] is: Traceback (most recent call last): File "/usr/local/sbin/drobom", line 336, in <module> d=Drobo.Drobo(u,debug) File "/opt/ActivePython/2.5/lib/python2.5/site-packages/Drobo.py", line 308, in __init__ raise DroboException # Assert: All Drobo have 4 slots. Drobo.DroboExceptionProblem accessing a Drobo: Unknown [root@us000622 tmp]# droboview -d /dev/sdc interesting, /dev/sda fw[6] is: ؕr Traceback (most recent call last): File "/usr/local/sbin/drobom", line 451, in <module> tb = DroboGUI(d) File "/opt/ActivePython/2.5/lib/python2.5/site-packages/DroboGUI.py", line 774, in __init__ self.__initDeviceTab() File "/opt/ActivePython/2.5/lib/python2.5/site-packages/DroboGUI.py", line 255, in __initDeviceTab devtablayout.setVerticalSpacing(4) AttributeError: 'QGridLayout' object has no attribute 'setVerticalSpacing' I'm really experiences with perl, csh, ksh, vbs etc but Python looks for me totally different, so it is at the moment no choice for me to find the problems by myself. TIA, Silvio Wanka BTW, there is perhaps an mistake in your documentation (ReadMe, index.html etc): - Email - The developers list, one of us will surely answer. is linked to dro...@so... but I got from our mail gateway: dro...@so... #< #5.0.0 smtp; 550 unknown user> #SMTP# |
From: Peter S. <Pet...@gm...> - 2009-10-15 01:18:31
|
hi folks, - The whole history and all branches from the subversion repository was imported into the Git repository. - Chris was kind enough to review the repository, and confirm that it looked OK. - A release (0.6.1) has been done using Git. - All the subversion oriented developer documentation has been modified to refer to git procedures. - so I have turned off commit access to the subversion tree, it is now readonly for everyone. Developer access is now: git clone ssh:// use...@dr.../gitroot/drobo-utils/drobo-utilsdrobo-utils Woo Hoo! |
From: <pet...@us...> - 2009-08-02 01:21:49
|
Revision: 261 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=261&view=rev Author: peter_silva Date: 2009-08-02 01:21:41 +0000 (Sun, 02 Aug 2009) Log Message: ----------- re-structured to get a proper hierarchy. Added DARFS items. Modified Paths: -------------- trunk/README.txt Modified: trunk/README.txt =================================================================== --- trunk/README.txt 2009-08-02 01:20:18 UTC (rev 260) +++ trunk/README.txt 2009-08-02 01:21:41 UTC (rev 261) @@ -11,13 +11,21 @@ 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... +the races... Command-line access is also bundled into a set of improvements +to a standards droboshare called 'Droboshare Augmented Root File System' (DARFS) + + .. contents:: -REQUIREMENTS +INSTALLATION ------------ +Drobo utils installation. + +REQUIREMENTS +============ + Drobo-utils was developed on pre-release version of Kubuntu (Hardy, Intrepid, and now Jaunty) Any similarly recent distro ought to do. @@ -43,33 +51,8 @@ Depends: ${shlibs:Depends}, ${misc:Depends}, parted peter@pepino% -SAFETY ------- - -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. - -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. - INSTALLING pre-requisites -------------------------- +========================= On ubuntu, it would typically look like so: Open a shell window. Enter the following package installation commands:: @@ -96,7 +79,7 @@ Install From Package --------------------- +==================== Point your browser at: http://sourceforge.net/project/showfiles.php?group_id=222830 where current packages are available. after downloading a .deb, it is simply a matter of: @@ -105,40 +88,38 @@ done! Install from Source -------------------- +=================== See DEVELOPER.txt -Try it Out ----------- +Try Out the CLI +=============== Assuming you have all of the above parts, in the directory where you -downloaded the source, you should be able to just do:: +downloaded the source, you should be able to invoke the command line +interface as follows:: drobom status see if something sensible happens... on my system with a drobo the following happens:: - % drobom status + % sudo drobom status /dev/sdz /drobo01 100% full ( ['Red alert', 'Bad disk', 'No redundancy'], 0 ) % Note: drive changed to sdz to avoid copy/paste errors. very scary, but my drobo is in bad shape right now... you should just get [] -as a status, which means there is nothing wrong. If you get an error -like it isn't detecting any drobos: +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. -No Drobo discovered, is one connected? +Try Out the GUI +=============== -Try to start up drobom from the root account. (sudo drobom..., or -sudo bash, or su - ) 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. - Once the command line stuff that is working, and assuming you have python-qt4 installed, try:: @@ -149,7 +130,17 @@ on desktops are accessible to users, so you can see them. +Try Out the Python API +====================== + See DEVELOPERS.txt + +Building debian & ubuntu packages +================================= + + See DEVELOPERS.txt + + Setup Drobo with Linux ---------------------- @@ -259,13 +250,13 @@ Getting an svn Snapshot ------------------------ +======================= See DEVELOPERS.txt Multiple LUNS -------------- +============= 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 @@ -306,7 +297,8 @@ Drobo Pro ---------- +========= + 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 @@ -333,15 +325,20 @@ (source: http://groups.google.com/group/drobo-talk/browse_frm/thread/453e02e105e9b41?hl=en ) -Firmware Upgrades ------------------ +Some people reported data corruption. This link claims to fix one such +issue: +http://www.drobospace.com/forum/thread/13951/Dropped-iSCSI-connections/?page=2#24792 -It's 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. + +Drobo Firmware +-------------- + +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. Fwupgrade -will do the work. It takes a few minutes, and prints a status +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:: root@pepino:/home/peter/drobo/drobo-utils/trunk# drobom fwupgrade @@ -393,6 +390,62 @@ fwload command. +SAFETY +====== + +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. + +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. + +Compatibility +============= + +Drobo has been tested with every old firmware version. Any Drobo should +be upgradable to modern firmware using the dashboard. + + NOTE: really need at least 1.1.1 to use Linux & ext3. + just use the tools to upgrade your firmware ASAP. + + 1.01 - very old... bad idea to install this, need to write + a script to get out, because it isn't in the revision + table. + not much works except firmware upgrade. + + 1.0.2 - works ok in CLI And GUI to view, and upgrade firmware. + + 1.0.3 - GUI and CLI work OK, can upgrade firmware. + Used ntfs3g for a few months under ubuntu 7.10 Linux. + Used 2 TB LUN, with 1.5 TB of physical space available. + + 1.1.0 - dashboard works no issues. + - from this point, you don't seem to need to unplug the USB + connector to complete the upgrade. + + - firmware prior to here deals badly with ext3. + + 1.1.1 - 1.2.4 works without issues. + ('name' not supported by firmware) + + 1.3.0 - works without issues. + + KNOWN BUGS ---------- @@ -414,44 +467,79 @@ We have a report that dumping diagnostics does not work over firewire. Work-around: connect via USB. -Building debian & ubuntu packages ---------------------------------- - See DEVELOPERS.txt +Droboshare Support +------------------ +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. -Firmware Compatibility ----------------------- +DARFS +===== +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 - Drobo has been tested with every old firmware version. Any Drobo should - be upgradable to modern firmware using the dashboard. +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. - NOTE: really need at least 1.1.1 to use Linux & ext3. - just use the tools to upgrade your firmware ASAP. +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. - 1.01 - very old... bad idea to install this, need to write - a script to get out, because it isn't in the revision - table. - not much works except firmware upgrade. +DARFS Installation +================== +Download it from drobo-utils.sf.net: +steps: - 1.0.2 - works ok in CLI And GUI to view, and upgrade firmware. + 1. copy the tar file onto somewhere on your share. + 2. log in via DropBear ssh as a root user on the droboshare. + 3. cd /mnt/DroboShares/YourDrobo (root of drobo file system, for example) + 4. tar -xzf darfs.tgz (root of drobo file system, for example) + 5. the root directory of the tar is 'slash'.. it will be under YourDrobo + 6. export PATH="/mnt/DroboShares/YourDrobo/slash/usr/bin:${PATH}" (which is where python and drobom are.) + 7. drobom status - 1.0.3 - GUI and CLI work OK, can upgrade firmware. - Used ntfs3g for a few months under ubuntu 7.10 Linux. - Used 2 TB LUN, with 1.5 TB of physical space available. - - 1.1.0 - dashboard works no issues. - - from this point, you don't seem to need to unplug the USB - connector to complete the upgrade. +you're done! - - firmware prior to here deals badly with ext3. +Enable SFTP Support +=================== - 1.1.1 - 1.2.4 works without issues. - ('name' not supported by firmware) +all you need to do is: - 1.3.0 - works without issues. +ln -s /usr/libexec /mnt/Droboshares/YourDrobo/slash/usr/libexec +Try an sftp from another machine (as root...) and it ought to work. +(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.) + + +Building Droboshare applications +================================ + See DEVELOPERS.txt + +Droboshare Firmware +=================== + +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. + + Credits ------- This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-08-02 01:20:25
|
Revision: 260 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=260&view=rev Author: peter_silva Date: 2009-08-02 01:20:18 +0000 (Sun, 02 Aug 2009) Log Message: ----------- incorporated TODO list into DEVELOPERS.txt more DARFS documentation. Modified Paths: -------------- trunk/DEVELOPERS.txt Removed Paths: ------------- trunk/TODO Modified: trunk/DEVELOPERS.txt =================================================================== --- trunk/DEVELOPERS.txt 2009-07-18 12:06:13 UTC (rev 259) +++ trunk/DEVELOPERS.txt 2009-08-02 01:20:18 UTC (rev 260) @@ -2,7 +2,7 @@ DEVELOPERS NOTES ---------------- -.. contents: +.. contents:: This software is copyright under GPL. See near end file for details... @@ -71,7 +71,7 @@ Record results of release tests in the branch (QA.txt) As new tests are created, modify QA.txt on trunk for to keep references for the next release. Quality Assurance (QA.txt) --------------------------- +========================== QA.txt is a quality assurance log. The version on the trunk of the releases indicates the QA procedure to be applied to the next version during the release process. Since @@ -81,7 +81,7 @@ Building Debian & Ubuntu Packages ---------------------------------- +================================= assumes you have installed the Build dependencies:: @@ -122,7 +122,113 @@ % scp README.html <user>,dro...@we...:htdocs +Droboshare +---------- +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. There is download called +the Droboshare Augmented Root File system (DARFS), which includes a python +interpreter and drobo-utils. + +Open Task: Reverse Engineer Dashboard <-> Droboshare Protocol +============================================================= + +Why isn't there full support in host based drobo-utils itself? Digital +Robotics hasn't released details of the protocol used by the proprietary +dashboard to communicate with a droboshare, so it would be a lot of work to +reverse engineer that. So support of a droboshare from a linux GUI on a +host system is not likely in the near future. + +If someone wants to figure that out, it might be a good thing (tm) +After that is figured out, the next step would be to understand +how to flash the firmware remotely. That would eliminate the last function +that cannot be done with open source. + +Building DARFS +============== + +DARFS - Droboshare Augmented Root File System. A pile of stuff that can +be run on a droboshare. + +Have a look here: + +http://groups.google.com/group/drobo-talk/web/building-droboshare-apps-on-debianish-os?hl=en + +TODO +---- + +Tasks which would be cool to get done, in no particular order: + +CentOS support. Fedora is likely fine, but should build a VM with CentOS on it, and build an rpm. RHEL has an ancient python (2.4?) with no ctypes by default, so could be interesting. + +GUI - handle when Drobo disappears... + +Refuse known non-working feature bits... firmware (review 2009 SDK release) + Review feature bits, mis-marked? 28 + +Add Alerting to GUI & CLI + -- save config... + .. SMTP forwarder: + .. address + .. authentication.? u+p + .. + +Droboshare bugs + -- don't dump diags to /tmp, they don't fit. + -- don't + +BUGS: + when running two fw uploads, the second one will not run easily. + need to wait for transaction to timeout... perhaps randomize id? + did randomization, did not change anything... + +STANDARD menu entries for droboview... + partition types do not appear to be correctly displayed... + some confusion between NTFS vs. EXT3 no obvious ill effect. + + partition type should pre-select in Format dialog... + + memory consumption on the GUI. still chews up 4 MB per hour... + +gnats: + man page does not document output. + -- what is the meaning of the output? provide a sample... + +review print statements: + should they write to stderr? + + +STANDARD menu entries for droboview... + +Better STATUS progress reporting: + -- the block count is there, but heuristics for determining timing suck. + -- some sort of indicator of how long 'relay out' will be in progress. + -- when it is busy, it should say so... like when I emptied an ntfs it took hours for the led indicators to drop from 70% to 0. It should say something about what is going on. + +LIVELIER GUI: + -- have status queries proceed asynchronously from the GUI. + right now, if the drobo is slow, the GUI makes it slower, and gets very slow too. + should run as a daemon, async. from the GUI. + +Re-design the whole darn thing. + -- there should be some sort of service integrated with dbus-hal + -- not sure that a GUI is needed at all. but if it is, it should be a DBUS client. + -- how does authentication work in DBUS? + + + of interest: + -- python bindings for parted... http://dcantrel.fedorapeople.org/pyparted/ + + +Revision date: 2009/05/19 + +copyright: + +Drobo Utils Copyright (C) 2008,2009 Peter Silva (Pet...@gm...) +Drobo Utils comes with ABSOLUTELY NO WARRANTY; For details type see the file +named COPYING in the root of the source directory tree. + Administrivia ------------- Deleted: trunk/TODO =================================================================== --- trunk/TODO 2009-07-18 12:06:13 UTC (rev 259) +++ trunk/TODO 2009-08-02 01:20:18 UTC (rev 260) @@ -1,68 +0,0 @@ - - -in no particular order: - -GUI - handle when Drobo disappears... - -Review feature bits, mis-marked? 28 -test with old firmware... - -Alerting... - -- save config... - .. SMTP forwarder: - .. address - .. authentication.? u+p - .. - -BUGS: - when running two fw uploads, the second one will not run easily. - need to wait for transaction to timeout... perhaps randomize id? - did randomization, did not change anything... - -STANDARD menu entries for droboview... - partition types do not appear to be correctly displayed... - some confusion between NTFS vs. EXT3 no obvious ill effect. - - partition type should pre-select in Format dialog... - - memory consumption on the GUI. still chews up 4 MB per hour... - -gnats: - man page does not document output. - -- what is the meaning of the output? provide a sample... - -review print statements: - should they write to stderr? - - -STANDARD menu entries for droboview... - -Better STATUS progress reporting: - -- the block count is there, but heuristics for determining timing suck. - -- some sort of indicator of how long 'relay out' will be in progress. - -- when it is busy, it should say so... like when I emptied an - ntfs it took hours for the led indicators to drop from 70% to 0. - It should say something about what is going on. - -LIVELIER GUI: - -- have status queries proceed asynchronously from the GUI. - right now, if the drobo is slow, the GUI makes it slower, and gets very slow too. - should run as a daemon, async. from the GUI. - -Re-design the whole darn thing. - -- there should be some sort of service integrated with dbus-hal - -- not sure that a GUI is needed at all. but if it is, it should be a DBUS client. - -- how does authentication work in DBUS? - - - of interest: - -- python bindings for parted... http://dcantrel.fedorapeople.org/pyparted/ - - -Revision date: 2009/05/19 - -copyright: - -Drobo Utils Copyright (C) 2008,2009 Peter Silva (Pet...@gm...) -Drobo Utils comes with ABSOLUTELY NO WARRANTY; For details type see the file -named COPYING in the root of the source directory tree. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: Sebastian S. <sps...@th...> - 2009-07-30 18:10:19
|
Hi All, Just a heads up that I posted a patch that gets most of the drobom commands working on the Pro via iSCSI. http://sourceforge.net/tracker/?func=detail&aid=2829806&group_id=222830&atid=1056843 This change works for me, the only issue being that it ends up displaying the "sgX" (Scsi generic) device and not the "sdX" ( Block Device) in the listings. I think it would be trivial to do the forward/backwards mapping. -Sebastian |
From: <pet...@us...> - 2009-07-18 12:06:17
|
Revision: 259 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=259&view=rev Author: peter_silva Date: 2009-07-18 12:06:13 +0000 (Sat, 18 Jul 2009) Log Message: ----------- Add hint about dependency on python-ctypes on RHEL (which has python 2.4) Modified Paths: -------------- trunk/README.txt Modified: trunk/README.txt =================================================================== --- trunk/README.txt 2009-05-26 22:11:09 UTC (rev 258) +++ trunk/README.txt 2009-07-18 12:06:13 UTC (rev 259) @@ -28,6 +28,9 @@ python -- interpreter for python language parted -- partitioner, usually included with the distro. + if using RHEL, which has python 2.4... + python-ctypes -- module for C-interface + for the GUI: python-qt4 -- the python bindings for version 4 of the QT toolkit This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <ag...@us...> - 2009-05-26 22:11:12
|
Revision: 258 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=258&view=rev Author: agrover Date: 2009-05-26 22:11:09 +0000 (Tue, 26 May 2009) Log Message: ----------- detection was throwing an exception due to too many parameters to get_sub_page. Modified Paths: -------------- trunk/DroboIOctl.py Modified: trunk/DroboIOctl.py =================================================================== --- trunk/DroboIOctl.py 2009-05-24 12:56:57 UTC (rev 257) +++ trunk/DroboIOctl.py 2009-05-26 22:11:09 UTC (rev 258) @@ -132,7 +132,7 @@ mcb=struct.pack("6B", 0x12, 0, 0, 0, hoholen, 0 ) # len ought to be 96 - hoho=self.get_sub_page(hoholen,mcb,0,4,self.debug) + hoho=self.get_sub_page(hoholen,mcb,0,self.debug) (dunno1,vendor,dunno2) = struct.unpack(fmt,hoho) return ( host, channel, id, lun, vendor ) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-05-24 12:57:00
|
Revision: 257 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=257&view=rev Author: peter_silva Date: 2009-05-24 12:56:57 +0000 (Sun, 24 May 2009) Log Message: ----------- documentation fixes. Modified Paths: -------------- trunk/README.txt trunk/TODO Modified: trunk/README.txt =================================================================== --- trunk/README.txt 2009-05-24 12:54:51 UTC (rev 256) +++ trunk/README.txt 2009-05-24 12:56:57 UTC (rev 257) @@ -44,7 +44,7 @@ ------ Those worried about safety of using this software should know: it was -developed with assistance from the vendor (Digital Robotics Inc.), and +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 @@ -328,6 +328,7 @@ After that, drobo-utils should be able to detect the Drobo and manage it over ethernet. +(source: http://groups.google.com/group/drobo-talk/browse_frm/thread/453e02e105e9b41?hl=en ) Firmware Upgrades ----------------- Modified: trunk/TODO =================================================================== --- trunk/TODO 2009-05-24 12:54:51 UTC (rev 256) +++ trunk/TODO 2009-05-24 12:56:57 UTC (rev 257) @@ -2,7 +2,7 @@ in no particular order: -Find Dialog -- in ShowFile +GUI - handle when Drobo disappears... Review feature bits, mis-marked? 28 test with old firmware... This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-05-24 12:54:58
|
Revision: 256 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=256&view=rev Author: peter_silva Date: 2009-05-24 12:54:51 +0000 (Sun, 24 May 2009) Log Message: ----------- interpret msdos as FAT32... Modified Paths: -------------- trunk/Drobo.py Modified: trunk/Drobo.py =================================================================== --- trunk/Drobo.py 2009-05-24 03:30:20 UTC (rev 255) +++ trunk/Drobo.py 2009-05-24 12:54:51 UTC (rev 256) @@ -371,7 +371,7 @@ fd=open(format_script, 'w') fd.write( "#!/bin/sh\n" ) - if fstype == 'FAT32': + if fstype == 'FAT32' or fstype == 'msdos': ptype='msdos' else: ptype='gpt' @@ -399,7 +399,7 @@ fd.write( "parted %s mkpart ntfs 0 100%%\n" % cd ) fd.write( "parted %s print; sleep 5\n" % cd ) fd.write( 'mkntfs -f -L Drobo01 %s1\n' % cd ) - elif fstype == 'FAT32': + elif fstype == 'FAT32' or fstype == 'msdos': fd.write( "parted %s mkpart primary fat32 0 100%%\n" % cd ) fd.write( "parted %s print; sleep 5\n" % cd ) fd.write( 'mkdosfs -v -v -F 32 -S 4096 -n Drobo01 %s1\n' % cd ) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-05-24 03:30:29
|
Revision: 255 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=255&view=rev Author: peter_silva Date: 2009-05-24 03:30:20 +0000 (Sun, 24 May 2009) Log Message: ----------- bug in device detection debug output Modified Paths: -------------- trunk/DroboIOctl.py Modified: trunk/DroboIOctl.py =================================================================== --- trunk/DroboIOctl.py 2009-05-20 03:45:12 UTC (rev 254) +++ trunk/DroboIOctl.py 2009-05-24 03:30:20 UTC (rev 255) @@ -132,7 +132,7 @@ mcb=struct.pack("6B", 0x12, 0, 0, 0, hoholen, 0 ) # len ought to be 96 - hoho=self.get_sub_page(hoholen,mcb,0,4) + hoho=self.get_sub_page(hoholen,mcb,0,4,self.debug) (dunno1,vendor,dunno2) = struct.unpack(fmt,hoho) return ( host, channel, id, lun, vendor ) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-05-20 03:45:17
|
Revision: 254 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=254&view=rev Author: peter_silva Date: 2009-05-20 03:45:12 +0000 (Wed, 20 May 2009) Log Message: ----------- QA & Release work. Modified Paths: -------------- branches/r0_6_0/Drobo.py branches/r0_6_0/QA.txt branches/r0_6_0/debian/changelog branches/r0_6_0/debian/rules branches/r0_6_0/setup.py Modified: branches/r0_6_0/Drobo.py =================================================================== --- branches/r0_6_0/Drobo.py 2009-05-20 01:10:53 UTC (rev 253) +++ branches/r0_6_0/Drobo.py 2009-05-20 03:45:12 UTC (rev 254) @@ -38,7 +38,7 @@ MAX_TRANSACTION = 250 # obviously need to update this with every release. -VERSION = 'running trunk at: ' + time.ctime(time.time()) +VERSION = 'r0_6_0' # set to non-zero to increase verbosity of library functions. Modified: branches/r0_6_0/QA.txt =================================================================== --- branches/r0_6_0/QA.txt 2009-05-20 01:10:53 UTC (rev 253) +++ branches/r0_6_0/QA.txt 2009-05-20 03:45:12 UTC (rev 254) @@ -5,14 +5,41 @@ -- Set version to pre-release one. -- build packages with pre-release version id. 1.1 drobom status... check for accuracy. + +root@pepino:~# drobom status +/dev/sdf:/dev/sdg - Drobo01 00% full - ([], 0) +root@pepino:~# + 1.2 drobom settime + +root@pepino:~# drobom settime +root@pepino:~# + 1.3 drobom status... check for accuracy. + +root@pepino:~# drobom status +/dev/sdf:/dev/sdg - Drobo01 00% full - ([], 0) +root@pepino:~# + 1.4 drobom fwload (something really old) 1.03 + +done with GUI. + 1.4.1 drobom shutdown -- to run the firmware. + +done with GUI. + 1.4.2 restart (unplug and replug usb) + +done 1.4.3 run drobom status etc.. (make sure it is running 1.0.3) should say disk pack is un-readable or some such. +root@pepino:~# drobom status +firmware too old to report capacity properly... or the drobo is empty... +/dev/sdf - TRUSTED DATA -1% full - (['Unknown version'], 0) +root@pepino:~# + 1.4.4 hard reset to factory default after downgrade, disk pack will no longer be recognized. need to reset to make Drobo look at the disks. @@ -20,25 +47,340 @@ http://www.drobospace.com/article/10207/Resetting-the-Drobo/?highlight=reset+drobo 1.4.3 place a file on the Drobo. make sure it works. + +root@pepino:~# drobom format ext3 +This is guaranteed to erase your disk, so you must say: PleaseEraseMyData +root@pepino:~# drobom format ext3 PleaseEraseMyData +You asked nicely, so I will format ext3 as you requested +OK, I built the script but nothing is erased yet... +If you are really sure, go ahead and do: sh /tmp/fmtscript +root@pepino:~# more /tmp/fmtscript +#!/bin/sh +parted /dev/sdf mklabel gpt +parted /dev/sdf mkpart ext2 0 100% +parted /dev/sdf print; sleep 5 +mke2fs -j -i 262144 -L Drobo01 -m 0 -O sparse_super,^resize_inode /dev/sdf1 +root@pepino:~# sh -x /tmp/fmtscript ++ parted /dev/sdf mklabel gpt +Information: You may need to update /etc/fstab. + ++ parted /dev/sdf mkpart ext2 0 100% +Information: You may need to update /etc/fstab. + ++ parted /dev/sdf print +Model: TRUSTED USB Mass Storage (scsi) +Disk /dev/sdf: 2199GB +Sector size (logical/physical): 512B/512B +Partition Table: gpt + +Number Start End Size File system Name Flags + 1 17.4kB 2199GB 2199GB ext2 + ++ sleep 5 ++ mke2fs -j -i 262144 -L Drobo01 -m 0 -O sparse_super,^resize_inode /dev/sdf1 +mke2fs 1.41.4 (27-Jan-2009) +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 37 mounts or +180 days, whichever comes first. Use tune2fs -c or -i to override. +root@pepino:~# mount /dev/sdf1 /drobo01 +root@pepino:~# +root@pepino:~# echo hoho >/drobo01/kk +root@pepino:~# ls -al /drobo01/ +total 28 +drwxr-xr-x 3 root root 4096 2009-05-19 22:25 . +drwxr-xr-x 25 root root 4096 2009-05-04 23:21 .. +-rw-r--r-- 1 root root 5 2009-05-19 22:25 kk +drwx------ 2 root root 16384 2009-05-19 22:20 lost+found +root@pepino:~# drobom status +/dev/sdf /drobo01 TRUSTED DATA 00% full - ([], 0) +root@pepino:~# + + 1.4.4 drobom status -- have a look. +oot@pepino:~# drobom info +--------------------------------------------------------- +Info about Drobo Name: TRUSTED DATA Devices: /dev/sdf +--------------------------------------------------------- +query config result: +(4, 1, 2199023250944) +max lun size is: 2199023250944 + +query capacity result: +(995528540160, 0, 995528540160, 0) +Physical space... used: 0 free: 995528540160 Total: 995528540160 + +query protocol version result: +(0, 10) + +query settings result: +(293, 8, 'TRUSTED DATA') +Drobo time is Wed Dec 31 19:04:53 1969 + +query slotinfo result: number of slots: 4 +[(0, 500107862016, 0, 'green', 'ST3500830AS', 'ST3500830AS'), (1, 500107862016, 0, 'green', 'WDC WD5000AAKS-00C8A0', 'WDC WD5000AAKS-0'), (2, 0, 0, 'gray', '', ''), (3, 500107862016, 0, 'green', 'WDC WD5000AAKS-00C8A0', 'WDC WD5000AAKS-0')] +query firmware result: +(1, 172, 9222, 8, 0, 'Sep 13 2007,16:07:38', 'ArmMarvell', '1.0.3', ['NO_AUTO_REBOOT', 'NO_FAT32_FORMAT', 'USED_CAPACITY_FROM_HOST', 'DISKPACKSTATUS', 'ENCRYPT_NOHEADER', 'CMD_STATUS_QUERIABLE']) +drobo says firmware revision: 1 . 172 ( 9222 ) was built: Sep 13 2007,16:07:38 + +query status result: +([], 0) + +query options result: +(0, 0, 0) + +query luninfo result: +(0, 995528540160, 0) + +--------------------------------------------------------- +root@pepino:~# + 1.5 drobom fwupgrade + +with GUI +root@pepino:~# drobom view +looking for firmware for: armmarvell 1.172.9222 hw version: 1.00 +This Drobo should be running: raptor/firmware/armmarvell/v1.12.tdf +checkup: this Drobo is a armmarvell hw rev: 1.00, and needs: 1.172.9222 +looking for firmware for: armmarvell 1.172.9222 hw version: 1.00 +This Drobo should be running: raptor/firmware/armmarvell/v1.12.tdf +looking for: /root/.drobo-utils/armmarvell_1.00_v1.12.tdf +local copy already present: /root/.drobo-utils/armmarvell_1.00_v1.12.tdf +Reading Firmware from = /root/.drobo-utils/armmarvell_1.00_v1.12.tdf +validateFirmware start... +header+body lengths validated. Good. +Magic number validated. Good. +484 + 2942433 = 2942917 length validated. Good. +CRC from header: 1401631832, calculated using python zlib crc32: 1401631832 +CRC for body from header: 2717012571, calculated: 2717012571 +32 bit Cyclic Redundancy Check correct. Good. +validateFirmware successful... +correct fw available + 1.5.1 drobom shutdown - to run the firmware. 1.5.2 drobom status -- have a look. + +root@pepino:~# drobom info firmware +--------------------------------------------------------- +Info about Drobo Name: TRUSTED DATA Devices: /dev/sdf +--------------------------------------------------------- +query firmware result: +(1, 201, 12942, 12, 6, 'May 13 2008,15:29:32', 'ArmMarvell', '1.1.2', ['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_DROBOSHARE', 'SUPPORTS_NEW_LUNINFO2']) +drobo says firmware revision: 1 . 201 ( 12942 ) was built: May 13 2008,15:29:32 + +--------------------------------------------------------- +root@pepino:~# + 1.5.3 repeat 1.5 perhaps a second time (as needed to get to current) +root@pepino:~# drobom view +looking for firmware for: armmarvell 1.201.12942 hw version: 1.00 +This Drobo should be running: raptor/firmware/armmarvell/v1.3.0.tdz +checkup: this Drobo is a armmarvell hw rev: 1.00, and needs: 1.201.12942 +looking for firmware for: armmarvell 1.201.12942 hw version: 1.00 +This Drobo should be running: raptor/firmware/armmarvell/v1.3.0.tdz +looking for: /root/.drobo-utils/armmarvell_1.00_v1.3.0.tdz +local copy already present: /root/.drobo-utils/armmarvell_1.00_v1.3.0.tdz +Reading Firmware from = /root/.drobo-utils/armmarvell_1.00_v1.3.0.tdz +validateFirmware start... +header+body lengths validated. Good. +Magic number validated. Good. +484 + 3130135 = 3130619 length validated. Good. +CRC from header: 4183081909, calculated using python zlib crc32: 4183081909 +CRC for body from header: 2216664787, calculated: 2216664787 +32 bit Cyclic Redundancy Check correct. Good. +validateFirmware successful... +correct fw available +root@pepino:~# drobom info firmware +--------------------------------------------------------- +Info about Drobo Name: Drobo disk pack Devices: /dev/sdf +--------------------------------------------------------- +query firmware result: +(1, 248, 15408, 13, 6, 'Dec 2 2008,10:24:08', 'ArmMarvell', '1.3.0', ['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_DROBOSHARE', 'SUPPORTS_NEW_LUNINFO2', 'feature x0800', 'feature x2000 ']) +drobo says firmware revision: 1 . 248 ( 15408 ) was built: Dec 2 2008,10:24:08 + +--------------------------------------------------------- +root@pepino:~# + + 1.7 drobom setlunsize 3 (should fail),1,2 +root@pepino:~# drobom setlunsize 2 +This is guaranteed to erase your disk, so you must say: PleaseEraseMyData +root@pepino:~# drobom setlunsize 3 PleaseEraseMyData +lun size needs to be 1, 2, 4, 8, or 16 TiB; 3 is invalid +root@pepino:~# +root@pepino:~# drobom setlunsize 4 PleaseEraseMyData +You asked nicely, so I will set the lunsize to 4 as you requested +set lunsize to 4 TiB +Done... Drobo is likely now rebooting. In a few minutes, it will come back with the new LUN size. +root@pepino:~# +root@pepino:~# drobom info luns +--------------------------------------------------------- +Info about Drobo Name: Drobo disk pack Devices: /dev/sdf +--------------------------------------------------------- +query luninfo result: +(0, 4398046511104, 0, 'No Partitions', ['FAT32']) + +--------------------------------------------------------- +root@pepino:~# drobom setlunsize 1 PleaseEraseMyData +You asked nicely, so I will set the lunsize to 1 as you requested +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:~# drobom info luns +--------------------------------------------------------- +Info about Drobo Name: Drobo disk pack Devices: /dev/sdf +--------------------------------------------------------- +query luninfo result: +(0, 1099511558144, 0, 'No Partitions', ['FAT32']) + +--------------------------------------------------------- +root@pepino:~# + +root@pepino:~# drobom setlunsize 2 PleaseEraseMyData +You asked nicely, so I will set the lunsize to 2 as you requested +set lunsize to 2 TiB +Done... Drobo is likely now rebooting. In a few minutes, it will come back with the new LUN size. +root@pepino:~# +root@pepino:~# drobom info luns +--------------------------------------------------------- +Info about Drobo Name: Drobo disk pack Devices: /dev/sdf +--------------------------------------------------------- +query luninfo result: +(0, 2199023185920, 0, 'No Partitions', ['FAT32']) + +--------------------------------------------------------- +root@pepino:~# + + 1.8 drobom create file systems, each type. msdos ntfs ext3 .... +MSDOS one didn't work! + +root@pepino:~# drobom format FAT32 PleaseEraseMyData +You asked nicely, so I will format FAT32 as you requested +OK, I built the script but nothing is erased yet... +If you are really sure, go ahead and do: sh /tmp/fmtscript +root@pepino:~# more /tmp/fmtscript +#!/bin/sh +parted /dev/sdf mklabel msdos +parted /dev/sdf mkpart primary fat32 0 100% +parted /dev/sdf print; sleep 5 +mkdosfs -v -v -F 32 -S 4096 -n Drobo01 /dev/sdf1 +root@pepino:~# sh -x /tmp/fmtscript ++ parted /dev/sdf mklabel msdos +Warning: The existing disk label on /dev/sdf will be destroyed and all data on this disk will be lost. Do +you want to continue? +parted: invalid token: msdos +Yes/No? Yes +New disk label type? [gpt]? +Information: You may need to update /etc/fstab. + ++ parted /dev/sdf mkpart primary fat32 0 100% +Information: You may need to update /etc/fstab. + ++ parted /dev/sdf print +Model: TRUSTED Mass Storage (scsi) +Disk /dev/sdf: 2199GB +Sector size (logical/physical): 512B/512B +Partition Table: gpt + +Number Start End Size File system Name Flags + 1 17.4kB 2199GB 2199GB primary msftres + ++ sleep 5 ++ mkdosfs -v -v -F 32 -S 4096 -n Drobo01 /dev/sdf1 +mkdosfs 3.0.1 (23 Nov 2008) +Boot jump code is eb 58 +Using 32 reserved sectors +536870854 sectors for FAT+data, starting with 32 sectors/cluster +Trying with 32 sectors/cluster: +FAT12: #clu=16776830, fatlen=6144, maxclu=4080, limit=4080 +FAT12: too much clusters +FAT16: #clu=16776702, fatlen=8192, maxclu=65520, limit=65520 +FAT16: too much clusters +FAT16: would be misdetected as FAT12 +FAT32: #clu=16776190, fatlen=16383, maxclu=16776192, limit=268435440 +Using sector 6 as backup boot sector (0 = none) +/dev/sdf1 has 255 heads and 63 sectors per track, +logical sector size is 4096, +using 0xf8 media descriptor, with 536870886 sectors; +file system has 2 32-bit FATs and 32 sectors per cluster. +FAT size is 16383 sectors, and provides 16776190 clusters. +Volume ID is 180dbb15, volume label Drobo01 . +root@pepino:~# + + +NTFS OK... + root@pepino:~# drobom format ntfs PleaseEraseMyData +You asked nicely, so I will format ntfs as you requested +OK, I built the script but nothing is erased yet... +If you are really sure, go ahead and do: sh /tmp/fmtscript +root@pepino:~# more /tmp/fmtscript +#!/bin/sh +parted /dev/sdf mklabel gpt +parted /dev/sdf mkpart ntfs 0 100% +parted /dev/sdf print; sleep 5 +mkntfs -f -L Drobo01 /dev/sdf1 +root@pepino:~# sh -x /tmp/fmtscript ++ parted /dev/sdf mklabel gpt +Warning: The existing disk label on /dev/sdf will be destroyed and all data on this disk will be lost. Do +you want to continue? +parted: invalid token: gpt +Yes/No? Yes +New disk label type? [gpt]? +Information: You may need to update /etc/fstab. + ++ parted /dev/sdf mkpart ntfs 0 100% +Information: You may need to update /etc/fstab. + ++ parted /dev/sdf print +Model: TRUSTED Mass Storage (scsi) +Disk /dev/sdf: 2199GB +Sector size (logical/physical): 512B/512B +Partition Table: gpt + +Number Start End Size File system Name Flags + 1 17.4kB 2199GB 2199GB ntfs + ++ sleep 5 ++ mkntfs -f -L Drobo01 /dev/sdf1 +Cluster size has been automatically set to 4096 bytes. +Creating NTFS volume structures. +mkntfs completed successfully. Have a nice day. +root@pepino:~# + + 1.9 drobom diags # verify that dumping diagnostics still works... +Done with GUI, and show as well... + 2.0 with fw >= 1.30 drobom name + done with GUI. drobom info... + done with GUI. 3.0 Re-build packages with final release id. Modified: branches/r0_6_0/debian/changelog =================================================================== --- branches/r0_6_0/debian/changelog 2009-05-20 01:10:53 UTC (rev 253) +++ branches/r0_6_0/debian/changelog 2009-05-20 03:45:12 UTC (rev 254) @@ -1,39 +1,16 @@ -drobo-utils (0.5.0-2) unstable; urgency=low +drobo-utils (0.6.0-1) unstable; urgency=low - * replaced DroboDMP C extension by DroboIOctl python class. no need - for architecture dependent packages. this also means you can just - try it out straight after download, no need to install anything. - much easier. fewer build dependencies as well. - * device detection completely re-written. It works better now. - * Now displays mount points where it makes sense to do so. - * status command output better/different. shows all devices and mount points - for each drobo. - * full Multiple LUN support. should do what is expected. - * full multiple Drobo support. should do what is expected. - * added modular info printing with csv list of outputs. - * firmware 1.3.0, has enabled formerly broken functionality which - name makes the sync command rename every drobo to 'hi there'. - fixed. - * added 'name' command, to name Drobo. (functionality of Sync) - * corrected detection logic, which depended on formerly immutable name. - (affects fw >= 1.3.0) now use same mechanisms as sg_scan from sg3_utils. - * documentation moved into restructured text. now shows up on the web. - web site and documntation now consistent. + * Major: GUI heavily re-vamped. Behaves better. + * Major: DroboPRO support added (thanks to lemonizer on the google group!) + * Major: GUI gets online documentation. + * GUI: layouts replaced fixed dimensions. + * GUI: added Rename support + * GUI: added Load firmware button + * GUI: Show Diagnostics (equiv. to diagprint.) + * GUI: Name display to main display. Easier to tell which Drobo is which. + * GUI: added mount point display to space used tool tip. + * api: added ability to detect un-documented feature bit settings. + * ddiag.c becomes drobom diagprint + * catlee fixes the packaging again. - -- Peter Silva <Pet...@gm...> Sat, 31 Jan 2009 15:36:17 -0500 - -drobo-utils (0.4.0-1) unstable; urgency=medium - - * IMPORTANT: firmware 1.3.0 support added. Earlier drobo-utils versions - will not recognize a drobo running 1.3.0 or later. - * CLI is more normal... use getopts (got rid of device as fixed place arg.) - now allows command to be an option as well. - * Changed DEBUG from a flag requiring code modification, to a bitmap honored - as a command-line argument (--verbose) - * misc. improvements in documentation. - * droboview now only launches for first drobo found in list, and stays - foreground always. - * drobom list returns a list that is easier to parse (suitable for use in - backticks.) - -- Peter Silva <Pet...@gm...> Fri, 12 Sep 2008 11:31:43 -0400 Modified: branches/r0_6_0/debian/rules =================================================================== --- branches/r0_6_0/debian/rules 2009-05-20 01:10:53 UTC (rev 253) +++ branches/r0_6_0/debian/rules 2009-05-20 03:45:12 UTC (rev 254) @@ -26,7 +26,7 @@ dh_testroot dh_clean -k dh_installdirs - make doc + make doc python setup.py install_lib -d $(CURDIR)/debian/$(PKGNAME)/usr/share/python-support/$(PKGNAME) find $(CURDIR)/debian/$(PKGNAME) -name "*\.pyc" -delete python setup.py install_data -d $(CURDIR)/debian/$(PKGNAME)/usr/share/$(PKGNAME) Modified: branches/r0_6_0/setup.py =================================================================== --- branches/r0_6_0/setup.py 2009-05-20 01:10:53 UTC (rev 253) +++ branches/r0_6_0/setup.py 2009-05-20 03:45:12 UTC (rev 254) @@ -5,7 +5,7 @@ from distutils.core import setup setup (name = 'Drobo-utils', - version = '0.5.0', + version = '0.6.0', description = 'Drobo Management Protocol io package', py_modules=['Drobo','DroboGUI', 'DroboIOctl' ], scripts=['drobom', 'droboview'], This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-05-20 01:10:55
|
Revision: 253 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=253&view=rev Author: peter_silva Date: 2009-05-20 01:10:53 +0000 (Wed, 20 May 2009) Log Message: ----------- Release branch with DroboPro support, new GUI, and online help. Added Paths: ----------- branches/r0_6_0/ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-05-20 01:03:59
|
Revision: 252 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=252&view=rev Author: peter_silva Date: 2009-05-20 01:03:51 +0000 (Wed, 20 May 2009) Log Message: ----------- Mostly documentation improvements. Also added a search function that doesn't work, so it's commented out. Modified Paths: -------------- trunk/CHANGES.txt trunk/DroboGUI.py trunk/README.txt trunk/TODO Modified: trunk/CHANGES.txt =================================================================== --- trunk/CHANGES.txt 2009-05-19 11:45:25 UTC (rev 251) +++ trunk/CHANGES.txt 2009-05-20 01:03:51 UTC (rev 252) @@ -2,14 +2,17 @@ $LastChangedDate$ $Rev$ -0.5.1 +0.6.0 + * Major: GUI heavily re-vamped. Behaves better. * Major: DroboPRO support added (thanks to lemonizer on the google group!) - * Major: GUI improvement: replaced fixed dimensions in GUI with layouts. - * GUI gets online documentation. - * added Rename support to GUI. - * added Name display to main display. Easier to tell which Drobo is which. - * added mount point display to space used tool tip. - * added ability to detect un-documented feature bit settings. + * Major: GUI gets online documentation. + * GUI: layouts replaced fixed dimensions. + * GUI: added Rename support + * GUI: added Load firmware button + * GUI: Show Diagnostics (equiv. to diagprint.) + * GUI: Name display to main display. Easier to tell which Drobo is which. + * GUI: added mount point display to space used tool tip. + * api: added ability to detect un-documented feature bit settings. * ddiag.c becomes drobom diagprint * catlee fixes the packaging again. Modified: trunk/DroboGUI.py =================================================================== --- trunk/DroboGUI.py 2009-05-19 11:45:25 UTC (rev 251) +++ trunk/DroboGUI.py 2009-05-20 01:03:51 UTC (rev 252) @@ -66,15 +66,14 @@ al = QtGui.QVBoxLayout(self) self.main = QtGui.QLabel(""" drobo-utils: software to manage a Drobo storage unit from Data Robotics International Corp. - Winner of the Data Robotics Bounty 2008 for a linux dashboard! - Version: """ + Drobo.VERSION + """ + Winner of the Data Robotics Incorporated (DRI) Bounty 2008 for a linux dashboard! + Thanks tor RI for putting up the Bounty! + Copyright 2008 Peter Silva ( Pet...@gm... ) license: General Public License (GPL) v3 + Version: """ + Drobo.VERSION + """ - with contributions from: Chris Atlee (ch...@at...), Brad Guillory, <wit...@sp...rge> - and inspiration from: Joe Krahn - - and thanks for DRI for putting up the Bounty! + See README for other contributors. """ , self) al.addWidget(self.main) self.quit = QtGui.QPushButton('Dismiss',self) @@ -83,12 +82,19 @@ self.hide) class ShowText(QtGui.QWidget): + + def __init__(self, manual, isfile=True, parent=None): QtGui.QWidget.__init__(self, parent) self.setMinimumSize(500, 440) al = QtGui.QVBoxLayout(self) + # search support... buggy. + #self.lastsearch='' + #self.lscursor=QtGui.QTextCursor(self) + #self.lscursor.setPosition(0) + if isfile: dirs=[ "/usr/local/share/drobo-utils-doc", "/usr/share/drobo-utils/share/drobo-utils-doc", "." ] readme="" @@ -117,6 +123,24 @@ al.addWidget(self.quit) self.connect(self.quit, QtCore.SIGNAL('clicked()'), self.hide) + #self.findbt = QtGui.QPushButton('Find',self) + #al.addWidget(self.findbt) + #self.connect(self.findbt, QtCore.SIGNAL('clicked()'), self.__search) + + + def __search(self): + """ + search is for finding a string in a text document being displayed. + STATUS: totally borked. + """ + text, ok = QtGui.QInputDialog.getText(self, self.tr("Search Text"), + self.tr("Look for:"), QtGui.QLineEdit.Normal, + self.lastsearch) + if ok and not text.isEmpty(): + self.lastsearch = QtCore.QString(text) + self.lscursor = self.find(self.lastsearch,0) + self.lscursor.setPosition(0) + class DroboGUI(QtGui.QMainWindow): """ GUI for a single Drobo, start one for each drobo. """ @@ -462,7 +486,6 @@ def __renameDialog(self): - settings=self.drobo.GetSubPageSettings() text, ok = QtGui.QInputDialog.getText(self, self.tr("QInputDialog.getText()"), self.tr("New name:"), QtGui.QLineEdit.Normal, Modified: trunk/README.txt =================================================================== --- trunk/README.txt 2009-05-19 11:45:25 UTC (rev 251) +++ trunk/README.txt 2009-05-20 01:03:51 UTC (rev 252) @@ -457,6 +457,7 @@ Chris Atlee: the proper debian packaging. Brad Guillory: some help with diagnostics and patches. Joe Krahn: lots of inspiration. + Andy Grover: some elegance cleanups. Administrivia Modified: trunk/TODO =================================================================== --- trunk/TODO 2009-05-19 11:45:25 UTC (rev 251) +++ trunk/TODO 2009-05-20 01:03:51 UTC (rev 252) @@ -1,8 +1,12 @@ + in no particular order: -Name command support in GUI +Find Dialog -- in ShowFile +Review feature bits, mis-marked? 28 +test with old firmware... + Alerting... -- save config... .. SMTP forwarder: @@ -55,7 +59,7 @@ -- python bindings for parted... http://dcantrel.fedorapeople.org/pyparted/ -Revision date: 2008/12/27 +Revision date: 2009/05/19 copyright: This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-05-19 11:45:32
|
Revision: 251 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=251&view=rev Author: peter_silva Date: 2009-05-19 11:45:25 +0000 (Tue, 19 May 2009) Log Message: ----------- added tool tips to all relevant buttons. Modified Paths: -------------- trunk/DroboGUI.py Modified: trunk/DroboGUI.py =================================================================== --- trunk/DroboGUI.py 2009-05-19 03:12:31 UTC (rev 250) +++ trunk/DroboGUI.py 2009-05-19 11:45:25 UTC (rev 251) @@ -399,6 +399,7 @@ self.Format.Formatbutton = QtGui.QPushButton('Format (Erases All Data!) ', self.Format) + self.Format.Formatbutton.setToolTip("Configure a Drobo for use") flay.addWidget(self.Format.Formatbutton,6,0,1,-1) self.tab.addTab(self.Format, "Format") @@ -480,6 +481,7 @@ # Set the tool colors to grey, to indicate non-functional... # self.Tools.Standbybutton = QtGui.QPushButton('Shutdown', self.Tools) + self.Tools.Standbybutton.setToolTip( 'Unmount file systems, and turn Drobo off (DRI calls this standby)' ) self.Tools.Standbybutton.setCheckable(False) tlay.addWidget(self.Tools.Standbybutton,0,0,1,1) @@ -489,6 +491,7 @@ w=self.Tools.Standbybutton.width() self.Tools.Blinkybutton = QtGui.QPushButton('Blink Lights', self.Tools) + self.Tools.Blinkybutton.setToolTip( 'Make a light show (totally harmless)' ) self.Tools.Blinkybutton.setCheckable(False) tlay.addWidget(self.Tools.Blinkybutton,0,1,1,1) @@ -496,34 +499,40 @@ self.drobo.Blink) self.Tools.Renamebutton = QtGui.QPushButton('Rename', self.Tools) + self.Tools.Renamebutton.setToolTip( "Change the Drobo's name (does not affect mount points.)" ) self.Tools.Renamebutton.setCheckable(False) tlay.addWidget(self.Tools.Renamebutton,1,0,1,1) self.connect(self.Tools.Renamebutton, QtCore.SIGNAL('clicked()'), self.__renameDialog) self.Tools.Updatebutton = QtGui.QPushButton('Update', self.Tools) + self.Tools.Updatebutton.setToolTip( "See if new firmware is available." ) tlay.addWidget(self.Tools.Updatebutton,1,1,1,1) self.connect(self.Tools.Updatebutton, QtCore.SIGNAL('clicked()'), self.checkup) Registerbutton = QtGui.QPushButton('Register', self.Tools) + Registerbutton.setToolTip( "Report for warranty service." ) Registerbutton.setStyleSheet( "QWidget { color: gray }" ) Registerbutton.setCheckable(False) tlay.addWidget(Registerbutton,2,0,1,1) Diagbutton = QtGui.QPushButton('Diagnostics', self.Tools) + Diagbutton.setToolTip( "Have Drobo write a diagnostics file to /tmp" ) Diagbutton.setCheckable(False) tlay.addWidget(Diagbutton,2,1,1,1) self.connect(Diagbutton, QtCore.SIGNAL('clicked()'), self.__diags) - Diagbutton = QtGui.QPushButton('Show Diag', self.Tools) - Diagbutton.setCheckable(False) - tlay.addWidget(Diagbutton,3,0,1,1) - self.connect(Diagbutton, QtCore.SIGNAL('clicked()'), self.__printDiagFile) + DiagShowbutton = QtGui.QPushButton('Show Diag', self.Tools) + DiagShowbutton.setToolTip( "Show a decoded diagnostics file" ) + DiagShowbutton.setCheckable(False) + tlay.addWidget(DiagShowbutton,3,0,1,1) + self.connect(DiagShowbutton, QtCore.SIGNAL('clicked()'), self.__printDiagFile) - DiagLdbutton = QtGui.QPushButton('Load Firmware', self.Tools) - DiagLdbutton.setCheckable(False) - tlay.addWidget(DiagLdbutton,3,1,1,1) - self.connect(DiagLdbutton, QtCore.SIGNAL('clicked()'), self.__loadFirmware) + FwLdbutton = QtGui.QPushButton('Load Firmware', self.Tools) + FwLdbutton.setToolTip( "Pick your own firmware (use Update normally)" ) + FwLdbutton.setCheckable(False) + tlay.addWidget(FwLdbutton,3,1,1,1) + self.connect(FwLdbutton, QtCore.SIGNAL('clicked()'), self.__loadFirmware) self.Tools.progress = QtGui.QProgressBar(self.Tools) #self.Tools.progress.setMinimumWidth(2*w) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-05-19 03:12:40
|
Revision: 250 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=250&view=rev Author: peter_silva Date: 2009-05-19 03:12:31 +0000 (Tue, 19 May 2009) Log Message: ----------- Added arbitrary firmware load support to GUI. Modified Paths: -------------- trunk/Drobo.py trunk/DroboGUI.py Modified: trunk/Drobo.py =================================================================== --- trunk/Drobo.py 2009-05-19 03:09:17 UTC (rev 249) +++ trunk/Drobo.py 2009-05-19 03:12:31 UTC (rev 250) @@ -324,9 +324,6 @@ print "%s fw[6] is not armmarvell." % self.char_dev_file raise DroboException - - - def __del__(self): Modified: trunk/DroboGUI.py =================================================================== --- trunk/DroboGUI.py 2009-05-19 03:09:17 UTC (rev 249) +++ trunk/DroboGUI.py 2009-05-19 03:12:31 UTC (rev 250) @@ -449,11 +449,16 @@ self.diagdialog = ShowText(datam,False) self.diagdialog.show() + def __loadFirmware(self): + fileName = QtGui.QFileDialog.getOpenFileName(self, + self.tr("QFileDialog.getOpenFileName()"), + '/root/.drobo-utils', + self.tr("All Files (*);;Text Files (*.txt)")) + if not fileName.isEmpty(): + if self.drobo.PickFirmware(str(fileName)): + self.drobo.writeFirmware( self.Tools.progress.setValue ) + - - - - def __renameDialog(self): @@ -515,6 +520,11 @@ tlay.addWidget(Diagbutton,3,0,1,1) self.connect(Diagbutton, QtCore.SIGNAL('clicked()'), self.__printDiagFile) + DiagLdbutton = QtGui.QPushButton('Load Firmware', self.Tools) + DiagLdbutton.setCheckable(False) + tlay.addWidget(DiagLdbutton,3,1,1,1) + self.connect(DiagLdbutton, QtCore.SIGNAL('clicked()'), self.__loadFirmware) + self.Tools.progress = QtGui.QProgressBar(self.Tools) #self.Tools.progress.setMinimumWidth(2*w) tlay.addWidget(self.Tools.progress,4,0,1,2) This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pet...@us...> - 2009-05-19 03:09:24
|
Revision: 249 http://drobo-utils.svn.sourceforge.net/drobo-utils/?rev=249&view=rev Author: peter_silva Date: 2009-05-19 03:09:17 +0000 (Tue, 19 May 2009) Log Message: ----------- Documented a bit about Drobo Pro support. Modified Paths: -------------- trunk/README.txt Modified: trunk/README.txt =================================================================== --- trunk/README.txt 2009-05-19 01:44:38 UTC (rev 248) +++ trunk/README.txt 2009-05-19 03:09:17 UTC (rev 249) @@ -302,7 +302,33 @@ It would be fun to set the LunSIZE to 8 TiB and test it out... +Drobo Pro +--------- +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: +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 + +1. Configure iscsi ip address via drobo dashboard on win/osx +2. Install open-iscsi (http://www.open-iscsi.org/): sudo apt-get install open-iscsi +3. Connect the dbpro to host machine via iscsi +4. Query dbpro's id: sudo iscsiadm --mode discovery --type sendtargets --portal 192.168.2.80 +5. Copy the id string returned by iscsiadm, something like "iqn.2005-06.com.datarobotics:drobopro.tdb091840080.node0" +6. Connect to the dbpro: sudo iscsiadm --mode node --targetname iqn.2005-06.com.datarobotics:drobopro.tdb091840080.node0 --portal 192.168.2.80:3260 --login + +If everything went well, your dbpro should show up under /dev. Also +check /var/log/messages to confirm that the iscsi device connected +successfully. + +After that, drobo-utils should be able to detect the Drobo and manage +it over ethernet. + + Firmware Upgrades ----------------- @@ -381,6 +407,8 @@ After you resize luns, droboview gets confused, you need to exit and restart. +We have a report that dumping diagnostics does not work over firewire. +Work-around: connect via USB. Building debian & ubuntu packages --------------------------------- This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |