Re: How do I clear blinking front panel SBE warning on a PowerEdge server w/out rebooting?
as far as I know it is not possible.
the messages and the LCD are more or less 'linked' to each other.
bye
Original-Nachricht
> Datum: Fri, 25 Jun 2010 17:22:26 -0700
> Von: Bryce Nesbitt
> An: linux-poweredge@dell.com
> Betreff: How do I clear blinking front panel SBE warning on a PowerEdge
> serverw/out rebooting?
> Dear List,
>
> How do I clear a blinking front panel warning on a PowerEdge 1950
> server w/out rebooting the server?
> I have an ECC (error correcting code) SBE (single bit error) that I
> plan to ignore ("2111 SBE Log Disabled DIMM 7").
> I know how to delete the log line via the drac card cli, but that kind
> of misses the point.
>
> I'd like to leave the message in the logs, but clear the front panel.
> Is this possible?
>
>
> --
> Bryce Nesbitt
> The Berkeley Electronic Press
> bepress: 10 years of accelerating and enhancing the flow of scholarly
> ideas
>
> ___
> Linux-PowerEdge mailing list
> Linux-PowerEdge@dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Re: OMSA on Precision
It may be possible to use the SAS Storage Manager utility, but I don't have a card to test. It's GUI only though and doesn't have any network functionality that I'm aware of though. On Fri, Jun 25, 2010 at 11:44 AM, J. Epperson wrote: > Dell guys: will the PERC/CERC apps work with his controller? > > If so, megamon and the raidmon scripts may do what Grant needs, but > they're a bit kludgy to set up. I have a working setup on an old > Precision box with a PERC 3 pulling duty as my home server, so post if > you're trying that route and have questions. > > On Fri, June 25, 2010 11:22, Sturgis, Grant wrote: > > Thanks Bryan. With that said, is there any way possible to report on > > the CERC SATA RAID status without rebooting? > > > > This system has a history of failed hard drives, but I think I fixed the > > root cause (power supply). I'd like to report RAID status at a frequent > > interval to make sure it's not failing. > > > > > > > > -Original Message- > > From: Bryan [mailto:bryan.madhat...@gmail.com] > > Sent: Friday, June 25, 2010 9:04 AM > > To: Sturgis, Grant > > Subject: Re: OMSA on Precision > > > > Workstations don't have a bmc/ipmi functionality in most cases. > > Without this you don't have hardware reporting. > > > > On 6/25/10, Sturgis, Grant wrote: > >> Hey folks, > >> > >> Not Poweredge related, but I'm hoping for help anyway. I have a > >> Precision 670 with CentOS 5.5 and the latest OMSA (6.2) installed from > >> the Linux repo. > >> > >> Problem is that OMSA cannot "see" anything. The web interface shows > >> nothing as does omreport chassis (and other omreport commands). > >> > >> Is this possible? Can anyone point me in the right direction? > >> > >> Thanks, > >> > >> Grant > >> > >> > >> > >> > >> Pardon this rubbish: > >> > >> ___ > >> Linux-PowerEdge mailing list > >> Linux-PowerEdge@dell.com > >> https://lists.us.dell.com/mailman/listinfo/linux-poweredge > >> Please read the FAQ at http://lists.us.dell.com/faq > >> > > > > ___ > > Linux-PowerEdge mailing list > > Linux-PowerEdge@dell.com > > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > Please read the FAQ at http://lists.us.dell.com/faq > > > > > > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq > ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
How do I clear blinking front panel SBE warning on a PowerEdge server w/out rebooting?
Dear List,
How do I clear a blinking front panel warning on a PowerEdge 1950
server w/out rebooting the server?
I have an ECC (error correcting code) SBE (single bit error) that I
plan to ignore ("2111 SBE Log Disabled DIMM 7").
I know how to delete the log line via the drac card cli, but that kind
of misses the point.
I'd like to leave the message in the logs, but clear the front panel.
Is this possible?
--
Bryce Nesbitt
The Berkeley Electronic Press
bepress: 10 years of accelerating and enhancing the flow of scholarly ideas
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
PERC S300 - can it be made to work?
Hello Can anyone give me a definitive statement wrt the status of PERC S300 SATA controller support for Linux? I found an inconclusive thread on this list last month: http://lists.us.dell.com/pipermail/linux-poweredge/2010-May/042244.html and rumour from two months ago that it might be supported by the mpt2sas driver: http://www.delltechcenter.com/thread/3474701/ mpt2sas doesn't support it in the binaries we have to hand, and I can't see how or where in the current mainline kernel source. I also found people claiming it's hardware-identical to the fully-working SAS 6/iR controller we thought we were getting (both PCBs are marked "UCS-61" and look the same to the untrained eye). Is there a Linux driver of any kind available anywhere? A JBOD-only driver that we have to compile ourselves would be absolutely fine. Is it possible to re-flash the hardware with the SAS 6/iR firmware? Cheers Duncan -- Duncan Gibb - Technical Director Sirius Corporation plc - control through freedom http://www.siriusit.co.uk/ ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: OMSA on Precision
Dell guys: will the PERC/CERC apps work with his controller? If so, megamon and the raidmon scripts may do what Grant needs, but they're a bit kludgy to set up. I have a working setup on an old Precision box with a PERC 3 pulling duty as my home server, so post if you're trying that route and have questions. On Fri, June 25, 2010 11:22, Sturgis, Grant wrote: > Thanks Bryan. With that said, is there any way possible to report on > the CERC SATA RAID status without rebooting? > > This system has a history of failed hard drives, but I think I fixed the > root cause (power supply). I'd like to report RAID status at a frequent > interval to make sure it's not failing. > > > > -Original Message- > From: Bryan [mailto:bryan.madhat...@gmail.com] > Sent: Friday, June 25, 2010 9:04 AM > To: Sturgis, Grant > Subject: Re: OMSA on Precision > > Workstations don't have a bmc/ipmi functionality in most cases. > Without this you don't have hardware reporting. > > On 6/25/10, Sturgis, Grant wrote: >> Hey folks, >> >> Not Poweredge related, but I'm hoping for help anyway. I have a >> Precision 670 with CentOS 5.5 and the latest OMSA (6.2) installed from >> the Linux repo. >> >> Problem is that OMSA cannot "see" anything. The web interface shows >> nothing as does omreport chassis (and other omreport commands). >> >> Is this possible? Can anyone point me in the right direction? >> >> Thanks, >> >> Grant >> >> >> >> >> Pardon this rubbish: >> >> ___ >> Linux-PowerEdge mailing list >> Linux-PowerEdge@dell.com >> https://lists.us.dell.com/mailman/listinfo/linux-poweredge >> Please read the FAQ at http://lists.us.dell.com/faq >> > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq > > ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: OMSA on Precision
Thanks Bryan. With that said, is there any way possible to report on the CERC SATA RAID status without rebooting? This system has a history of failed hard drives, but I think I fixed the root cause (power supply). I'd like to report RAID status at a frequent interval to make sure it's not failing. -Original Message- From: Bryan [mailto:bryan.madhat...@gmail.com] Sent: Friday, June 25, 2010 9:04 AM To: Sturgis, Grant Subject: Re: OMSA on Precision Workstations don't have a bmc/ipmi functionality in most cases. Without this you don't have hardware reporting. On 6/25/10, Sturgis, Grant wrote: > Hey folks, > > Not Poweredge related, but I'm hoping for help anyway. I have a > Precision 670 with CentOS 5.5 and the latest OMSA (6.2) installed from > the Linux repo. > > Problem is that OMSA cannot "see" anything. The web interface shows > nothing as does omreport chassis (and other omreport commands). > > Is this possible? Can anyone point me in the right direction? > > Thanks, > > Grant > > > > > Pardon this rubbish: > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq > ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
OMSA on Precision
Hey folks, Not Poweredge related, but I'm hoping for help anyway. I have a Precision 670 with CentOS 5.5 and the latest OMSA (6.2) installed from the Linux repo. Problem is that OMSA cannot "see" anything. The web interface shows nothing as does omreport chassis (and other omreport commands). Is this possible? Can anyone point me in the right direction? Thanks, Grant Pardon this rubbish: ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Error on OM firmware tools install: Centos 5.5
Hey all -- Getting an error on trying to install the firmware tools: [*r...@test log]# yum install dell_ft_install* *Loaded plugins: fastestmirror* *Loading mirror speeds from cached hostfile* * * addons: centos.mbni.med.umich.edu* * * base: ftp.ussg.iu.edu* * * extras: centos.cs.wisc.edu* * * updates: centos-distro.cavecreek.net* *Setting up Install Process* *Resolving Dependencies* *--> Running transaction check* *---> Package dell_ft_install.noarch 0:1.0-1 set to be updated* *--> Processing Dependency: dell_ie_tape_ibm for package: dell_ft_install* *--> Processing Dependency: dell_ie_rac_5 for package: dell_ft_install* *--> Processing Dependency: dell_ie_maser_inv_lcl for package: dell_ft_install* *--> Processing Dependency: dell_ie_tape_prostor for package: dell_ft_install* *--> Processing Dependency: dell_ie_tape_tandberg for package: dell_ft_install* *--> Processing Dependency: dell_ie_imc for package: dell_ft_install* *--> Processing Dependency: dell_ie_bios for package: dell_ft_install* *--> Processing Dependency: dell_ie_bp for package: dell_ft_install* *--> Processing Dependency: dell_ie_bmc for package: dell_ft_install* *--> Processing Dependency: dell_ie_sas for package: dell_ft_install* *--> Processing Dependency: dell_ie_zappa for package: dell_ft_install* *--> Processing Dependency: dell_ie_rac_4 for package: dell_ft_install* *--> Running transaction check* *---> Package dell_ie_bios.noarch 0:1.0.8-1 set to be updated* *--> Processing Dependency: dell_ft_ie_interface for package: dell_ie_bios* *---> Package dell_ie_bmc.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_bp.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_imc.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_maser_inv_lcl.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_rac_4.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_rac_5.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_sas.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_tape_ibm.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_tape_prostor.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_tape_tandberg.noarch 0:1.0.8-1 set to be updated* *---> Package dell_ie_zappa.noarch 0:1.0.8-1 set to be updated* *--> Running transaction check* *---> Package dell_ft_ie_interface.noarch 0:1.0.8-1.6.el5 set to be updated* *--> Processing Dependency: firmware-tools >= 2.0.0 for package: dell_ft_ie_interface* *--> Processing Dependency: firmware-addon-dell >= 2.0 for package: dell_ft_ie_interface* *--> Running transaction check* *---> Package firmware-addon-dell.x86_64 0:2.2.2-5.6.el5 set to be updated* *--> Processing Dependency: python-smbios for package: firmware-addon-dell* *--> Processing Dependency: smbios-utils for package: firmware-addon-dell* *---> Package firmware-tools.noarch 0:2.1.9.d1-2.1.el5 set to be updated* *--> Running transaction check* *---> Package python-smbios.x86_64 0:2.2.19-10.1.el5 set to be updated* *--> Processing Dependency: libsmbios = 2.2.19-10.1.el5 for package: python-smbios* *--> Processing Dependency: python-ctypes for package: python-smbios* *---> Package smbios-utils.x86_64 0:2.2.19-10.1.el5 set to be updated* *--> Processing Dependency: smbios-utils-python for package: smbios-utils* *--> Running transaction check* *--> Processing Dependency: libsmbios = 2.2.19-4.1.el5 for package: smbios-utils-bin* *---> Package libsmbios.i386 0:2.2.19-10.1.el5 set to be updated* *---> Package libsmbios.x86_64 0:2.2.19-10.1.el5 set to be updated* *---> Package python-ctypes.x86_64 0:1.0.2-1.1.el5 set to be updated* *---> Package smbios-utils-python.x86_64 0:2.2.19-10.1.el5 set to be updated * *--> Finished Dependency Resolution* *smbios-utils-bin-2.2.19-4.1.el5.i386 from installed has depsolving problems * * --> Missing Dependency: libsmbios = 2.2.19-4.1.el5 is needed by package smbios-utils-bin-2.2.19-4.1.el5.i386 (installed)* *Error: Missing Dependency: libsmbios = 2.2.19-4.1.el5 is needed by package smbios-utils-bin-2.2.19-4.1.el5.i386 (installed)* * You could try using --skip-broken to work around the problem* * You could try running: package-cleanup --problems* *package-cleanup --dupes* *rpm -Va --nofiles --nodigest* *The program package-cleanup is found in the yum-utils package.* It looks like it wants an update to the smbios-utils-bin.i386 package... but unfortunately, no such update for the i386 package appears to be in the repository. I realize that there are sources I could build from... but is this a known issue and will there be an update for the i386 package coming out soon? OS: CentOS 5.5 x86-64 Thanks, Shaun ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Strange ACPI/power_meter error on boot: R210, CentOS 5.5
Hey all -- I'm noticing a strange power_meter error on boot on my R210: ACPI: Power Button (FF) [PWRF] ACPI: Mapper loaded dell-wmi: No known WMI GUID found ACPI Exception (evregion-0424): AE_SUPPORT, Returned by Handler for [DataTable] [20060707] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PMI0._GHL] (Node 8100027d6fb0), AE_SUPPORT ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PMI0._PMC] (Node 8100027d6430), AE_SUPPORT ACPI Exception (power_meter-0759): AE_SUPPORT, Evaluating _PMC [20060707] Device 'power_meter0' does not have a release() function, it is broken and must be fixed. BUG: warning at drivers/base/core.c:101/device_release() (Not tainted) Call Trace: [] kobject_cleanup+0x53/0x7e [] kobject_release+0x0/0x9 [] kref_put+0x6f/0x7a [] :power_meter:acpi_power_meter_add+0x158/0x16f [] acpi_bus_driver_init+0x30/0x57 [] acpi_bus_register_driver+0x95/0xd4 [] :power_meter:acpi_power_meter_init+0x25/0x34 [] sys_init_module+0xaf/0x1f2 [] system_call+0x7e/0x83 It doesn't appear to be affecting anything, but I'm curious if there's a fix or anything for it? OS: Centos 5.5 x86-64 Kernel: 2.6.18-194.3.1.el5 Thanks, Shaun ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Strange networking issue
I have a PE2850, running RHEL5.4, with a two port intel card in it. One port from both onboard and PCI NIC connect to the network in an active-backup bond. Yesterday at about 2pm we had a broadcast storm on one of the switches, and eth0 failed over to eth3. Everything was running fine (I didn't even notice the failover, nor did users). At 6pm, we had another strange networking issue (not sure what yet, but one of our VMware HA boxes decided to no longer be available by heartbeat). The eth3 interface dropped this: Jun 24 18:07:43 ccvobdubpr kernel: e1000: eth3: e1000_clean_tx_irq: Detected Tx Unit Hang Jun 24 18:07:43 ccvobdubpr kernel: Tx Queue <0> Jun 24 18:07:43 ccvobdubpr kernel: TDH Jun 24 18:07:43 ccvobdubpr kernel: TDT <93> Jun 24 18:07:43 ccvobdubpr kernel: next_to_use <93> Jun 24 18:07:43 ccvobdubpr kernel: next_to_clean Jun 24 18:07:43 ccvobdubpr kernel: buffer_info[next_to_clean] Jun 24 18:07:43 ccvobdubpr kernel: time_stamp <4257186b> Jun 24 18:07:43 ccvobdubpr kernel: next_to_watch Jun 24 18:07:43 ccvobdubpr kernel: jiffies <42573ee7> Jun 24 18:07:43 ccvobdubpr kernel: next_to_watch.status <0> There was no failover message. People started complaining this morning about the speed. A colleague ifdown/up the bond and all is ok. Until I checked the log: Jun 25 08:38:03 ccvobdubpr kernel: e1000: eth3: e1000_watchdog_task: NIC Link is Up 10 Mbps Half Duplex, Flow Control: None Currently we are running on eth0. [r...@ccvobdubpr log]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Intel Corporation 82541GI Gigabit Ethernet Controller DEVICE=eth0 BOOTPROTO=dhcp #HWADDR=00:13:72:5F:10:6B ONBOOT=yes MASTER=bond0 SLAVE=yes [r...@ccvobdubpr log]# cat /etc/sysconfig/network-scripts/ifcfg-eth3 # Intel Corporation 82546GB Gigabit Ethernet Controller DEVICE=eth3 BOOTPROTO=dhcp HWADDR=00:1B:21:53:62:51 ONBOOT=no MASTER=bond0 SLAVE=yes [r...@ccvobdubpr log]# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008) Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 1 Down Delay (ms): 0 Slave Interface: eth0 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:13:72:5f:10:6b Slave Interface: eth3 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:1b:21:53:62:51 I have a number of questions here. #1 why didn't it fail over. I take it it hung, and the interface slowed right down. #2 Why did it come back up as 10Mb (It was definitely running fine between 2pm and 6pm yesterday) #3 can I fix eth3 without a reboot. Thanks B The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
