1220SA adp3132 SATA raid controller driver for ubuntu
Posted in General by Anil RavindranathJason Emanuel wrote:-
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.
December 28th, 2007 at 7:30 pm
Hi Anil,
Thanks for the help. Do you guys have a 64 bit source package available? Here’s the error message I receive:
Package build failed. Here’s the log:
dh_testdir
dh_testdir
dh_testroot
dh_clean -k -d
dh_installdirs
dh_installdocs
dh_installchangelogs
find . -maxdepth 1 -mindepth 1 -not -name debian -print0 | \
xargs -0 -r -i cp -a {} debian/adaptec-adp3132
dh_compress
dh_makeshlibs
dh_installdeb
dh_shlibdeps
dh_gencontrol
dpkg-gencontrol: error: current build architecture amd64 does not appear in package’s list (i386)
dh_gencontrol: command returned error code 65280
make: *** [binary-arch] Error 1
find Adaptec_adp3132-OpenBuild -type d -exec chmod 755 {} ;
find: Adaptec_adp3132-OpenBuild: No such file or directory
rm -rf Adaptec_adp3132-OpenBuild
Thanks
January 4th, 2008 at 4:10 pm
Hi Anil,
Thanks for your help. I’ve managed to get the packages installed on CentOS 5.0 but when I run the ASM and fill in the root credentials i get a “user root could not be logged in” error. The contents of the RaidErr.log are as follows:
04 Jan 2008 10:55:20,466 [RaidMan:Console:Login:chocho] ERROR GUIManagementAgentRemote.doLogin:175 - Login failed
java.rmi.ServerError: Error occurred in server thread; nested exception is:
java.lang.UnsatisfiedLinkError: authenticateUser
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:382)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
at com.ibm.sysmgt.raidmgr.agent.GatekeeperRMI_Stub.login(Unknown Source)
at com.ibm.sysmgt.raidmgr.mgtGUI.GUIManagementAgentRemote.doLogin(GUIManagementAgentRemote.java:146)
at com.ibm.sysmgt.raidmgr.mgtGUI.ManagedSystem.doLogin(ManagedSystem.java:211)
at com.ibm.sysmgt.raidmgr.mgtGUI.LoginHelper.doLoginToLocal(LoginHelper.java:682)
at com.ibm.sysmgt.raidmgr.mgtGUI.LoginHelper.doLoginToRemote(LoginHelper.java:115)
at com.ibm.sysmgt.raidmgr.mgtGUI.LoginHelper.doLoginToRemote(LoginHelper.java:91)
at com.ibm.sysmgt.raidmgr.mgtGUI.ManagedSystem$1.run(ManagedSystem.java:703)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.UnsatisfiedLinkError: authenticateUser
at com.ibm.sysmgt.raidmgr.agent.ManagementAgent.authenticateUser(Native Method)
at com.ibm.sysmgt.raidmgr.agent.SecurityManagerRMI.login(SecurityManagerRMI.java:432)
at com.ibm.sysmgt.raidmgr.agent.GatekeeperRMI.login(GatekeeperRMI.java:142)
at com.ibm.sysmgt.raidmgr.agent.GatekeeperRMI_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
… 1 more
Any advice?
February 18th, 2008 at 8:15 am
Hi Jason, not sure if anyone came back to you on this - if not sorry for the delay. I’ve had the same problem in the past caused by ASM using older versions of the libstc++ libraries than those shipped with the distribution.
Can you try with the latest version of ASM (version 5.20) which ships with the appropriate version of the libstdc++ library?
If you look under our support downloads section under one of the more recent controllers e.g. the 3805,
http://www.adaptec.com/en-US/downloads/storage_manager/sm?productId=SAS-3805&dn=Adaptec+RAID+3805
You’ll see the rpm’s for version 5.20.
There’s a posting elsewhere on this blog describing the steps to convert to a deb package and a changes to get the ASM agent to start in run level 2.
Alternatively you could do an ldd of the two so libraries in the /usr/StorMan directory and install the appropriate older version of libstdc++ to resolve missing dependencies.
cheers, Phil