public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Johan Groth <johan.groth@linux-grotto.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scsi errors with Megaraid 300-8x
Date: Thu, 24 Aug 2006 12:57:27 -0400	[thread overview]
Message-ID: <44EDDA77.40307@rtr.ca> (raw)
In-Reply-To: <44EDC135.4080007@linux-grotto.org.uk>

Johan Groth wrote:
> Mark Lord wrote:
>
>> OPPORTUNITY FOR FAME AND FORTUNE! (okay, maybe just some fame):
>> =================================
>> Hack the existing smartctl code to read out the failed sector numbers,
>> and then issue single-sector read-overwrite to each of those bad sectors.
>>
>> Very simple code.  I'll do it myself eventually, but please beat me to 
>> it!
> 
> Authors of badblocks already has with the -n option :)

Not quite.  As you pointed out:

> I would like to run badblocks again but only around the damaged part. 

The drive *knows* which sectors are bad -- it's mostly all in the S.M.A.R.T.
logs and such.  Which smartctl already knows how to read.

So now we just need a script-kiddie to do a nice little awk script for you,
which extracts the bad sectors info from the output of smartctl, and then
feeds this as input to badblocks.

Cheers

      reply	other threads:[~2006-08-24 16:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 14:45 Scsi errors with Megaraid 300-8x Johan Groth
2006-08-23 15:27 ` Mark Lord
2006-08-23 15:42   ` Johan Groth
2006-08-23 15:45     ` Justin Piszcz
2006-08-23 15:48       ` Johan Groth
2006-08-23 15:53         ` Justin Piszcz
2006-08-23 15:57           ` Johan Groth
2006-08-23 15:59             ` Justin Piszcz
2006-08-24 14:48         ` Mark Lord
2006-08-24 15:09           ` Johan Groth
2006-08-24 16:57             ` Mark Lord [this message]

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=44EDDA77.40307@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=johan.groth@linux-grotto.org.uk \
    --cc=linux-kernel@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