I'm also having trouble. I have a Dell PE 2950, PERC 6/i (RHEL 5.4). What is the eta for Dell to fix this broken update?
Should we roll-back to 6.1 or wait? If I wait too long then yum rollbacks will also roll-back more recent package updates. Awhile back OpenIPMI also broke my Dell software. I had to remove libsmbios then install libsmbios, then install firmware-addon-dell to get that back. That was the 2nd time I'd had to do that. The OMSA 5.5 update before that was fun too. i had to completely yum erase and then install again to get it working. So, this is the 4th problem I've had with these OMSA updates. Some of us only have one production system, and it would be nice if Dell tested these better. Packages from Red Hat don't break like this. "omreport system version" shows: Version Report --------------------- Main System Chassis --------------------- Name : BIOS Version : 2.4.3 Name : BMC Version : 1.77 Name : DRAC 5 Version : 1.40 ---------- Software ---------- Name : Red Hat Enterprise Linux Server Version : release 5.4 (Tikanga) Kernel 2.6.18-164.el5 (x86_64) Name : Dell Server Administrator Version : 6.2.0 --Ted On 12/17/09, [email protected] <[email protected]> wrote: > Send Linux-PowerEdge mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Linux-PowerEdge digest..." > > > Today's Topics: > > 1. RE: [official] OpenManage 6.2 yum repository posted > (Johan Sj?berg) > 2. LCD Display on R710 (Ryan Kish) > 3. Re: [official] OpenManage 6.2 yum repository posted (Zach White) > 4. OM 6.2 Broken Storage Section (Aaron McKinnon) > 5. Re: [official] OpenManage 6.2 yum repository posted > (Aaron McKinnon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 17 Dec 2009 15:49:54 +0100 > From: Johan Sj?berg <[email protected]> > Subject: RE: [official] OpenManage 6.2 yum repository posted > To: "[email protected]" <[email protected]> > Message-ID: > > <b08f3f3d67451844a7a8a029fcc71e4c0f6041e...@win01.ad.deltamanagement.se> > > Content-Type: text/plain; charset="iso-8859-1" > > I have the "No controllers found" on one PE1850 with Perc4e/Si as well. The > server runs CentOS 5.4. I have another server with identical hardware and OS, > and there it works after the update to 6.2 > > /Johan > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Giuseppe Tanzilli - > ServerPlan > Sent: den 17 december 2009 12:23 > To: [email protected] > Subject: Re: [official] OpenManage 6.2 yum repository posted > > Hi, > same issue here with OMSA 6.2 not detecting PERC anymore on PE2950, > I tried restarting OMSA services and rebooting, but the issue persists. > > I have many 2950 with this issue after the nightly update. > Same issue on PowerEdge R410 > > Thanks a lot, > Giuseppe > > Il 17/12/2009 8.45, Dirk Gfroerer ha scritto: > > Hi, > > > > after upgrading a PowerEdge 840 with a SAS 5i/R (Centos 5.4) and a T300 > > with a PERC 6/i (RHEL 5.4) the storage controllers on both machines are > > no longer accessible through OMSA. "omreport storage controller" lists > > "No controllers found". Everything has been working fine with OMSA 6.1. > > > > Am I the only one or did anyone else lose access to the storage > controllers? > > > > Thanks& Kind Regards, > > Dirk > > > > _______________________________________________ > > Linux-PowerEdge mailing list > > [email protected] > > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > Please read the FAQ at http://lists.us.dell.com/faq > > > > _______________________________________________ > Linux-PowerEdge mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq > > > > ------------------------------ > > Message: 2 > Date: Thu, 17 Dec 2009 09:02:46 -0700 > From: "Ryan Kish" <[email protected]> > Subject: LCD Display on R710 > To: <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > I am hoping someone can let me know where I am going wrong here. I am > trying to set a custom sring on 12 new r710s. All are running Debian > Etch, and have the OMSA tools re-packaged by SARA (5.5.0-5). > > The command: > ./omconfig chassis frontpanel lcdindex=1 config=custom text=txt > > The result: > Error! Invalid LCD Index. > > I have tried omitting the lcdindex parameter as well as changing the > line number. Nothing seems to work. I know I can set this in the BIOS, > but rebooting the machines for this task seems a little unreasonable. > > Thanks, > Ryan > > > > ------------------------------ > > Message: 3 > Date: Thu, 17 Dec 2009 08:50:48 -0800 > From: Zach White <[email protected]> > Subject: Re: [official] OpenManage 6.2 yum repository posted > To: "<[email protected]>" <[email protected]> > Cc: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes > > As other people have pointed out, the symlinks in /usr/bin seem to be > missing. This has broken all the Dell specific monitoring on my test > server (which points at the linux.dell.com repository, not my local > rsync'd repository.) > > Things like cron jobs, init scripts, NRPE plugins, etc, all use the > default system path, which does NOT include /opt/dell/srvadmin/oma/ > bin/. I can provide my own symlinks, but then I have to start worrying > about whether I actually got everything. > > Can Dell please restore those symlinks in OpenManage 6.2? An hour of > work on your part will collectively save your customers hundreds of > hours. > > -Zach > > On Dec 16, 2009, at 2:01 PM, <[email protected]> > <[email protected] > > wrote: > > > Hi All, > > > > The OpenManage 6.2 yum repository has just been posted, and 'latest' > > symlink updated: > > > > http://linux.dell.com/repo/hardware/latest/ > > > > The repo contains OMSA 6.2 which adds support for the T110, R210, > > T310, and R510 servers. > > > > New Feature!: The OM repo now officially supports updating your > > firmware and BIOS using firmware-tools. The user experience is the > > same as the current unofficial "firmware" repo, however there are > > improvements on the back-end. The repo page above has the general > > usage outlined. Also, documentation is available here: > > > > > http://support.dell.com/support/edocs/software/smdup/dup62/en/ug/linux/html/3onliner.htm > > > > We are very excited about this ability. Expect more detailed > > announcements to come. We will be merging the info available in the > > current "firmware" repo wiki page into the OMSA repo wiki page in > > the next few days: > > http://linux.dell.com/wiki/index.php/Repository/OMSA > > > > Thanks, > > Jeff > > > > > > _______________________________________________ > > Linux-PowerEdge mailing list > > [email protected] > > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > Please read the FAQ at http://lists.us.dell.com/faq > > > > ------------------------------ > > Message: 4 > Date: Thu, 17 Dec 2009 09:01:22 -0800 > From: Aaron McKinnon <[email protected]> > Subject: OM 6.2 Broken Storage Section > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Non of our servers can now see the storage elements: > > # srvadmin-services.sh status > dell_rbu (module) is running > ipmi driver is running > dsm_sa_datamgrd (pid 23010) is running > dsm_sa_eventmgrd (pid 23122) is running > dsm_sa_snmpd (pid 23181) is running > dsm_om_shrsvcd (pid 23256) is running > dsm_om_connsvcd (pid 23299 23298) is running > > # omreport storage controller controller=1 > Invalid controller value. Read, controller=1 > Valid values for controller are: 0 > > I have three controllers on this machine, but no disks on what is listed > as zero. > > # omreport storage vdisk > List of Virtual Disks in the System > > Controller LSI Logic 1020/1030 Ultra320 SCSI Adapter (Slot 2) > No virtual disks found > > We have restarted OM and snmpd to no avail. Ideas? > > -Aaron > > > > ------------------------------ > > Message: 5 > Date: Thu, 17 Dec 2009 09:05:30 -0800 > From: Aaron McKinnon <[email protected]> > Subject: Re: [official] OpenManage 6.2 yum repository posted > To: "[email protected]" <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I just sent an email, but I have the same problem on *all* of my > servers. The storage section seems completely broken. Worked fine before > the update last night. > > -Aaron > > Johan Sj?berg wrote: > > I have the "No controllers found" on one PE1850 with Perc4e/Si as well. > The server runs CentOS 5.4. I have another server with identical hardware and > OS, and there it works after the update to 6.2 > > > > /Johan > > > > > > > > -----Original Message----- > > From: [email protected] > [mailto:[email protected]] On Behalf Of Giuseppe Tanzilli - > ServerPlan > > Sent: den 17 december 2009 12:23 > > To: [email protected] > > Subject: Re: [official] OpenManage 6.2 yum repository posted > > > > Hi, > > same issue here with OMSA 6.2 not detecting PERC anymore on PE2950, > > I tried restarting OMSA services and rebooting, but the issue persists. > > > > I have many 2950 with this issue after the nightly update. > > Same issue on PowerEdge R410 > > > > Thanks a lot, > > Giuseppe > > > > Il 17/12/2009 8.45, Dirk Gfroerer ha scritto: > > > >> Hi, > >> > >> after upgrading a PowerEdge 840 with a SAS 5i/R (Centos 5.4) and a T300 > >> with a PERC 6/i (RHEL 5.4) the storage controllers on both machines are > >> no longer accessible through OMSA. "omreport storage controller" lists > >> "No controllers found". Everything has been working fine with OMSA 6.1. > >> > >> Am I the only one or did anyone else lose access to the storage > controllers? > >> > >> Thanks& Kind Regards, > >> Dirk > >> > >> _______________________________________________ > >> Linux-PowerEdge mailing list > >> [email protected] > >> https://lists.us.dell.com/mailman/listinfo/linux-poweredge > >> Please read the FAQ at http://lists.us.dell.com/faq > >> > >> > > > > _______________________________________________ > > Linux-PowerEdge mailing list > > [email protected] > > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > Please read the FAQ at http://lists.us.dell.com/faq > > > > _______________________________________________ > > Linux-PowerEdge mailing list > > [email protected] > > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > Please read the FAQ at http://lists.us.dell.com/faq > > > > > > > > ------------------------------ > > _______________________________________________ > Linux-PowerEdge mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq > > End of Linux-PowerEdge Digest, Vol 65, Issue 29 > *********************************************** > _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
