linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maarten van den Berg <maarten@ultratux.net>
To: linux-raid@vger.kernel.org
Subject: Re: Raid5 Construction Question
Date: Thu, 19 Aug 2004 23:50:35 +0200	[thread overview]
Message-ID: <200408192350.35339.maarten@ultratux.net> (raw)
In-Reply-To: <20040819202601.GA14858@mutsumi.mindwaresystems.com>

On Thursday 19 August 2004 22:26, Kourosh wrote:
> On Thu, Aug 19, 2004 at 10:24:06PM +0200, Maarten van den Berg wrote:
> > On Thursday 19 August 2004 19:52, PAulN 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.

I did not do this for multiple reasons.
The first -and by far the most important one- was that I desperately needed 
the data that was on the broken array (it all stemmed from a two-disk raid5 
failure).  I do not trust these vendor-diskettes to leave my data intact.

Secondly it was far easier for me to run this dd test under linux than find a 
loose floppydrive, connect it to my server, reinstate IRQ 6 and run various 
floppies against it.

And third, as the system had multiple identical promise addon controllers and 
7 mostly identical ide disks, I figured I couldn't be totally sure the disk 
linux saw as /dev/hdm was disk ??? on controller ?? as reported by such 
floppies.

I do recommend those utilities for a final go / no-go verdict, but you better 
run them on standalone systems on single disks.  
Or maybe I'm just being too paranoid is all...?

Maarten


  parent reply	other threads:[~2004-08-19 21:50 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
2004-08-19 21:50         ` Maarten van den Berg [this message]
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=200408192350.35339.maarten@ultratux.net \
    --to=maarten@ultratux.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).