From: "Greg Freemyer" <greg.freemyer@gmail.com>
To: "Mark Lord" <lkml@rtr.ca>, "Philipp Thomas" <pth@suse.de>
Cc: "Gene Heskett" <gene.heskett@gmail.com>,
"Mikael Pettersson" <mikpe@it.uu.se>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux ide Mailing list" <linux-ide@vger.kernel.org>
Subject: Make_bad_sector
Date: Tue, 29 Jan 2008 10:39:21 -0500 [thread overview]
Message-ID: <87f94c370801290739t39640bf5w960576ae4b273156@mail.gmail.com> (raw)
On Jan 28, 2008 3:43 PM, Mark Lord <lkml@rtr.ca> wrote:
> Gene Heskett wrote:
> > On Monday 28 January 2008, Mark Lord wrote:
> >..
> >> Another way is to use the "make_bad_sector" utility that
> >> is included in the source tarball for hdparm-7.7, as follows:
> >>
> >> make_bad_sector --readback /dev/sda 474507
> >>
> > Apparently not in the rpm, darnit.
> ..
>
> That's okay. It should still be in the SRPM source file.
> And it's a tiny download from sourceforge.net:
>
> http://sourceforge.net/search/?type_of_search=soft&type_of_search=soft&words=hdparm
>
Mark,
I asked on the SUSE list and was informed by Philipp Thomas of Novell
(cc'ed) that the only mention of make_bad_sector in the hdparm-7.7
source is in a todo list.
Sounds like a useful tool, so I was hoping to encourage suse to
include it with future releases.
Thanks
Greg
--
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
next reply other threads:[~2008-01-29 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 15:39 Greg Freemyer [this message]
2008-01-29 16:16 ` Make_bad_sector Mark Lord
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=87f94c370801290739t39640bf5w960576ae4b273156@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=gene.heskett@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mikpe@it.uu.se \
--cc=pth@suse.de \
/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
all inboxes | Powered by JetHome®