All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Evans <maillists@hosttuls.com>
To: Toby Fisher <toby@tjfisher.co.uk>
Cc: Linux Admin <linux-admin@vger.kernel.org>
Subject: Re: Drive Ready seek errors
Date: Thu, 03 Jun 2004 14:24:23 -0700	[thread overview]
Message-ID: <40BF9707.6070208@hosttuls.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0406031052180.15780@sebagqbbe.gwsvfure.pb.hx>

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.

  parent reply	other threads:[~2004-06-03 21:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  5:02 Drive Ready seek errors Brandon Evans
2004-06-03  9:54 ` Toby Fisher
2004-06-03  9:59   ` Pau Montero Pares
     [not found]     ` <40BF9824.4090002@hosttuls.com>
2004-06-04 10:09       ` Pau Montero Pares
2004-06-04 13:04         ` Chris DiTrani
2004-06-07 17:45         ` Brandon Evans
2004-06-03 21:24   ` Brandon Evans [this message]
2004-06-08 23:29     ` Toby Fisher
2004-06-08 23:30     ` Toby Fisher
2004-06-03 12:30 ` terry white
2004-06-03 21:30   ` Brandon Evans
2004-06-04 10:14     ` Alexander Economou
2004-06-05 10:15     ` a Maxtor story (was: Drive Ready seek errors) markus reichelt
2004-06-05 16:10       ` a Maxtor story Ben Potter
2004-06-05 16:32         ` DragonK
2004-06-05 16:33           ` Ben Potter
2004-06-07 13:46             ` Yu Chen
2004-06-05 18:26           ` Scott Taylor
2004-06-03 13:04 ` Drive Ready seek errors Miguel González Castaños

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40BF9707.6070208@hosttuls.com \
    --to=maillists@hosttuls.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=toby@tjfisher.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.