headers
Тарас Перебейносов | 2 May 2011 01:10
Picon

Dell PowerEdge R410. Kernel panic after update driver for SAS 6/iR Integrated

OS: Red Hat Enterprise Linux Server release 5.5 (Tikanga)
Kernel: 2.6.18-238.5.1.0.1.el5 #1 SMP
Driver: mptlinux-4.00.38.02-3dkms.noarch

rpm -ivh mptlinux-4.00.38.02-3dkms.noarch.rpm
Preparing...                ########################################### [100%]
    package mptlinux-4.00.38.02-3dkms.noarch is already installed

dkms status -m mptlinux --all
mptlinux, 4.00.38.02, 2.6.18-238.5.1.0.1.el5, x86_64: installed (original_module exists)
mptlinux, 4.00.38.02, 2.6.18-194.el5, x86_64: installed-weak from 2.6.18-238.5.1.0.1.el5

after reboot system down with kernel panic.
Booting available only with old initrd: initrd-2.6.18-238.5.1.0.1.el5.img.dup_orig

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Permalink | Reply | 1 comment |
headers
Тарас Перебейносов | 2 May 2011 02:31
Picon

Re: Dell PowerEdge R410. Kernel panic after update driver for SAS 6/iR Integrated

# tar xzvf mptlinux-4.00.38.02-src.tar.gz

# cd message/fusion/

# ./compile
make: Entering directory `/usr/src/kernels/2.6.18-238.5.1.0.1.el5-x86_64'
  LD      /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/built-in.o
  CC [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptbase.o
  CC [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptscsih.o
  CC [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptspi.o
  CC [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptfc.o
  CC [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptsas.o
  CC [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptctl.o
  CC [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptlan.o
  Building modules, stage 2.
  MODPOST
  CC      /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptbase.mod.o
  CC      /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptctl.mod.o
  CC      /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptfc.mod.o
  CC      /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptlan.mod.o
  CC      /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptsas.mod.o
  CC      /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptscsih.mod.o
  CC      /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptspi.mod.o
  LD [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptbase.ko
  LD [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptctl.ko
  LD [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptfc.ko
  LD [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptlan.ko
  LD [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptsas.ko
  LD [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptspi.ko
  LD [M]  /opt/dell/SAS_6IR_Integrated/R211003-mptlinux-4.00.38.02-3/message/fusion/mptscsih.ko
make: Leaving directory `/usr/src/kernels/2.6.18-238.5.1.0.1.el5-x86_64'

# ./update
`mptbase.ko' -> `/lib/modules/2.6.18-238.5.1.0.1.el5/kernel/drivers/message/fusion/mptbase.ko'
`mptctl.ko' -> `/lib/modules/2.6.18-238.5.1.0.1.el5/kernel/drivers/message/fusion/mptctl.ko'
`mptfc.ko' -> `/lib/modules/2.6.18-238.5.1.0.1.el5/kernel/drivers/message/fusion/mptfc.ko'
`mptlan.ko' -> `/lib/modules/2.6.18-238.5.1.0.1.el5/kernel/drivers/message/fusion/mptlan.ko'
`mptsas.ko' -> `/lib/modules/2.6.18-238.5.1.0.1.el5/kernel/drivers/message/fusion/mptsas.ko'
`mptscsih.ko' -> `/lib/modules/2.6.18-238.5.1.0.1.el5/kernel/drivers/message/fusion/mptscsih.ko'
`mptspi.ko' -> `/lib/modules/2.6.18-238.5.1.0.1.el5/kernel/drivers/message/fusion/mptspi.ko'

# ./load
insmod: error inserting 'mptbase.ko': -1 File exists
insmod: error inserting 'mptscsih.ko': -1 File exists
insmod: error inserting 'mptsas.ko': -1 File exists
insmod: error inserting 'mptctl.ko': -1 Unknown symbol in module

Это что?

2011/5/2 Тарас Перебейносов <taras.perebeynosov <at> gmail.com>
OS: Red Hat Enterprise Linux Server release 5.5 (Tikanga)
Kernel: 2.6.18-238.5.1.0.1.el5 #1 SMP
Driver: mptlinux-4.00.38.02-3dkms.noarch

rpm -ivh mptlinux-4.00.38.02-3dkms.noarch.rpm
Preparing...                ########################################### [100%]
    package mptlinux-4.00.38.02-3dkms.noarch is already installed

dkms status -m mptlinux --all
mptlinux, 4.00.38.02, 2.6.18-238.5.1.0.1.el5, x86_64: installed (original_module exists)
mptlinux, 4.00.38.02, 2.6.18-194.el5, x86_64: installed-weak from 2.6.18-238.5.1.0.1.el5

after reboot system down with kernel panic.
Booting available only with old initrd: initrd-2.6.18-238.5.1.0.1.el5.img.dup_orig

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Permalink | Reply | 0 comments |
headers
David B. | 2 May 2011 11:04
Picon

Om 6.5 didn't see PERC 6/i events

Hi Dell list,

Once again, I need some help (CF OM 6.5 and service freeze on boot for
my last ask).

I'm upgrading all my dell poweredge (1950 II, 2950 III and R300) to
Debian Squeeze and OM 6.5.

We found a very strange "behavior".
I've got an upgraded PE 19500 III. All is OK.

But omreport still report cache battery charging.
In fact, cache battery si no longer charging, but omreport can't see it !
# omreport storage battery
List of Batteries in the System

Controller PERC 6/i Integrated (Slot Embedded)
ID                        : 0
Status                    : Non-Critical
Name                      : Battery 0
State                     : Charging
Recharge Count            : Not Applicable
Max Recharge Count        : Not Applicable
Predicted Capacity Status : Ready
Learn State               : Idle
Next Learn Time           : 13 days 13 hours
Maximum Learn Delay       : 7 days 0 hours
Learn Mode                : Auto

We've removed a disk from this RAID 1 array.
Omreport can't see it.

I've put this disk back and omreport say all is ok, but raid rebuild is
in progress. :(
# omreport storage pdisk controller=0
List of Physical Disks on Controller PERC 6/i Integrated (Embedded)

Controller PERC 6/i Integrated (Embedded)
ID                        : 0:0:0
Status                    : Ok
Name                      : Physical Disk 0:0:0
State                     : Online
Power Status              : Not Applicable
Bus Protocol              : SATA
Media                     : HDD
Revision                  : GK6OA9N1
Failure Predicted         : No
Certified                 : Not Applicable
Encryption Capable        : No
Encrypted                 : Not Applicable
Progress                  : Not Applicable
Mirror Set ID             : Not Applicable
Capacity                  : 465.25 GB (499558383616 bytes)
Used RAID Disk Space      : 465.25 GB (499558383616 bytes)
Available RAID Disk Space : 0.00 GB (0 bytes)
Hot Spare                 : No
Vendor ID                 : DELL
Product ID                : Hitachi HUA721050KLA330
Serial No.                : *
Part Number               : *
Negotiated Speed          : Not Available
Capable Speed             : Not Available
Manufacture Day           : Not Available
Manufacture Week          : Not Available
Manufacture Year          : Not Available
SAS Address               : 1221000000000000

ID                        : 0:0:1
Status                    : Ok
Name                      : Physical Disk 0:0:1
State                     : Online
Power Status              : Not Applicable
Bus Protocol              : SATA
Media                     : HDD
Revision                  : GK6OA9N1
Failure Predicted         : No
Certified                 : Not Applicable
Encryption Capable        : No
Encrypted                 : Not Applicable
Progress                  : Not Applicable
Mirror Set ID             : Not Applicable
Capacity                  : 465.25 GB (499558383616 bytes)
Used RAID Disk Space      : 465.25 GB (499558383616 bytes)
Available RAID Disk Space : 0.00 GB (0 bytes)
Hot Spare                 : No
Vendor ID                 : DELL
Product ID                : Hitachi HUA721050KLA330
Serial No.                : *
Part Number               : *
Negotiated Speed          : Not Available
Capable Speed             : Not Available
Manufacture Day           : Not Available
Manufacture Week          : Not Available
Manufacture Year          : Not Available
SAS Address               : 1221000001000000

If I reboot this server and then go to the PERC 6 configuration bios. I
can see that RAID is rebuilding.
Then I reboot to Linux.
Now I can see RAID rebuild process but rebuild progress will stuck to
XX%, for example 54% for ever.
I must reboot my server each time I need to "refresh" RAID status, this
is quite painfull. :(

All bios and FW are up to date through SUU 6.5 DVD.
Dell OM seems to be up to date too.
# omreport about
sh: /bin/rpm: not found

Product name : Server Administrator
Version      : 6.5.0
Copyright    : Copyright (C) Dell Inc. 1995-2011 All rights reserved.
Company      : Dell Inc.

PERC6/i driver version seems to be enough :
# omreport storage controller
 Controller  PERC 6/i Integrated (Embedded)

Controllers
ID                                            : 0
Status                                        : Ok
Name                                          : PERC 6/i Integrated
Slot ID                                       : Embedded
State                                         : Ready
Firmware Version                              : 6.3.0-0001
Minimum Required Firmware Version             : Not Applicable
Driver Version                                : 00.00.04.01

Minimum Required Driver Version               : Not Applicable
Storport Driver Version                       : Not Applicable
Minimum Required Storport Driver Version      : Not Applicable
Number of Connectors                          : 2
Rebuild Rate                                  : 30%
BGI Rate                                      : 30%
Check Consistency Rate                        : 30%
Reconstruct Rate                              : 30%
Alarm State                                   : Not Applicable
Cluster Mode                                  : Not Applicable
SCSI Initiator ID                             : Not Applicable
Cache Memory Size                             : 256 MB
Patrol Read Mode                              : Auto
Patrol Read State                             : Stopped
Patrol Read Rate                              : 30%
Patrol Read Iterations                        : 104
Abort Check Consistency on Error              : Disabled
Allow Revertible Hot Spare and Replace Member : Enabled
Load Balance                                  : Not Applicable
Auto Replace Member on Predictive Failure     : Disabled
Redundant Path view                           : Not Applicable
CacheCade Capable                             : Not Applicable
Persistent Hot Spare                          : Not Applicable
Encryption Capable                            : Not Applicable
Encryption Key Present                        : Not Applicable
Encryption Mode                               : Not Applicable
Spin Down Unconfigured Drives                 : Not Applicable
Spin Down Hot Spares                          : Not Applicable

Any idea ?

Thank you.
David.
Permalink | Reply | 0 comments |
headers
Nelson Baptista | 2 May 2011 14:16

Fwd: FW: SAN HQ Notification Alert

hi,

I know that this mailling list is for linux support, but ...
I have a Dell EqualLogic PS6000 and sometimes I have this kind of alerts, in this case, is about TCP retransmits.

This message was generated by the Dell EqualLogic SAN HeadQuarters service (version 2.1.0.5342)

Caution conditions:

  • 02-05-2011 1:32:53 to 02-05-2011 2:32:54

    • Member EQLSAN02MEMBER01 TCP retransmit percentage of 1,2%. If this trend persists for an hour or more, it may be indicative of a serious problem on the member, resulting in an email notification.

      • TCP retransmit rate greater than 1% should be investigated. Check the network connections and switch settings.

      • Condition already generated an e-mail message. If the condition persists, additional messages will be sent approximately every 6 hours.

    • TCP outbound packet counts for polling period: 3.137

    • TCP retransmit packet counts for polling period: 38

    • eth0 send rate for polling period: <1.0 KB/sec

    • eth1 send rate for polling period: <1.0 KB/sec

    • eth2 send rate for polling period: <1.0 KB/sec

    • eth3 send rate for polling period: <1.0 KB/sec

anyone has/had this kind of problem, and what you did to solve it?....
the equipment is connect to a Dell PowerConnect, and from web console, there is no errors in the ports where Equalogic is connected.

Thanks,
Best Regards,
NBA

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Permalink | Reply | 0 comments |
headers
Steve Jenkins | 2 May 2011 18:07
Picon
Gravatar

OMSA 6.5 installs happily on PowerEdge 1850

Just as an interesting data point, I successfully upgraded from OMSA
6.4 -> 6.5 on a PowerEdge 1850 running CentOS 5.6 (32-bit) with
nothing more than a "yum update."

I was pleasantly surprised that everything went so smoothly. The PERC
4e/Si (what I care most about monitoring via Nagios and
check_openmanage) is completely visible and accessible.

SteveJ
Permalink | Reply | 0 comments |
headers
Alexandre Vovan | 2 May 2011 20:36

upgrade BIOS and firmware on PE 850

Hello,

Hope you're all doing well. 

I am trying to upgrade the BIOS and CERC firmware on a PE 850, but without success. Here's what I tried :

1. burned ISO of latest System Update Utility DVD - it's 4.8GB and it won't fit on a normal DVD! So I burned it on
a Dual-Layer DVD, and the PE 850 doesn't seem to recognize it.
2. installed Debian and OMSA - but I can't see how I could use this (CLI or web) to performa a BIOS or firmware update...
3. tried to install Windows 2008 32-bit to run the windows BIOS update utility - Windows doesn't recognize
the CERC driver taken from the Dell website.
4. installed Windows XP to run the windows BIOS update utility - pops up an error when I try to run it.

Any ideas? 

Thanks! :)

Alexandre
Permalink | Reply | 1 comment |
headers
Jeff | 2 May 2011 22:03
Picon

OMSA Live CD for firmware update on an ESXi host?

I am trying to solve a problem with an R200 that runs ESXi.

There is a known issue with ESXi and old firmware on R200 DVD drives.
But I can't find a good way to update the firmware. The Dell support
site offers both Windows-based and DOS-based firmware update packages
for this particular drive. I have booted the R200 to DOS from USB key
and attempted to run the DOS-based updater, but it is more-or-less
undocumented and it is not getting the job done.

So, I was hoping to use the OMSA Live CD (based on CentOS) to boot up
the ESXi host, but I don't know if the Live CD has firmware update
capability and whether or not it knows about firmware for peripherals
like DVD drives. As I recall, firmware updates, via the Linux
repositories are pretty much limited to BIOS, BMC and storage
controllers.

Before I go to the trouble of scheduling down-time for this ESXi host
(sadly, we don't have vMotion capability), can anybody tell me about
experiences with the Live CD?

Or I suppose I could use any Linux Live CD if I could only find the
right firmware package. The drive in question, according to the ESXi
diagnostics,  is a Teac DV-28SW

Thanks,

--
Jeff
Permalink | Reply | 4 comments |
headers
Tim Small | 2 May 2011 23:15
Picon
Favicon

Re: upgrade BIOS and firmware on PE 850

On 02/05/11 19:36, Alexandre Vovan wrote:

> 2. installed Debian and OMSA - but I can't see how I could use this (CLI or web) to performa a BIOS or firmware update...
> 3. tried to install Windows 2008 32-bit to run the windows BIOS update utility - Windows doesn't recognize
the CERC driver taken from the Dell website.
> 4. installed Windows XP to run the windows BIOS update utility - pops up an error when I try to run it.
>
> Any ideas? 
>   

Did you try:

http://www.ducea.com/2007/08/27/dell-bios-firmware-updates-on-debian/

to update the BIOS?  It has always worked for me - no farting about with
iso images, or broken rpms required...

Not sure about the CERC, but I tend to end up manually pulling apart
Dell's bizarre RHEL rpms to install under Debian for RAID cards.

If that doesn't work, I use the DOS one (and netboot, or USB,
syslinux+CD boot the DOS image).  If all else fails, perhaps you could
try flashrom (have used it successfully on many non-Dell system)
http://www.flashrom.org/Flashrom

I think I would be inclined to ditch the CERC, and replace it with
something a bit better supported under Linux, like a $20 Silicon Image
3132, or $40 Silicon Image 3124 (PCIe or PCI-X respectively).  Oh, you
can even flash those with flashrom under Debian.

Tim.

--

-- 
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.  
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53  http://seoss.co.uk/ +44-(0)1273-808309
Permalink | Reply | 0 comments |
headers
Baird, Josh | 3 May 2011 00:21

linux.dell.com slowness?

Is linux.dell.com painfully slow for anyone else?  I'm trying to rsync
the hardware repos over, and at this rate, it's going to take days
(8-20k/sec).

Josh
Permalink | Reply | 0 comments |
headers
Epangsky Pal | 3 May 2011 01:35
Picon
Favicon

R710 centOS-5.6 OMSA IPMI issue

Hi,

System R710, CentOS 5.6 x86_64 following the directions at

http://linux.dell.com/repo/hardware/latest/

Can't get my IPMI to work...
# srvadmin-services.sh restart
Shutting down DSM SA Shared Services:                      [  OK  ]
Shutting down DSM SA Connection Service:                   [  OK  ]
Stopping Systems Management Data Engine:
Stopping dsm_sa_eventmgrd: Not started                     [FAILED]
Stopping dsm_sa_datamgrd: Not started                      [FAILED]
Stopping Systems Management Device Drivers:
Stopping dell_rbu:                                         [  OK  ]
Starting Systems Management Device Drivers:
Starting dell_rbu:                                         [  OK  ]
Starting ipmi driver:                                      [FAILED]
Starting Systems Management Device Drivers:
Starting dell_rbu: Already started                         [  OK  ]
Starting ipmi driver:                                      [FAILED]
Starting DSM SA Shared Services:                           [  OK  ]
Starting DSM SA Connection Service:                        [  OK  ]

# dkms status
openipmi, 39.1dell, 2.6.18-194.el5, x86_64: built
openipmi, 39.1dell, 2.6.18-194.el5, i686: built
openipmi, 39.1dell, 2.6.18-194.el5xen, x86_64: built
openipmi, 39.1dell, 2.6.18-194.el5xen, i686: built
openipmi, 39.1dell, 2.6.18-194.el5PAE, i686: built
openipmi, 39.1dell, 2.6.18-238.9.1.el5, x86_64: installed (original_module exists)
openipmi, 39.1dell, 2.6.18-238.9.1.el5debug, x86_64: installed (original_module exists)
openipmi, 39.1dell, 2.6.18-194.32.1.el5debug, x86_64: installed-weak from 2.6.18-238.9.1.el5debug
openipmi, 39.1dell, 2.6.18-238.5.1.el5debug, x86_64: installed-weak from 2.6.18-238.9.1.el5debug
openipmi, 39.1dell, 2.6.18-194.32.1.el5, x86_64: installed-weak from 2.6.18-238.9.1.el5
openipmi, 39.1dell, 2.6.18-194.26.1.el5debug, x86_64: installed-weak from 2.6.18-238.9.1.el5debug
openipmi, 39.1dell, 2.6.18-194.26.1.el5, x86_64: installed-weak from 2.6.18-238.9.1.el5


# inventory_firmware
Wait while we inventory system:
System inventory:
        BIOS = 2.1.15
        SAS/SATA Backplane 0:0 Backplane Firmware = 1.07
        ST9146852SS Firmware = ht64
        System BIOS for PowerEdge R710 = 2.1.15
        NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth2) = 6.2.14
        NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth1) = 6.2.14
        PERC 6/i Integrated Controller 0 Firmware = 6.3.0-0001
        NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth3) = 6.2.14
        NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth4) = 6.2.14
        NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth5) = 6.2.14
        NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth6) = 6.2.14

#dmesg output
ipmi message handler version 39.1
ipmi_si: Unknown parameter `kipmid_max_busy_us'
ipmi message handler version 39.1
ipmi_si: Unknown parameter `kipmid_max_busy_us'
ipmi message handler version 39.1
ipmi_si: Unknown parameter `kipmid_max_busy_us'

#/var/log/messages
May  2 19:31:18 oss06w kernel: ipmi message handler version 39.1
May  2 19:31:18 oss06w kernel: ipmi_si: Unknown parameter `kipmid_max_busy_us'
May  2 19:31:18 oss06w instsvcdrv: /etc/rc.d/init.d//dsm_sa_ipmi start command failed with status 1
May  2 19:31:20 oss06w kernel: ipmi message handler version 39.1
May  2 19:31:20 oss06w kernel: ipmi_si: Unknown parameter `kipmid_max_busy_us'
May  2 19:31:20 oss06w instsvcdrv: /etc/rc.d/init.d//dsm_sa_ipmi start command failed with status 1


Not sure what I am missing.
Previously had freeipmi and got rid of it. Have done reinstalls of omsa too.

Wondering what I'm missing.

TIA



_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Permalink | Reply | 0 comments |

Gmane