I’m trying to get a 1220SA sata raid controller card working under Ubuntu 7.10 Gutsy. I have a copy of the adp3132.rhel4.x86_64.rpm but I cannot seem to get it to install. Can someone point me in the right direction? I’ve gone so far as to unzip the rpm and I’m poking around through the installer script but it is quite a large file and I’d hate to mess something up.

thanks in advance for any help you can provide me.

 Jason,

You are trying RHEL4 driver rpm on ubuntu which will not work as the driver rpm is specific to a particular OS version and tied to that OS’s Vermagic.  What I would suggest is to try using the SHIM rpm package instead. The SHIM package is available at the same downloads page under “linux source code”. Install the rpm and follow the instructions to build your own module obj, img and driver rpms for your OS.  To use the SHIM package you need to have kernel sources for the Linux version you are using.

I installed Adaptec Storage Manager Ver 5.20 in a RHEL5 machine. A RAID 10 array is configured and attached to a HostRAID ESB2 controller.

I can see the controller and the array using the GUI. But arcconf doesn’t see controller. For example, ‘./arcconf GETSTATUS 0′ results in ‘Controllers found: 0. Invalid controller number.’.

Kavan,

Since you are using HostRAID controller, you need to use to hrconf instead of arcconf. Please try “hrconf getstatus 1″ and it should work. You can get the hrconf utility from www.adaptec.com/support which is part of Storage Management downloads.

How do I update the BIOS of my Adaptec 3405 from Adaptec Storage Manager on Ubuntu server? I don’t want to have to reboot to DOS. Thanks

Thanks for raising this Roger - using DOS for the firmware upgrades can be a right pain especially as many systems now don’t have floppy drives. The good news is you can do this either from the Adaptec Storage Manager GUI or from the arcconf command line tool. For either method, start by downloading the firmware (as of 12/12/07 the firmware is B15323). Extract / transfer the files ending with a “.ufi” extension to the Linux system.

Before following either procedure, I should add some wise words - please backup any important data and plan the process so that downtime will not detrimentally impact users. 

Using the GUI - start the Adaptec Storage Manager (ASM) GUI and login to ASM using root credentials. On the left side of the screen, right click on “direct attached storage”

- From the drop down menu, select the option “Update Controller Images”. This will start the ROM update wizard, click next.

- On the “choose the ROM update image files” select “add” and browse to the location of the .ufi files you downloaded. There will either be two or four files to select depending on the controller (two for the 3405S). Select all the available files - multiple files are selected by holding down CTRL. Click next.

- The relevant controller should be displayed. (Note that Adaptec Storage Manager can monitor many systems from one GUI. If you have multiple machines with 3405 controllers they will all appear and you can select which of these you wish to upgrade). Select the controller(s) by clicking the check box beside it / them, “next” to the final confirmation screen and then “apply”. The firmware updrade should proceed.

Note if the controller is greyed out in the screen above, this is either because the controller is already running this version of firmware or you are downgrading it. In this case holding ctrl while selecting the controller will force the update to continue (use with caution).

Using the command line utility “arcconf”

- After downloading / extracting the UFI files change directory to /usr/StorMan and as root execute the command line utility “arcconf ROMUPDATE <controller number> <base name>” so in my system with a single 3405 and my ufi files in directory /firmware, the syntax would be “arcconf ROMUPDATE 1 /firmware/AS3405″. When prompted, confirm with “y” and the upgrade should proceed.

 I hope this is a help. If you have any issues then please let me know and I’ll do my best to help.

thanks for reading, Phil

 I have a server running 64bit Ubuntu 7.10 with a 2020ZCR using the aacraid kernel module. I’m trying to figure out how to check the status of the array, but I have been unable to find anything that works. Does Adaptec have some sort of utility that I can use?

That’s a great question Brian and thanks for submitting it. As it happens, I’ve just responded to Philippe from France who was asking something similar although there are a few differences since you are using an earlier product.

Under Storage Manager downloads for the 2020ZCR on our support site, version 4.30 build 16038 of Adaptec Storage Manager is listed however I would suggest using the newer 5.20 build 17414 version for Linux x64 which is posted under our later products. You can download this from any of the newer Unified Serial products for example here :-

http://www.adaptec.com/en-US/downloads/storage_manager/sm?productId=SAS-3405&dn=Adaptec+RAID+3405 

The newer version resolves an issue when converting the downloaded rpm file to deb format using the “alien” command - with version 4.30, alien doesn’t recognise the machine architecture x86_64 as valid, it is expecting amd64. Secondly the later version ships with the libraries that Adaptec Storage Manager needs to use and drops the dependency on having the right version of libstdc++ installed.

If after downloading, you can follow the steps in my response to Philippe (titled “How do I get Adaptec Storage Manager to work with Ubuntu 7.10?”) then it should work.

You didn’t mention if you were using the graphical desktop. If you are then you could use the GUI interface as described in my other note. If not, then you can still monitor the array using either the arcconf command line utility or you can install ASM on a different machine which does have a graphical desktop (Linux or Windows) and add the Ubuntu machine as a remotely managed system (in this case, if you are using the firewall, you may need to open port 34571).

Please do come back to let us know how this goes.

Thanks for reading,

 Phil

Working for a client who has a 2110S installed under Slackware Linux. They would like to rebuild a broken RAID-1 array without shutting down and rebooting the server (to use SMOR). I have been unable to find a Storage Manager download on the Adaptec website that lists support for the 2110S. Can you provide a URL to an appropriate distribution of Storage Manager? Thanks in advance!

The following suggestions are untested, any RAID manipulation carried out incorrectly will lead to loss of data.

The 2110S belongs to the Babylon class of RAID controllers.. This family of Adapters includes all the DPT I2O based controllers and the Adaptec Babylon 3210S, 3410S, 2000S, 2005S, 2010S, 2015S, 2100S, 2110S & 2400A. You will find that Storage Manager products for any one of these adapters will generally work for the entire family, albeit the specific versions may have not been specifically tested together.

In that vein, you may wish to try the Storage Manager for the 2400A located at http://www.adaptec.com/en-US/downloads/storage_manager/sm?productId=AAR-2400A&dn=Adaptec+ATA+RAID+2400A; but I suspect you will need to search for compatibility libraries in your version of Linux as the last build of this product was for RedHat 7.3 (a 2.4 based kernel).

It should not matter if you are using the dpt_i2o or the i2o_block Linux drivers, the ioctls are compatible with the dpteng middleware that ties all the management utilities together and acts as the traffic cop that communicates to the Adapters.

Also, Markus Lidel, the author of the i2o_block driver, was kind enough to continue to support our raidutil, the Storage Manager Command Line Utility, under Linux. We had released raidutil and the dpteng middleware into the public domain. You will find his effort located at http://i2o.shadowconnect.com/download.php. We could not release the GUI portion into the public domain because of Library Licensing issues with a third party. The dpteng middleware that is part of Marcus’ package is supposed to be compatible with the GUI.

Good Luck!

Sep 26 04:12:08 bu1 kernel: aacraid:ID(0:04:0); Error Event [command:0×2a]
Sep 26 04:12:08 bu1 kernel: aacraid:ID(0:04:0); Medium Error [k:0×3,c:0×3,q:0×0]
Sep 26 04:12:08 bu1 kernel: aacraid:ID(0:04:0); Peripheral Device Write Fault

These messages are from the perspective of Adaptec RAID controller’s Firmware’s kernel (not from the Linux Kernel) and relate to the Physical Targets and their transactions over the I/O transport. Newer controller firmware reports these messages via our logging applications. In this specific case a physical hard drive connected to Target ID 4 of your Adaptec RAID controller reports a medium error message. Medium refers to the formatted storage surface of the drive.

I would suggest evaluating the physical drive’s health. Run a RAID verify task for instance, if the target is bad it would then be taken offline requiring it’s replacement, or it could merely have one bad block, and it has already been remapped and thus this message means little in that case.

I would also suggest contacting technical support, they may have additional tools and suggestions and can help you  to identify the physical device that has caused the problem.

386 version of aaccli works on x86_64 installations.

The replacement for aaccli, which was only made available in a 32 bit version, is ArcConf which is available in 32 and 64 bit versions. You may be able to use ArcConf on legacy products, however, we recommend using the tool that was shipped or updated with the card.

Technical Support should be contacted, there is probably an internal error in the Firmware or Hardware that should be addressed.

Specifically, BlinkCode EF is BLINKLED_NMI_HANDLER_FAILURE can be triggered by an internal NMI that has no characterized combinations of hardware failure to induce it.

Possible in-the-field causes, a WAG:

1) bad power supply
2) overheating
3) conductive materials on the cards
4) corrosion
5) poor PCI bus connections, bad connectors
6) chip failures on the cards
7) Firmware failing to cover all causes of NMI activities (bug?)
8 ) ?