All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Hardy <mhardy@h3c.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid5 Construction Question
Date: Thu, 19 Aug 2004 13:39:13 -0700	[thread overview]
Message-ID: <41250FF1.9010401@h3c.com> (raw)
In-Reply-To: <20040819202601.GA14858@mutsumi.mindwaresystems.com>


Using the SMART protocol to automatically test and monitor them (after a 
full test when I first build the box is how I typically steer clear of 
these things.

I've only done more err...budget setups using IDE but apparently it 
works well on SCSI too:

http://smartmontools.sourceforge.net/smartmontools_scsi.html

You could very quickly issue a full test command to all the drives then 
come back later and check them to make sure they completed correctly

-Mike

Kourosh wrote:

> I've found that one of the better ways of varifying a disk is to run 
> the disk manufacturers disk utilities on it.  They all provide a 
> bootable disk to run the utilities.  Several times I've had problems 
> similar to this and each time it ended up being a disk that was 
> failing.  Run the utility as all the vendors I've dealt with require 
> the error code from the utility to process an RMA, so might as well do 
> it sooner, rather than later.
> 
> You could also try low-level formating each disk using the SCSI 
> controllers utilities.  IIRC it should remap any bad blocks.
> 
> Hope this helps,
> 
> Kourosh

  reply	other threads:[~2004-08-19 20:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 17:24 Raid5 Construction Question PAulN
2004-08-19 17:30 ` Guy
2004-08-19 17:52   ` PAulN
2004-08-19 18:17     ` Guy
2004-08-19 18:24       ` PAulN
2004-08-19 18:29         ` Guy
2004-08-19 18:35       ` Gordon Henderson
2004-08-19 20:24     ` Maarten van den Berg
2004-08-19 20:26       ` Kourosh
2004-08-19 20:39         ` Mike Hardy [this message]
2004-08-19 21:50         ` Maarten van den Berg
2004-08-19 21:55           ` Guy
2004-08-19 20:53       ` Guy
2004-08-20  1:21     ` Neil Brown
2004-08-20  1:56       ` Guy
2004-08-20  2:01         ` Neil Brown
2004-08-20  4:53       ` Paul Nowoczynski
2004-08-19 18:32 ` Tim Moore
2004-08-19 20:30   ` Maarten van den Berg
2004-08-23 15:24     ` Tim Moore
2004-08-23 15:27       ` Gordon Henderson
  -- strict thread matches above, loose matches on Subject: below --
2004-08-20  5:17 Mike Baynton
2004-08-20  6:52 ` Guy

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=41250FF1.9010401@h3c.com \
    --to=mhardy@h3c.com \
    --cc=linux-raid@vger.kernel.org \
    /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.