From mboxrd@z Thu Jan  1 00:00:00 1970
From: Brandon Evans <maillists@hosttuls.com>
Subject: Re: Drive Ready seek errors
Date: Thu, 03 Jun 2004 14:24:23 -0700
Sender: linux-admin-owner@vger.kernel.org
Message-ID: <40BF9707.6070208@hosttuls.com>
References: <40BEB0E7.306@hosttuls.com> <Pine.LNX.4.58.0406031052180.15780@sebagqbbe.gwsvfure.pb.hx>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-admin-owner@vger.kernel.org>
In-Reply-To: <Pine.LNX.4.58.0406031052180.15780@sebagqbbe.gwsvfure.pb.hx>
List-Id: <linux-admin.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: Toby Fisher <toby@tjfisher.co.uk>
Cc: Linux Admin <linux-admin@vger.kernel.org>

Toby Fisher wrote:
> On Wed, 2 Jun 2004, Brandon Evans wrote:
> 
> 
>>Lately, a lot of my Linux boxes have had hard drive failures.  There are 
>>about 15 servers running raid 1 on Red hat 7.3.  Does anyone have any 
>>suggestions, maybe some good doc's, on hard drive troubleshooting / 
>>tuning?  Some of the failed hard drives are only a couple months old, 
>>and have already been replaced twice, so I suspect a faulty ide 
>>controller.   What is a good IDE controller card to buy for Linux?
> 
> 
> I can't answer the question about the controller cards, but have you 
> considered using smartd?  It should give you some warning that your drives 
> are on the way out.   In addition, if this is happening across several 
> boxes, it is possible that kernel configuration is a problem.  How do 
> these drives fail?  What kinds of errors do you get?
> 
> --- 
> Toby Fisher	Email: toby@tjfisher.co.uk
> Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
> ICQ: #61744808
> -

I havent used smartd yet, but I will look into it.  The kernel 
configuration could be a problem,
since redhat stoped supporting 7.3, I have been building our own for 
security reasons.  I'll
search around the kernel archive.

Here is the error log from one of the servers.

Jun  2 17:31:20 server1 kernel: ide0: reset: success
Jun  2 17:31:21 server1 kernel: hda: write_intr error1: nr_sectors=1, 
stat=0x51
Jun  2 17:31:21 server1 kernel: hda: write_intr: status=0x51 { 
DriveReady SeekComplete Error }
Jun  2 17:31:21 server1 kernel: hda: write_intr: error=0x10 { 
SectorIdNotFound }, LBAsect=234436369, sector=232219399
Jun  2 17:31:21 server1 kernel: hda: write_intr error1: nr_sectors=1, 
stat=0x51
Jun  2 17:31:21 server1 kernel: hda: write_intr: status=0x51 { 
DriveReady SeekComplete Error }
Jun  2 17:31:21 server1 kernel: hda: write_intr: error=0x10 { 
SectorIdNotFound }, LBAsect=234436369, sector=232219399
Jun  2 17:31:21 server1 kernel: hda: write_intr error1: nr_sectors=1, 
stat=0x51
Jun  2 17:31:22 server1 kernel: hda: write_intr: status=0x51 { 
DriveReady SeekComplete Error }
Jun  2 17:31:22 server1 kernel: hda: write_intr: error=0x10 { 
SectorIdNotFound }, LBAsecttr error1: nr_sectors=1, stat=0x51
Jun  2 17:31:22 server1 kernel: hda: write_intr: status=0x51 { 
DriveReady SeekComplete Error }
Jun  2 17:31:22 server1 kernel: hda: write_intr: error=0x10 { 
SectorIdNotFound }, LBAsect=234436369, sector=232219399
Jun  2 17:31:22 server1 kernel: hda: write_intr error1: nr_sectors=1, 
stat=0x51
Jun  2 17:31:22 server1 kernel: hda: write_intr: status=0x51 { 
DriveReady SeekComplete Error }
Jun  2 17:31:22 server1 kernel: hda: write_intr: error=0x10 { 
SectorIdNotFound }, LBAsect=234436369, sector=232219399
Jun  2 17:31:22 server1 kernel: ide0: reset: success



-- 
Thanks,
     Brandon E.