linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rob <rob@fantinibakery.com>
To: linux-raid@ied.com
Cc: Jason Lunz <lunz@falooley.org>, linux-raid@vger.kernel.org
Subject: Re: recovery of hosed raid5 array
Date: Sat, 11 Oct 2003 21:14:38 -0400	[thread overview]
Message-ID: <3F88AAFE.7060101@fantinibakery.com> (raw)
In-Reply-To: <no.Yo.24973.N.nN.0310111457280@business.com>

What IS  "smartctl" ?

linux-raid@ied.com wrote:

> Hi,
>
>On Sat, 11 Oct 2003, Jason Lunz wrote:
>
>  
>
>>Date: Sat, 11 Oct 2003 15:52:40 +0000 (UTC)
>>From: Jason Lunz <lunz@falooley.org>
>>To: linux-raid@vger.kernel.org
>>Subject: recovery of hosed raid5 array
>>
>>    
>>
>[...]
>  
>
>>Once the rebuild started, I noticed an email from smartd, saying that
>>the _other_ drive on the Promise controller (/dev/hde) had had errors.
>>So I foolishly checked it out with smartctl,
>>    
>>
>
>  Can you please share with us newbies why using "smartctl" 
>in such situation is foolish, so we don't make the same 
>mistake ?
>
>  Thanks.
>
>    John
>
>
>[...]
>  
>
>>at which point everything
>>went to hell. /dev/hde now clicks repeatedly and refuses to work for
>>more than a minute or so, while /dev/hdg is partially destroyed from
>>being re-added. The rebuild was 3-4% complete when hde died.
>>    
>>
>
>
>  
>


  reply	other threads:[~2003-10-12  1:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-11 15:52 recovery of hosed raid5 array Jason Lunz
2003-10-11 18:59 ` linux-raid
2003-10-12  1:14   ` rob [this message]
2003-10-12 15:14   ` Jason Lunz
2003-10-12 17:39     ` dean gaudet
2003-10-12 18:04       ` Jason Lunz
2003-10-12 18:34         ` dean gaudet
2003-10-13 13:54       ` Dragan Simic
2003-10-13 17:00         ` dean gaudet
2003-10-26 19:40       ` Mike Fedyk
2003-10-26 19:48         ` Jason Lunz
2003-10-26 21:29         ` dean gaudet

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=3F88AAFE.7060101@fantinibakery.com \
    --to=rob@fantinibakery.com \
    --cc=linux-raid@ied.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lunz@falooley.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).