/ Documentation / Einarc / Xhtml / Reference manual

Einarc: Reference manual

1. Concept

Hardware RAID controllers are complex devices: essentially, it’s a computer inside a computer. It has it’s own processor (or may be processors), it usually has it’s own RAM, and, most important, it runs its own software, which is usually a fairly complex operating system that manages physical discs, hides all the RAID magic behind the curtains and allows the host operating system to see only few logical discs.

Unfortunately, most of the RAID controllers are proprietary. It’s a well-known fact that physical discs used on controller A are incompatible with some other controller B (even worse, they can be incompatible between various revisions of firmware of controller A). RAID’s firmware hides all the intricate management of discs from the system administrator. Administrator can control RAID using either:

  • BIOS OPROM, which is available by pressing some magic key when the computer’s booting.

    • Pros: it’s basic and solid method, it works, it doesn’t require any OS installed (can be done before OS installation), it works even if OS is broken, etc.
    • Cons: it requires rebooting of computer when trying to edit RAID or even to check/monitor its state (which is hard to do remotely without KVM-over-IP or similar solution), it requires manual intervention, it’s not scriptable (= it’s hard to create the same RAID configuration on 1000 machines), and, most of all, every RAID controller model or vendor has his own version of such OPROM utility, incompatible with each other even in terms they use.
  • Some management utilities, running in OS. Such utilities are mostly proprietary, provided by vendors, available in binary-only form.

    • Pros: they usually include command-line interface (they’re scriptable), they’re suitable to call regularly and automatically to monitor status of discs, they don’t require rebooting, etc.
    • Cons: of course, they require booted OS to run, and, worst of all, they’re also very incompatible with each other.

Einarc project tries to solve such problem: provide a unified, solid interface to manage all possible storage devices.

2. Architecture

Einarc unifies various RAIDs and storage devices, providing a simple object interface for end-user. Inside, it works as a proxy, translating commands from that object interface to RAID-specific commands for it’s proprietary CLI, and back, it translates response from proprietary CLI into unified answer.

Figure 1. Einarc architecture diagram

Einarc architecture diagram

Support for various RAIDs is implemented as classes. Each class has to implement a couple of methods that would translate requests.

  • Common unit of size used is Megabyte = 1024 * 1024 bytes. Various adapters provide various interfaces and size units, so X megabytes on one adapter may differ from X megabytes on some other adapter.

3. Supported devices

Currently, there are following modules available:

  • adaptec_aaccli — supports older Adaptec SCSI RAID controllers, such as Adaptec SCSI RAID 2230SLP, Adaptec SCSI RAID 2130SLP, Adaptec SCSI RAID 2120S, Adaptec SCSI RAID 2020ZCR, Adaptec SCSI RAID 2025ZCR.
  • adaptec_arcconf — supports newer Adaptec SAS/SATA RAID controllers, such as Adaptec RAID 5405, Adaptec RAID 5445, Adaptec RAID 5805, Adaptec RAID 5085, Adaptec RAID 51245, Adaptec RAID 51645, Adaptec RAID 52445, Adaptec RAID 3405, Adaptec RAID 3085, Adaptec RAID 3805, Adaptec RAID 31205, Adaptec RAID 31605, Adaptec RAID 2405, Adaptec RAID 2045, Adaptec RAID 4000, Adaptec RAID 4800SAS, Adaptec RAID 4805SAS, Adaptec RAID 6405.
  • amcc — supports all AMCC/3ware controllers, such as 3ware 7000 series, 3ware 8000 series, 3ware 9690SA, 3ware 9650SE, 3ware 9550SX, 3ware 9500S, 3ware 8506.
  • areca — supports all Areca SATA RAID controllers, such as ARC-1110, ARC-1120, ARC-1130, ARC-1160, ARC-1130ML, ARC-1160ML, ARC-1170, ARC-1200, ARC-1210, ARC-1220, ARC-1230, ARC-1260, ARC-1231ML, ARC-1261ML, ARC-1280ML, ARC-1280.
  • lsi_megacli — supports newer LSI MegaRAID SAS/SATA RAID controllers, such as LSI MegaRAID SAS 8208ELP, LSI MegaRAID SAS 8208XLP, LSI MegaRAID SAS 8204ELP, LSI MegaRAID SAS 8204XLP, LSI MegaRAID SAS 84016E, LSI MegaRAID SAS 8704ELP, LSI MegaRAID SAS 8708ELP, LSI MegaRAID SAS 8300XLP, LSI MegaRAID SAS 8708EM2, LSI MegaRAID SAS 8888ELP, LSI MegaRAID SAS 8880EM2, LSI MegaRAID SAS 2208, LSI MegaRAID SAS 9240, LSI MegaRAID SAS 9260 as well as rebranded copies of these controllers from Dell, HP and Intel, as well as all on-board or daughterboard products based on LSI SAS 1078 chipset.
  • lsi_megarc — support older LSI MegaRAID SCSI/SATA RAID controllers, such as LSI MegaRAID SATA 150-4 (523), LSI MegaRAID SATA 150-6 (523), LSI MegaRAID SATA 300-8X, LSI MegaRAID SATA 300-8XLP, LSI MegaRAID SATA 300-4XLP, LSI MegaRAID SCSI 320-0 (520-0 CH), LSI MegaRAID SCSI 320-0X (530), LSI MegaRAID SCSI 320-1 (520-1CH), LSI MegaRAID SCSI 320-1LP (520-1 CH LP), LSI MegaRAID SCSI 320-2 (518), LSI MegaRAID SCSI 320-2E, LSI MegaRAID SCSI 320-2X (532), as well as rebranded copies of these controllers from Dell, HP and Intel, as well as all on-board or daughterboard products based on LSI MegaRAID 160/320 or 150/300 chipset.
  • lsi_mpt — Fusion/MPT, now branded as LSI MPT design of HBAs, available in such adapters as LSI20160, LSIU320, LSI20320-R, LSI20320IE, LSI21320-R, LSI22320-R, LSI22320SE.
  • software — Linux software RAID device (md), for a sake of completeness.

This is not a complete list. To check if your adapter is supported, just run ./configure or einarc-install without options to select all available modules. There’s a good chance that your adapter would be supported too.

3.1. S.M.A.R.T.

Currently only a few modules support S.M.A.R.T. technology and are capable of retrieving its information.















smartmontools >= 5.39
requires at least one logical drive

4. Installation

Currently, Einarc is a sub-project of Inquisitor hardware testing framework and can be downloaded either bundled with Inquisitor itself or from its own mini-homepage. Alternatively, your favourite distributed may provide you with pre-built package.

4.1. Manual installation

After downloading, extract the contents of tarball (this would yield a directory with sources), then run ./configure. You can use the following options:

target to build for; default is selected by looking up architecture of current host
where to place user executables
ruby share directory
ruby binary extensions directory
proprietary extensions directory

a comma-separated list of storage support modules to build:

  • all — SPECIAL: build all available modules, default
  • auto — SPECIAL: autodetect which modules are required — experimental feature, added since v1.4, tries to make an automatic guess by analysing PCI IDs of machine where you run ./configure; requires lspci to run. If in doubt, just use "all" — it will download everything, all CLIs not usable on current machine just won’t be used.
  • lsi_megarc — older LSI MegaRAID SCSI/SATA adapters
  • adaptec_arcconf — newer Adaptec adapters that use arcconf
  • amcc — 3Ware/AMCC RAID 7/8/9xxx/95xxx series controllers that use tw_cli
  • lsi_megacli — newest LSI MegaRAID SAS adapters
  • adaptec_aaccli — older Adaptec SCSI adapters that use aaccli
  • areca — Areca adapters
-h, --help
show help

After running ./configure with options, file Makefile.config would be created. You can check it out and edit by hand if necessary. Then run make to start a build process. In fact, Einarc is written in a script language and does not need build, but we use the build stage to download all the proprietary CLIs that would be required to support requested controllers.

After downloading, unpacking and preparing all required tools, you can run make install (usually requires root privileges) to install Einarc in your system.

4.2. Package installation

Since version 1.4, it’s possible to package and install Einarc as pre-built binary package (rpm, deb) from major distribution repositories. Recommended name for a package is einarc.

After installation of package, all Einarc modules that don’t require proprietary CLIs are available (so far it’s only software module to control Linux software RAIDs), so in most case you’ll still have to download necessary proprietary CLIs to make Einarc useful. It can be done automatically on target machine by running einarc-install. It can be called with the same --modules option as in ./configure:


a comma-separated list of storage support modules to build:

  • all — SPECIAL: build all available modules, default
  • auto — SPECIAL: autodetect which modules are required — experimental feature, added since v1.4, tries to make an automatic guess by analysing PCI IDs of machine where you run ./configure; requires lspci to run. If in doubt, just use "all" — it will download everything, all CLIs not usable on current machine just won’t be used.
  • lsi_megarc — older LSI MegaRAID SCSI/SATA adapters
  • adaptec_arcconf — newer Adaptec adapters that use arcconf
  • amcc — 3Ware/AMCC RAID 7/8/9xxx/95xxx series controllers that use tw_cli
  • lsi_megacli — newest LSI MegaRAID SAS adapters
  • adaptec_aaccli — older Adaptec SCSI adapters that use aaccli
  • areca — Areca adapters

5. Command-line interface (CLI)

Simplest way to use Einarc is to use command-line interface. Einarc can be invoked using:

einarc [options] <object> <method> <parameters>


-V, --version
Print program version and exit.
Show short help text and exit.
-l, --list
List all adapters found in system and exit.
-h, --human
Force output in human-readable format: tables would have headers and they will be formatted with spaces to ensure fixed width fields. By default, Einarc outputs data in human-readable format if being called standalone from command-line and in tab-separated format when being called from a script. Using this option forces "humanized" format, even in script context.
-t, --type=TYPE
type (manufacturer) of RAID adapter; use -l (--list) option to list all types of supported adapters.
-a, --adapter=NUM
select the adapter if multiple adapters of a given type are present.

You can omit -t if there’s only one adapter type in the system. Omitting -a would select first available adapter of that type.

Refer to object interface description for particular objects.

Note that command-line interface is always ready to provide a hint. For example, one can forget almost everything and start with just calling "einarc". If there’s only one adapter available at the system, things can go as easy as:

$ einarc
Object not specified; available objects: logical, physical, log, adapter, firmware, task, bbu

If there’s more than 1 adapter in the system, one would get a message hinting that one should specify which adapter we’ll work with:

$ einarc
Multiple adapters exist: use --list to list all adapters, choose one and specify it with --type and --adapter
$ einarc --list
Type           Adapter #  Model                         Version
lsi_megacli    0          MegaRAID SAS PCI Express(TM)  8.0.1-0038
areca          1          ARC-1160                      PCI
$ einarc --type=areca
Object not specified; available objects: logical, physical, log, adapter, firmware, task, bbu

Let’s start with showing all logical drives. We don’t know what method we should choose, but Einarc will give a hint:

$ einarc logical
Command not specified; available commands: list, add, delete, clear, get, set
$ einarc logical list
#  RAID level   Physical drives                 Capacity     Device  State
1  5            0:1,0:2,0:4,0:5,0:8            762939.45 MB          normal
2  1+0          0:6,0:7                        190734.86 MB          normal
3  5            0:9,0:10,0:11,0:12,0:13       1907348.63 MB          normal
4  1+0          0:15,0:16                      476837.16 MB          normal

Note that Einarc’s output differs slightly when using Einarc in console manually or using Einarc’s output in a script. This is due to so called "humanize" option, which is turned on automatically in case of manual invocation from console. Note how output changes if we’ll simulate in-script output piping with simple cat:

$ einarc logical list | cat
1      5       0:1,0:2,0:4,0:5,0:8     762939.45       normal
2      1+0     0:6,0:7 190734.86       normal
3      5       0:9,0:10,0:11,0:12,0:13 1907348.63      normal
4      1+0     0:15,0:16       476837.16       normal

Einarc has switched to "machine-readable" output, tab-separated values in columns. It’s not as pretty for humans, but it’s very useful for script processing. For example, we’d like to get IDs of all RAID 5 arrays:

$ einarc logical list | cut -f1,2 | grep 5$ | cut -f1

More complex example: let’s check if a physical drive is hotspare drive or not. Such simple boolean flag is available as a property of physical object, and Einarc will give a hint on how to get it and when to add a reference to particular physical disc ID:

$ einarc physical
Command not specified; available commands: list, get, set
$ einarc physical get
Object identifier not specified
$ einarc physical list
ID      Model                    Revision       Serial                     Size     State
0:1     WDC WD2000JD-00          08.02D08       WD-WMAL00000001       190734.86 MB  1
0:2     WDC WD2000JD-00          08.02D08       WD-WMAL00000002       190734.86 MB  1
$ einarc physical get 0:1
Property not specified; available properties: hotspare
$ einarc physical get 0:1 hotspare

Getting a property of adapter is in fact even simpler: there shouldn’t be any IDs. Here we’ll get a list of all RAID levels a particular adapter supports:

$ einarc adapter
Command not specified; available commands: info, restart, get, set
$ einarc adapter get
Property not specified; available properties: coercion, raidlevels, alarm, rebuildrate
$ einarc adapter get raidlevels

6. Application programming interface (API)

Einarc’s libraries can be called directly with almost the same object terms as from the command-line interface.

Einarc is written in Ruby and thus can be used easily from this script language. Using Einarc API in your program takes a few simple steps:

6.1. Add libraries

Einarc modules should be loaded before use. Adding the following require statement would automatically load all available RAID support modules:

require 'einarc'

6.2. Listing available adapters

To find out which adapters are available, use:


This would return you an array of hashes, one element of array for each adapter found, for example:

[{:driver=>"areca", :version=>"PCI", :num=>1, :model=>"ARC-1160"}]

6.3. Create adapter objects

Instantiate a particular adapter object, for example:

a = RAID::Areca.new

6.4. Use adapter object methods

After adapter object a is created, one can use all the methods described in object interface using a simple convention.

  • If method does not return anything, it’s just

    a.object_method(all, other, arguments, ...)

    for example:

  • If method should return its data as Ruby objects (a hash, an array, an array of hashes, etc), then it should be called as

    a._object_method(all, other, arguments, ...)

    Note the beginning underscore. An example:

    => {"PCI product ID"=>"1160", "System Memory"=>"256MB/333MHz",
        "Current IP Address"=>"", "Controller Name"=>"ARC-1160",
        "BOOT ROM Version"=>"V1.39 2006-1-4  ", "CPU DCache Size"=>"32KB",
        "Main Processor"=>"500MHz", "Firmware version"=>"V1.39 2006-2-9  ",
        "PCI vendor ID"=>"17d3", "CPU ICache Size"=>"32KB",
        "Serial number"=>"XXXXXXXXXXXXXXXX"}
  • If method should print whatever strings Einarc CLI displays, it should be called as:

    a.object_method(all, other, arguments, ...)

    For example:

    PCI product ID          1160
    System Memory           56MB/333MHz
    Current IP Address

6.5. Error handling

All RAID-related activities raise an exception of class RAID::Error on error.

7. Object interface

Einarc exposes a relatively simple and straight-forward object model for an end-user.

Figure 2. Einarc objects

Einarc objects

Every computer (host) may have one or more adapters (object adapter). Adapters provide RAID services as logical discs (object logical) that are usually seen in OS as individual devnodes. Logical discs may include one or more physical discs (object physical). Physical discs are usually hidden from the OS and are accessible only through proprietary CLI. Adapters also may keep some history of what events happened in the past and what objects were involved (object log). Finally, adapters being little computers with their own operating system and multi-tasking may perform separate background tasks, such as building/rebuilding or checking of the array (object task).

Each of these objects have a couple of methods described below. Some of these objects have named properties that can be read using get and written using set. Some of the properties are read-only (only get would work), some are write-only (only set would work).

7.1. query (special)

A special function that lists available adapters of current model. This function is not called directly through object model, but called indirectly, iterating over all support drivers when performing an -l (--list) command line command to list all available and supported adapters.

Output is tab-separated strings in format:

Driver Adapter ID Adapter model Adapter serial number / version
lsi_megarc 00 MegaRAID SCSI 320-1 40LD/8SPAN
areca 01 ARC-1120 PCI

7.2. adapter

"adapter" is an object related to the controller card. It stores various settings with properties that can be read and wriiten with get and set and can be examined for general info with info command.


(mute, disable, enable) — mode of adapter’s beeper alarm
(0, 1)
(0-3) — a priority of rebuilding and other background tasks, 0 being the lowest (least percent of time slices goes to that tasks), 3 being the highest.


Gets general information about adapter. Information is returned as key-value pairs. Some keys are fixed and are consistent across all adapters:

  • Serial number
  • Firmware version
  • PCI vendor ID
  • PCI product ID
  • PCI subvendor ID
  • PCI subproduct ID

Other keys are adapter- and implementation-specific and thus vary.


several tab-separated lines in format

Name Value
Firmware Version 1L37
BIOS Version G119


name of property
value of property


  • name of property
  • value of property
none normally, error message if error happened

7.3. log

"log" is an object to access adapter’s event log in NVRAM.


Clears event log in NVRAM.

none normally, error message if error happened


Display full event log in NVRAM.


log entries, one per line, in following tab-separated format:

Entry ID YYYY-MM-DD HH:MI:SE Where it happened What happened
0 2006-12-04 14:13:24 ARC-1120-VOL#00 Create Volume
1 2006-12-04 14:13:24 Raid Set # 00 Create RaidSet


Posts a test message in log. Can be later read back to see that logging works.

none normally, error message if error happened; log list would now return at least this test message.

7.4. physical

"physical" is an object to access physical disc drives attached to adapter. It’s possible to get list with list and read and write it’s properties and settings with get and set.

Physical disc address is a:b, where a is channel number and b is a device number on that channel. Usually, it’s best to assume that it’s a string to pass through.


  • hotspare (0, 1) — if true, a physical drive is considered a global hotspare.
  • state (free, hotspare, logical drive ID) — shows that drive is either free, reserved for hotspare, or belongs to the one of the logical drives (numeric).


Shows a list of all physical disc drives attached to adapter.


info on one disc drive per line, tab-separated:

Physical disc address Drive vendor and model Drive version, revision, firmware, misc info Drive serial Drive size Drive state
0:1 WDC WD800JD-00J 05.01C05 WD-WMAM97310565 80000 hotspare
0:2 WDC WD1600JB-00EVA0 15.05R15 WD-WMAEK1016963 160000 0
1:7 WDC WD3200JD-00KLB0 08.05J08 WD-WMAMR1259708 320000 free


  • physical disc address
  • name of property
value of property


  • physical disc address
  • name of property
  • value of property
none normally, error message if error happened


  • physical disc address

SMART info for disc. One attribute per line, tab-separated:

Id Attribute Flag Value Worst Threshold Type Updated When failed Raw value
1 Raw_Read_Error_Rate 15 100 253 6 Pre-fail Always - 0
3 Spin_Up_Time 3 97 97 0 Pre-fail Always - 0
4 Start_Stop_Count 50 100 100 20 Old_age Always - 202
5 Reallocated_Sector_Ct 51 100 100 36 Pre-fail Always - 23
7 Seek_Error_Rate 15 75 60 30 Pre-fail Always - 31760414
9 Power_On_Hours 50 95 95 0 Old_age Always - 5065
10 Spin_Retry_Count 19 100 100 97 Pre-fail Always - 0
12 Power_Cycle_Count 50 100 100 20 Old_age Always - 202
187 Reported_Uncorrect 50 100 100 0 Old_age Always - 0
189 High_Fly_Writes 58 100 100 0 Old_age Always - 0
190 Airflow_Temperature_Cel 34 58 33 45 Old_age Always In_the_past 42
194 Temperature_Celsius 34 42 67 0 Old_age Always - 42
195 Hardware_ECC_Recovered 26 75 59 0 Old_age Always - 353642

7.5. logical

Logical drive is a virtual drive, set up on regions of one or several physical drives. It is referenced with a logical drive ID, a plain integer number.


  • raidlevel (passthrough, 0, 1, 5) — a RAID level of array or passthrough — a special logical disc without any RAIDs that will directly access single physical disc.
  • stripe — stripe size of logical drive in kilobytes; possible values vary with adapter, 64 is typical default.
  • cache (writeback, writethrough) — a write cache mode.
  • state (normal, degraded, initializing, migrating, rebuilding, checking) — state of array.


Displays a list of logical drives.


info on one logical drive per line, tab-separated:

Logical drive ID RAID level Physical discs included, comma-separated Capacity (MB) State
1 0 0:1 80000 normal
2 5 0:2,0:3,0:4 10000 degraded
3 passthrough 0:7 73400 normal


Creates one or more new logical drives.

  • RAID level (as in raidlevel property), for example 5
  • (optional) Physical discs to include, comma-separated, for example 0:2,0:3,0:4. By default, use all available physical discs. Various RAID levels place limits on what arrays can be created with a given set of discs. Obviously, passthrough can be created only on one physical disc.
  • (optional) Size of logical discs to create, comma-separated, for example 200,3500. By default, create one logical disc with maximal size. Not applicable while creating passthrough disc.
  • (optional) Properties, comma-separated pairs of name=value, for example stripe=64,cache=readahead.
none normally, error message if error happened.


Deletes a logical drive.

logical drive ID.
none normally, error message if error happened.


Deletes all logical drives. Leaves array of free physical discs, ready for creation of new array.

none normally, error message if error happened.


  • logical drive ID
  • name of property
value of property


  • logical drive ID
  • name of property
  • value of property
none normally, error message if error happened.

7.6. task

Tasks are processes that are executed in background on an adapter, such as building or checking the logical disc.


Displays a list of tasks.


info on one task per line, tab-separated:

Task ID Where What Progress
112 0 Bld/Vfy 0.0%
113 1:1 Checking 24.0%


Pauses further execution until all tasks are finished (it does so by waiting while regularly polling the task list for changes).


7.7. firmware

A special object that deals with adapter-related firmware reading/writing operations.


Extracts a firmware from the adapter into a file.

filename (would be overwritten)
none normally, error message if error happened.


Flashes a firmware from a file into the adapter.

none normally, error message if error happened.

8. History of releases

8.1. v2.0

  • New features:

    • Dedicated hotspare support ("hotspare add", "hotspare delete" methods)
    • Getting physical disc SMART attributes in unified form ("physical smart")
    • Adapter restart method to reset an adapter, stop all arrays and reinitialize them ("adapter restart")
    • Listing logical discs now also shows their /dev entries, if possible
    • Getting WWN and enclosure ID for physical drives (attributes "wwn" and "enclosure" for "physical" object, software only)
    • Getting adapter’s expanders ID and model (method "expanders" for "adapter" object)
    • Log dumping support ("log dump", for lsi_megacli only)
    • Enabling/disabling WriteCache support for logical and physical discs ("writecache" attribute for "physical" and "logical" object, software only)
    • Disabling powersaving support for logical and physical discs ("powersaving" attribute for "physical" and "logical" object, software only)
    • BBU support (arcconf)
  • Support for new adapters / chipsets, improved RAID autodetection:

    • Adaptec 2405, Adaptec 51645, Adaptec 5405Z, Adaptec 5445Z, Adaptec 5805Z, Adaptec 6405, Adaptec 6805, Adaptec 6805Q
    • Intel RS2BL040, Intel RS2BL080, Intel RS2WC040
    • LSI 53C896/897-based, LSI MegaRAID SAS 9240-4i, LSI MegaRAID SAS 9260, LSI SRCSASLS4I
    • SuperMicro SMC2108
  • User friendliness:

    • command line interface now hints what objects are available
    • most objects and methods can be abbreviated akin to UNIX commands (i.e. "physical list" ⇒ "pd ls", "logical hotspare delete" ⇒ "ld hs rm", etc)
    • adapter type and number specification can be omitted if there’s only one adapter in the system
    • more user-friendly error messages
    • output is "humanized" by default if we use real tty for output
    • added man pages: einarc(8), einarc-install(8), raid-wizard-clear(8), raid-wizard-passthrough(8), raid-wizard-optimal(8)
    • prevent lsi_megacli from littering its log files around by default
  • Bumped versions of proprietary CLI utilities:

    • Areca 1.9.0_120503
    • LSI MegaRC 1.11
    • LSI MegaCLI 8.07.07
    • 3Ware
    • ArcConf 1.1.20324
  • Compatibility issues:

    • Ruby 1.9 compatibility, 1.8 should be still supported
    • dash compatibility, bash is no longer required
    • Workarounds for proprietary CLI calls that require Linux kernel 2.6.x explicitly to work on kernel 3.x
    • Support for more than 26 logical discs (i.e. names like "sdaa" beyond "sda"-"sdz")
    • Dropped HAL support: querying now uses udev, procfs and sysfs
    • Explicitly disallowed software-RAID-on-top-of-hardware-RAID, added switch to disallow software-RAID-on-USB-mass-storage
  • Infrastructure and API changes:

    • Added testing framework using mock-up adapters CLI output, added tests for lsi_megacli and lsi_megarc
    • All output is done to @outstream by default (which can be overridden), not $stdout
    • Subversion → Git transition, Git maintenance support
  • Multiple bugfixes and minor improvements

8.2. v1.4

  • Support for post-build reconfiguration of proprietary CLIs and supporting modules. This allows Einarc to be supplied via usual binary packaging methods (rpm/deb): proprietary CLIs can be installed after binary package installation using special setup tool "einarc-install".
  • Experimental support for hardware RAID autodetection in both build-time (configure) and run-time (einarc-install).

8.3. v1.3

  • Support for 3ware / AMCC controllers by Andras Horvath.
  • Full read/write support of Linux software RAIDs.
  • Updated all proprietary utilities URLs, pumped up version numbers, fixed wrapper regular expressions to support new versions of CLIs.
  • Added new calculated fields in adapter_info: PCI product/subproduct and vendor/subvendor IDs. These allow precise identification of PCI devices related to adapters shown by Einarc.
  • Fuller BBU support for Adaptec adapters.
  • Multiple stability and build fixes (Makefile now supports parallel execution with "make -j").

8.4. v1.2

  • Support for new RAID devices: newer Adaptec adapters using arcconf.
  • New objects "bbu" and "firmware" are introduced: now it’s possible to get information about BBU and read/write firmware to supported adapters.
  • More strict "adapter info" report: it outputs serial number and tries to pinpoint a particular adapter using PCI IDs, if possible.
  • Updates for existing devices:

    • aaccli: now it downloads and uses later, more acceptable version, not linked against arts library. Note, however, that Adaptec_Storage_Manager-Linux_v2.10.00 is a huge ~36M download.
    • megacli: updated version to 1.01.27.
  • Multiple stability, metadata and rare occurance fixes for all modules.
  • Improved build system.
  • "raid-wizard-passthrough" can be used to handle smaller groups of HDDs (not all available devices).

8.5. v1.1

  • Added documentation in package
  • Brand-new configure: now everything can be controlled from command-line parameters, individual modules can be enabled/disabled at compile time.
  • Updated download/build mechanism: it asks for license agreement interactively. For non-interactive builds, just touch proprietary/agreed file.
  • Bugfixes in lsi_megarc, adaptec_aaccli modules
  • Compatibility with older Ruby (<1.8.6)

8.6. v1.0

  • First public release

9. Upgrade from 1.x to 2.0

Einarc v2.0 introduced API renovation, making it incompatible with previous versions. Changes include:

  • All library files are moved from raid/ to einarc/
  • Namespace for Einarc modules is changed from RAID to Einarc
  • Adapter discovery methods (query_adapters and list_adapters) are moved to Einarc module, instead of being class methods of RAID::BaseRaid class

If you were using 1.x API, generally you’ll have to do the following replacements to switch to 2.0:

Replacement In 1.x In 2.0
Library loading statement require 'raid/baseraid' require 'einarc'
Loading individual modules require 'raid/areca' require 'einarc/areca'
Querying for adapters RAID::BaseRaid::query_adapters Einarc::query_adapters
Adapter invocation RAID::Areca.new(...) Einarc::Areca.new(...)

10. Planned features

10.1. More devices

It’s possible to implement support for the following storage devices in Einarc:

  • FreeBSD’s GEOM software RAID
  • Adaptec raidutils
  • Chelsio TOE
  • Emulex dfc / lputil
  • ICP Vortex RAID Storage Console — icpcon
  • HighPoint RocketRAID hptraidconf
  • Some HP rebranded controllers using HP Array Configuration Utility CLI
  • LSI (former IBM, former Mylex) DAC960/DAC1100
  • Promise CLI
  • QLogic SANsurferCLI / qlremote

10.2. General features

Moreover, Einarc would be nice with:

  • Graphical UI
  • Web-based remote-accessible UI
  • Monitoring subsystem or plugin for Nagios