topic Re: RHEL4 System unresponsive when a disk crash on smartarray in Operating System - Linux

RHEL4 System unresponsive when a disk crash on smartarray

Charles Castelain_1 — Thu, 23 Nov 2006 05:20:33 GMT

Hello,

Here is my problem :

On a BL25PG1 I have a smartarray 6i with the battery write cache and 2x36Gb disks in mirror.
A few days ago one of my disk crashes and the systems stop to reponds.
It was still pingable but no more ssh,...

Here is what I have in the message log :

Nov 18 21:48:38 servername Event Log Daemon:[4412]: SCSI bus speed downshift occurred:Port 0 Box 1 of Embedded Array Controller.
Nov 18 21:49:23 servername last message repeated 2 times
Nov 18 21:49:23 servername Event Log Daemon:[4412]: Physical drive failed: SCSI Bus 1 Target 1 of Embedded Array Controller.
Nov 18 21:49:27 servername Event Log Daemon:[4412]: Logical drive 1 of Embedded Array Controller, has changed from status OK to INTERIM RECOVERY MODE
Nov 20 13:47:35 servername syslogd 1.4.1: restart.

The system stop to respond just after the disk blown.

RedHat thinks the problem is hardware related.

Anyone with the same behaviour? Problem?
Any idea?

Regards,

Charles Castelain

Re: RHEL4 System unresponsive when a disk crash on smartarray

Jean-Yves Picard — Thu, 23 Nov 2006 08:32:54 GMT

Hello,

The most important information is missing :
how is your array configured ?

I had several crash of disk in bl20G3 without any problem on Linux.
I had the 2 physical disks set into 3 mirrored partitions ( 3 logical disk seen by linux)
I run proliant support pack 7.1 or 7.4
My Linux is RedHat Enterprise 3 Update 2 or RH4U0

Jean-Yves Picard

Re: RHEL4 System unresponsive when a disk crash on smartarray

Charles Castelain_1 — Thu, 23 Nov 2006 08:36:03 GMT

Hello,

On a BL25PG1 I have a smartarray 6i with the battery write cache and 2x36Gb disks in mirror.

And for the fs :

/boot of 100Mb primary part
swap of 8gb primary part
/ of 8gb primary part
rest as vg00

Regards,

Charles Castelain

Re: RHEL4 System unresponsive when a disk crash on smartarray

TANHM — Fri, 01 Dec 2006 03:28:58 GMT

Hi Charles,

I think u can logged a call to the vendor, ask them to perfom a diag test on it and make sure the array controller are being configure properly. Please make sure the hardware engineer have a good knowledge on linux.

I believe 90% is due to hardware issue. I used to encounter such situation and the root cost is the raid card configuration problem.

Re: RHEL4 System unresponsive when a disk crash on smartarray

Charles Castelain_1 — Fri, 01 Dec 2006 03:50:04 GMT

Hello,

Yes. This is in my plan and what have been suggested by RedHat.

But do I need a special support contract since this system is just covered by it's one year warranty...

Do you often have the problem?

Regards,

Charles Castelain

Re: RHEL4 System unresponsive when a disk crash on smartarray

Charles Castelain_1 — Fri, 01 Dec 2006 03:55:14 GMT

Hello,

What do I need to check at the configuration level of the smartarray?

When I setup a server I just use ilo.
Stop the boot to enter the smartarray config.
Choose my raid setup.
Create my "volume".
Save my config.
Reboot.

Is there something I must verify at the server level?

Start my kickstart install.

Right now the only problem I have found are the following :

Impossible to install if a ram stick is dead even when the system claims it had disabled it.
Impossible to install RedHat4 update 3 on a bl25p via ilo. It bombs the blade when it tries to format the disks.

All the other installations are coming fine and smoothely.

Regards,

Charles Castelain

Re: RHEL4 System unresponsive when a disk crash on smartarray

TANHM — Sun, 03 Dec 2006 21:33:21 GMT

Hi Charles,

Then u need to check with the reseller or HP, depends on whether u bought directly from HP.

I think u just need to have a normal h/w contract, i believe any new h/w will come with a contract, in your case, i think is cover as it is a h/w related issue (h/w configuration problem).

Re: RHEL4 System unresponsive when a disk crash on smartarray

George Liu_4 — Mon, 04 Dec 2006 09:07:54 GMT

Most of that kind of problems are caused by kernel bugs. Try to use an old kernel.