linux-kernel - Re: Scsi errors with Megaraid 300-8x

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 24 Aug 2006 12:57:27 -0400
From:	Mark Lord <lkml@....ca>
To:	Johan Groth <johan.groth@...ux-grotto.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Scsi errors with Megaraid 300-8x

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/