From: "Greg Freemyer" <greg.freemyer@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kristin Vadas Marsicano <kristin.marsicano@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: Trouble with hdparm -d on Dell D610
Date: Fri, 11 Jan 2008 16:51:14 -0500 [thread overview]
Message-ID: <87f94c370801111351g132674fam295ba82a78f17842@mail.gmail.com> (raw)
In-Reply-To: <20080111213415.56d90f0d@lxorguk.ukuu.org.uk>
On Jan 11, 2008 4:34 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > most of the machines I encounter (and with both SATA and IDE drives),
> > except for the Dell D610 and HP 7700 (small desktop pc). The models I
> > just mentioned run the shred really slow, which I believe is due to
> > the DMA problem I was having (outlined in my previous emails). Any
> > thoughts?
>
> If your shred program is relying on DMA then you are using the wrong tool
> for the job. The correct way to erase a disk is to send it a security
> erase command. Rewriting over the data may not do what is wanted.
Alan,
I was talking to Kristin this morning about doing that. I was
concerned that there is not anybody certifying that each individual
disk drive model / firmware release is properly implementing the
Security Erase function.
Are you aware of testing body, etc. that publishes a white-list of
drives that are known to have a proper implementation of Security
Erase? Lacking something like that and realizing how rarely it is
used, I'm not sure it should be trusted.
Performing both a Security Erase and calling shred on the drive might
be the ultimate one-two punch.
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 prev parent reply other threads:[~2008-01-11 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 19:18 Trouble with hdparm -d on Dell D610 Kristin Vadas Marsicano
2008-01-11 19:30 ` Alan Cox
2008-01-11 19:49 ` Kristin Vadas Marsicano
2008-01-11 19:55 ` Alan Cox
2008-01-11 20:27 ` Kristin Vadas Marsicano
2008-01-11 21:05 ` Alan Cox
2008-01-11 21:27 ` Kristin Vadas Marsicano
2008-01-11 21:34 ` Alan Cox
2008-01-11 21:49 ` Kristin Vadas Marsicano
2008-01-11 21:54 ` Greg Freemyer
2008-01-12 5:08 ` Mark Lord
2008-01-11 21:51 ` Greg Freemyer [this message]
2008-01-12 0:06 ` Alan Cox
2008-01-14 22:48 ` Kristin Vadas Marsicano
2008-01-14 23:14 ` Alan Cox
2008-01-15 18:26 ` Kristin Vadas Marsicano
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=87f94c370801111351g132674fam295ba82a78f17842@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kristin.marsicano@gmail.com \
--cc=linux-ide@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).