devnull

Man of many talents. Server janitor, Chief Googler, Vice President of Pencil Sharpening, Director of Turning Things Off and On Again. Technology Plumber using Linux for stuff like Satellite STB, home CCTV system, kitchen sound bar, workstations, even car onboard computer. And servers, oh yeah - lots of them. I've been a Linux Mercenary for quite a while now, often using information posted by kind strangers on the Internet to solve problems during this journey. This blog is a humble attempt to give something back to the community.

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.

Oct 202016
 

A different, non-Linux story today. I own Peugeot 4007 4×4 SUV – a nice car that drives remarkably well and is highly regarded by the whole family. I would probably never buy a French car (no offence, my dear French audience) but this one is made in Japan, in the exactly same plant as Mitsubishi Outlander and Citroen C-Crosser. All of these three cars look almost exactly the same, the difference being engine fitted and few details outside.

4007 (AKA four double O seven) and C-Crosser (AKA crossdreser) siblings are fitted with an excellent 2.2 HDI FAP engine, a powerful and lively unit.

Now, to the point – my engine was seemingly running fine but, as I love tinkering with stuff, I hooked up ELM237 based Bluetooth OBD dongle into diagnostic socket to see if there are any errors recorded. After starting Torque it turned out that there are indeed two faults stored, P1351 and P2408. Googling these faults took me to Peugeot owners forum where it was revealed that

P1351, idm input circuit malfunction,
P2408, fuel cap sensor / switch circuit.

screenshot_2016-09-28-17-13-00

First problem relates to faulty glow plug/plugs. Although it’s quite still warm outside (they aren’t normally needed, only when temp drops to around 0C, allegedly) in this particular engine glow plugs are used to initiate and help with FAP* regeneration cycle, by bringing up temp in exhaust manifold and burn soot accumulated in filter. As far as I understand.

If you are hit with this issue a general advice is to check the relevant relay in engine compartment fuse box first and if that’s OK – replace all four glow plugs. Not so easy to change them if you don’t have a ramp as they sit on the bottom front of the engine. Certainly not a job that can be done on the driveway, besides, glow plugs have a nasty tendency to snap when they’re being removed which turns a simple job into a horror story. I can do simple stuff but this, no thank you. I decided to entrust with this bit to a local garage.

A day later, glow plugs replaced but faults despite clearing are coming back. Hmmm…. OK, lets leave this for now and focus on part two.

Second fault, fuel cap sensor. Why a fuel cap needs a sensor in the first place? It’s because every time you put a diesel into a tank, a tiny amount of special additive (eolys) is being injected into a tank. It helps to lower down fumes burn temperature to assist above mentioned FAP regeneration cycle. Something like that.

Now, how did I fix the second problem? Before diving into locating and replacing this sensor I tried to: check cap to see if there are still two magnets, remove fuel cap, start engine, switched off engine, put the cap back on. Started engine again and went for a short spin to the town. Now the best part. After connecting OBD and running diagnostic again result was: oh my Lord, no stored faults!

Not sure what is logic/magic behind this. I read something that ECU needs some time, few start stop cycles to remove faults. Re fuel cap, maybe ECU lost signal and only removing cap “reset” the system? Anyway, it was somehow related to glow plugs as these problems often show up on Peugeot forums in pairs.

Hope this will help someone who is facing similar problem. Those cars are not so popular, information on the internet are scarce and not very clear. Here with a cheap OBD dongle, cheap Android app I managed to diagnose and solve a problem that would normally result in hefty charge from Peugeot dealer.


* FAP is French for DPF (Diesel Particulate Filter). FAP catches diesel particulates in a silicon carbide filter. It then eliminates them by burning at a high temperature in a ‘regeneration’ process controlled by the engine’s computer.