No storage controller

When omreport storage controller reports:

No controllers found

This maybe a solution:

modprobe mptctl

has to executed before /etc/init.d/dataeng starts.
Rainer Sabelka sabelka add iue dot tuwien dot ac dot at>

Another solution:

# make sure /sys is mounted
mount -t sysfs sys /sys
/etc/init.d/dataeng restart

Kernels greater the 2.6.24 and Perc 3/4 controller

The command omreport stroage controller does not work, see explanation on linux poweredge list:

Hello, some followup on this issue:

Le jeudi 2 juillet 2009 à 14:24, Brice Figureau a écrit :
> > Of course, the issue is not really in the commit but in the
> > library.
> > I've straced the dataeng service, and found that it tries to locate the
> > device by using /proc/devices.
> >
> > Before the aforementioned patch, since the kernel attributed a major to
> > the char device, it appeared in /proc/devices:
> > Character devices:
> > ...
> > 252 megadev
> >
> > But with this patch, it doesn't anymore, since there is no major
> > allocated.
> > So thinks the device is not there, even though a
> > correct /dev/megadev0 is created by udev.
> >
> > The real question is how to fix OMSA?
> >
> > If there are any Dell engineer/developper reading this, please please
> > fix your megalib code (in fact I even think this is code coming from
> > LSI).
> >
> > Meanwhile, I think we can fix this issue, by either reverting this patch
> > (it should revert cleanly on debian kernels). Or maybe it'd be possible
> > to use LD_LIBRARY_PRELOAD to load a read interceptor that could
> > rewrite /proc/devices on the fly...

It seems that OMSA (or another dell tool) recreate the file /dev/megadev0 
with what he thinks is the correct malor/minor (252/0). This of course 
won't work as major 252 is now used by usbmon.
The module megaraid_mm now uses the miscdevice.h register function to have 
an auto-allocated minor number, while the major is 10 (for misc devices).
The auto-generator minor can be found in /proc/misc, so we can recreate the 
device node with mknod and the correct major (10) and minor 
(from /proc/misc) numbers.

Once that is done, omreport still won't see the device (tried OMSA 5.5 and 
6.0), but other tools will be able to access it.
For example you can try
which can report device health.
dellmgr (cf seems to work also, but you 
MUST first remove from its startup script the lines that 
recreate /dev/megadev0, same goes for megamon (which also try to 
create /dev/megadev0 in itd init script), but I didn't try it.

I hope this helps

-- Renaud MICHEL defimedia S.A.

IWS Webserver

The IWS webserver enables you to read the same information that the omreport command supplies in a nice web interface. You can start IWS from the /etc/init.d directory, currently we don't support automatic startup.

Now the web interface should work (tested on Lenny/etch release). Start it with

/etc/init.d/dsm_om_connsvc start

or have it started automatically on system startup with

update-rc.d dsm_om_connsvc defaults

To access the web interface, surf to


. You might have to add an exception for the security certificate, depending on your browser settings.

Note for amd64

This is from the email list. You must install lib32 pam modules:


If you have the debian package from[1]
and wants to have the webserver works on amd64 servers, you probably
wants this to make it works change :

/lib/security path to /lib32/security in /etc/pam.d/omauth

and copy from a etch 32 bits install theses files :


to /lib32 of your amd64 servers.

after a ldconfig you should be able to pam login.

Chmouel Boudjnah cboudjnah at 

Ubuntu 10.04

The dellomsa package requires libstdc++. This is not a standard ubuntu package. It can be obtained from the following address:

Extract it and put the *.so files in:

  • /usr/lib32

Thanks to: Jethro Beekman from Kick-in

Last modified 13 years ago Last modified on 05/14/10 10:45:26