From: "Kristin Vadas Marsicano" <kristin.marsicano@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: Trouble with hdparm -d on Dell D610
Date: Fri, 11 Jan 2008 16:49:38 -0500 [thread overview]
Message-ID: <7f68de3e0801111349i2518924bj7bcfd7b5e9c604e2@mail.gmail.com> (raw)
In-Reply-To: <20080111213415.56d90f0d@lxorguk.ukuu.org.uk>
On 1/11/08, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > My concern with disabling the new drivers is as follows: I use this
> > linux kernel and config image to boot machines over PXE and call a
> > shred program on each of the harddrives. If I turn off CONFIG_ATA,
> > will this limit my ability to support various new IDE and SATA drives
> > for running shred? So far, the configuration I have works well with
>
> Yes. In that case you can build without CONFIG_IDE_PIIX and with the
> CONFIG_ATA_PIIX driver and you should be fine too (but your disk will
> move to /dev/sda on that box). The PIIX is an awkward case as in some
> modes it combines both the SATA and PATA onto one 'device'.
>
Can I set this option through make menuconfig, or do I need to take
some other action? I poked around the menu config a big and wasn't
sure I found the properties you are refering to.
Would all my disks then be listed as sd[a-z] on every machine? Or just some?
> > 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.
>
For now, my desired action is to overwrite the drives with random
characters. My understanding is that security erase commands are
implemented in the firmware, and that it may be buggy. Please correct
me if my understanding is incorrect. Also, is there a way to invoke
the firmware security erase with a linux command?
--
Kristin Vadas Marsicano
kristin.marsicano@gmail.com
kristinisme.blogspot.com
next prev parent reply other threads:[~2008-01-11 21:49 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 [this message]
2008-01-11 21:54 ` Greg Freemyer
2008-01-12 5:08 ` Mark Lord
2008-01-11 21:51 ` Greg Freemyer
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=7f68de3e0801111349i2518924bj7bcfd7b5e9c604e2@mail.gmail.com \
--to=kristin.marsicano@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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).