monline

The link takes you to the relevant post on the Adaptec Linux blog where you can pick up all the bits necessary to make ASM work on Ubuntu/Debian. I tried to install asm_linux_x86_v5_30_17509.rpm on an Ubuntu 9.10 (Karmic) system with the Adaptec RAID 3405 controller and 4 Samsung SATA drives. Here's what worked for me ...

1. Download the RPM from the Adaptec site.
2. Install alien and create a DEB package:
   
   apt-get update
apt-get install alien
alien --scripts asm_linux_x86_v5_30_17509.rpm
   This will print one error message ("error: incorrect format: unknown tag"), but it's insignificant. It merely warns you that the %{COPYRIGHT} package attribute could not be found in the RPM and the alien command tried to retrieve it. You can verify this by executing alien with the additional -v (verbose) switch.
3. Install the DEB package:
   
   dpkg -i storman_5.30-17510_i386.deb
   (Note: for some reason the package version became "5.30-17510" ... despite the fact that the filename suggests it should be "5.30-17509". Never mind.)
   You'll get a few errors during the package installation:
   
   Selecting previously deselected package storman.
(Reading database ... 45423 files and directories currently installed.)
Unpacking storman (from storman_5.30-17510_i386.deb) ...

Adaptec
Version 5.30

Setting up storman (5.30-17510) ...
starting Adaptec Storage Manager agent ...
cut: fields and positions are numbered from 1
Try `cut --help' for more information.
cut: fields and positions are numbered from 1
Try `cut --help' for more information.

/var/lib/dpkg/info/storman.postinst: line 17: chkconfig: command not found

Installation completed successfully.
The application can be started by running: /usr/StorMan/StorMan.sh
4. Fix the above errors.
   First: change every occurance of the cut -b0-6 command into cut -b1-6 in the /etc/init.d/stor_agent script.
   Second: change the "Default" lines (in the same script) from this:
   
   # Default-Start:    3 5
# Default-Stop:     0 1 2 6
   Into this:
   
   # Default-Start:    2 3 5
# Default-Stop:     0 1 6
   Third: install the necessary symlinks to enable autostart of the agent.
   
   update-rc.d stor_agent defaults
5. You should be all set by now ... but there's one more thing.
   The agent is a Java application and by default it binds to the IPv6 address of your server. There's a pretty good chance that this will screw up your connection attempts using the GUI manager application. To work around it, you should alter the following line in /usr/StorMan/StorAgnt.sh from this:
   
   $JAVA_BIN/java -Djava.compiler=NONE -cp $INSTDIR/RaidMan.jar com.ibm.sysmgt.raidmgr.agent.ManagementAgent $*
   Into this:
   
   $JAVA_BIN/java -Djava.net.preferIPv4Stack=true -Djava.compiler=NONE -cp $INSTDIR/RaidMan.jar com.ibm.sysmgt.raidmgr.agent.ManagementAgent $*
6. Now you can start the agent (or reboot the server in case you want to test the autostart of the agent):
   
   invoke-rc.d stor_agent start

In the Adaptec Linux blog somebody wrote that you need to add the /usr/StorMan path to the /etc/ld.so.conf file and run ldconfig, since the ASM relies on libstdc5++ and it's not part of Ubuntu 9.10 (it was still available in Jaunty, but they've removed it from Karmic). Fortunately ASM ships with this lib and the ld.so.conf workaround was meant to use this shipped lib. However the agent startup script (StorAgnt.sh) in ASM v5.3.0 b17509 already takes care of this by adding this lib to the LD_PRELOAD environment variable before starting up the agent. But in case you wish to use the commandline utilities too, you should still do the ld.so.conf trick, since there're a number of binaries/libs in /usr/StorMan that depend on the libstdc++.so.5 lib. These are:

After you've finished installing ASM, you can get the status of your controller by executing something like this: