Dell OpenManage storage issues

[mauryz]

Thank'you for the solution: I was able to install OMSA on my Poweredge T320 & CentOS 7.1

Unfortunately I can't manage my storage: my PERC H310 is listed under PCI devices, but storage section keep telling me "No storage controllers detected."
I reinstalled OMSA many times, but nothing changes.
I don't have any error messages while installing, in logs section i see error ID 2314 "The initialization sequence of SAS components failed during system startup. SAS management and monitoring is not possible" from "Storage Service" subsytem, every time the server is rebooted.

This is a great problem, because this is a mail server, without UI in a serverfarm, so nobody could check daily if there is any HDD failing.

Thanks.

[edit/avij: I split the storage issues to a new topic]

[avij]

Yes, sadly you are not alone. I'm seeing the same on my R320. Other parts of omreport seem to work fine, but the functionality related to storage seems to be broken with 7.1.1503. OMSA worked fine in this regard with 7.0.1406.

This also seems to occur on RHEL 7.1. RHEL is supported by Dell, so once OMSA is eventually updated to work with RHEL 7.1, the updated OMSA should also work on CentOS. As for when this might happen.. I would not hold my breath. Dell hasn't moved at a neck-breaking speed when it comes to OMSA and 7.

Edit: I found this issue during 1503 QA, and the release notes for 1503 also mention this issue.

[mauryz]

Thanks: this is a great news!
I was started thinking 'bout some problems in my hardware, I've upgraded PERC firmware and RH drivers from Dell website, but no news..
Let's hope that Dell will upgrade OMSA ASAP, in order to let manage our controllers.

Do you think that boot in the previous kernel image could make a temporary solution?

[avij]

Unfortunately I'm not certain if it's the kernel or some other updated package that is causing the trouble. If I had a spare Dell server I could try finding out the change that broke OMSA, but I only have this one server and it's used in production.

Until Dell gets around to updating OMSA to work on 7.1, I guess I'll stick to checking the storage status via iDRAC every now and then.

[mauryz]

Unfortunately this host don't have any iDRAC license, so it is useless for me.
I reported the RH/CentOS 7.1 issue at Dell OMSA forum: let's hope for a fast patch in order to get it running again..

[Sustugriel]

Everyone,

A simple workaround for my servers which are on Centos 7.1.

-Uninstall OMSA 7.4.1
-Install OMSA 7.0

Remove OMSA:

Code: Select all

srvadmin-uninstall.sh

Add the 7.0 repository:

Code: Select all

wget -q -O - http://linux.dell.com/repo/hardware/OMSA_7.0/bootstrap.cgi | bash

Modify the yum repo to EL6

Code: Select all

vi /etc/yum.repos.d/dell-omsa-repository.repo

Change "el$" to "el6" in mirror list to reflect the following:

"mirrorlist=http://linux.dell.com/repo/hardware/OMS ... dpluginver"

Clean yum:

Code: Select all

yum clean all

Install OMSA 7.0

Code: Select all

yum install srvadmin-all

Code: Select all

srvadmin-services.sh start

Code: Select all

srvadmin-services.sh enable

Confirmed working on Gen9,10,11 servers, I assume it will work for others.. Hope this helps. I have not confirmed if 7.3 works, perhaps someone else could give it a try?

[mauryz]

Everyone,

A simple workaround for my servers which are on Centos 7.1.

-Uninstall OMSA 7.4.1
-Install OMSA 7.0

I confirm it work on 12Th Gen server: I've just installed in my PE T320 with PERC H310 and CentOS 7.1.
Thank'you for the workaround!

[roscopcoltrane]

This workaround works with rhel7.0 on a R815. You can use OMSA_7.4.0 instead of ver 7.0.

[gulikoza]

How about Gen13 servers? I don't get any status either on 7.1 & OMSA 8.0.1 with R730 and PercH730...

[avij]

Manuel Mausz posted a very informative message to the Linux-PowerEdge mailing list. He recommends modifying libstorelib.so.4.20.1-0. Please make a backup of that file before patching.

I ran the specified sed command to patch the file and then ran systemctl restart dataeng.service to restart the affected service. omreport storage vdisk and omreport storage controller now work as intended. YMMV.

Note: I tested this with CentOS 7.1.1503, OMSA 8.1.0, R320 and PERC H710.