Oct 262016
 

Today I was upgrading Dell PERC 6/i Integrated controller firmware on, rather old to put it mildly, PowerEdge 2950 server running Centos 7. Sadly update was failing with following message when I tried firing dup (dell update package for Red Hat Linux SAS-RAID_Firmware_3P52K_LN_6.3.3-0002_X00.BIN):

Oct 26 13:51:15 mielnet-web-dev03 kernel: sasdupie[11976]: segfault at 20 ip 00007fe7b2f3000d sp 00007ffe7d58bb00 error 4 in sasdupie[7fe7b2f0b000+110000]

What is going on? What’s causing segfault? After fiddling and googling I end up doing this:

chmod +x /tmp/SAS-RAID_Firmware_3P52K_LN_6.3.3-0002_X00.BIN 
/tmp/SAS-RAID_Firmware_3P52K_LN_6.3.3-0002_X00.BIN --extract /tmp/dup_extract_dir
cd /tmp/dup_extract_dir
./sasdupie -i -o inv.xml -debug

and after examining /tmp/dup_extract_dir/debug.log it turned out that sasdupie is segfaulting when trying to use libstorelibir.so.5 – so I figured version on system might be just too new. Lets try using a bit older version of this static object located under /opt/dell/srvadmin/lib64/ – it’s part of srvadmin-storelib RPM package by the way, RPM that can be installed from Dell repo.

cd /opt/dell/srvadmin/lib64
rm libstorelibir.so.5
ln -s libstorelibir-3.so libstorelibir.so.5

Keeping my fingers crossed and touching wood I typed using my nose:

/tmp/SAS-RAID_Firmware_3P52K_LN_6.3.3-0002_X00.BIN

Running validation...

PERC 6/i Integrated Controller 0

The version of this Update Package is newer than the currently installed version.
Software application name: PERC 6/i Integrated Controller 0 Firmware
Package version: 6.3.3-0002
Installed version: 6.0.2-0002

................................................
Device: PERC 6/i Integrated Controller 0
  Application: PERC 6/i Integrated Controller 0 Firmware
  The operation was successful.


Nice. No segfaults. Shout-out to Luiz Angelo Daros de Luca.

Jun 182015
 

Serial port console, tested with DRAC6 Express and Ubuntu 14.04

I aint payin for DRAC Enterprise!

insta-10

create service for console

vim /etc/init/ttyS1.conf

start on stopped rc RUNLEVEL=[12345]
stop on runlevel [!12345]
respawn
exec /sbin/getty -L 115200 ttyS1 vt102

sudo start ttyS1

edit grub setting

vim /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS1 console=ttyS1,115200n8"
GRUB_TERMINAL=serial
GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1"

sudo update-grub

make sure ttyS1 is present in /etc/securetty (it’s there by default)

we need to assign com2 to DRAC now, either via BIOS or via omconfig (you did install OpenManage, did you?)

omreport chassis biossetup
omconfig chassis biossetup attribute=serialcom setting=com2
omconfig chassis biossetup attribute=crab setting=enabled

or reboot and enter BIOS (F2) Serial Communication section

serial communication....On with serial redirection via com2
serial port address....Serial device1 = com1, serial device2 = com2
external serial connector....Serial device 2
failsafe baud rate....115200
remote terminal type....vt100/vt220
redirection after boot....Enabled
Save the changes and exit.

 

After reboot ssh to your DRAC and type on prompt

/admin1-> console com2

 
You’re welcome
 

Source:

http://mossiso.com/2011/10/17/centos-6-idrac6-and-poweredge-r510.html
http://www.openfusion.net/linux/dell_omsa