Subject: Re: Detecting I/O error and Halting System
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: zine el abidine Hamid <zine46@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20060328150712.85169.qmail@web30602.mail.mud.yahoo.com>
References: <20060328150712.85169.qmail@web30602.mail.mud.yahoo.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Tue, 28 Mar 2006 16:36:03 +0100
Message-Id: <1143560163.17522.29.camel@localhost.localdomain>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 899
Lines: 27

On Maw, 2006-03-28 at 17:07 +0200, zine el abidine Hamid wrote:
> I don't think that it's a HDD problem nor a cable
> problem because the servers are new. We have tried

New. Thats another word for "untested" I believe 8)

> How can I determine the problem?

I would consult the hardware vendor

> I want to add that the HDD seems to be disconnected
> (the BIOS can't find any drive for boot) after a
> simple reset. We must switch off the servers to get
> them work again.

Thats strongly indicating a hardware problem.

> (http://www.tldp.org/LDP/lkmpg/) but how can I
> shutdown Linux from inside a module...? 

See the softdog driver for an example.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/