Subject: Re: Daily crashes, incorrect RAID behaviour
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Carsten Otto <carsten.otto@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <13e988610608150436y6812f623p9919b2d5b1989427@mail.gmail.com>
References: <13e988610608150436y6812f623p9919b2d5b1989427@mail.gmail.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Tue, 15 Aug 2006 13:57:01 +0100
Message-Id: <1155646621.24077.270.camel@localhost.localdomain>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1116
Lines: 24

Ar Maw, 2006-08-15 am 13:36 +0200, ysgrifennodd Carsten Otto:
> The system works normally and suddenly one disk does not respond.
> After a soft reboot the BIOS does not recognize the disk, here a hard
> reboot helps. Whenever I start my normal system in this situation, my

Rule of thumb (and a good one). If the soft reboot and BIOS cannot
recover the disk then the disk is the problem. There isn't really
anything we can tell the drive to do which should make it take a hike
and ignore a reset sequence.  (Should.. however..)

> DriveReadySeekComplete (I do not recall the exact words, sorry) for one disk

Pity the exact text is essential.

> However, after the upgrade to the new power supply the system worked
> fine for almost two weeks (then the weekly crashes started).

I assume you've run memtest86 and also checked temperatures look good
around all the disks.
-
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/