This command will take forever and ever and ever (reads against /dev/random
blocks as the kernel runs out of entropy). /dev/urandom would be better but
still not very fast.
I recently came across a replacement for /dev/urandom called frandom
that the author claims is 10x faster on i686
On Fri, 27 Aug 2010 14:40:05 -0400, Lamar Owen wrote:
[]
As you said: Take a sledge hammer to it.
obFridayHumor
www.harddrivedestruction.com
The videos are worth the look, especially
http://www.youtube.com/watch?v=yISqCAnROh8 (it was a good thing I didn't
have any drink in
Oh, and I *do* have to do at DOD full sanitization: I work at a US gov't
agency, and the machine's being surplused
is dban really certified for DOD full sanitization ?
no: http://www.dban.org/node/52 ?
--
Eero
___
CentOS mailing list
On 27/08/2010 15:48, Peter Kjellstrom wrote:
On Friday 27 August 2010, Kevin Thorpe wrote:
On 27/08/2010 15:19, m.r...@5-cent.us wrote:
I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good dban
1.0.4 that I've used a bunch of times... but on this machine, it says
starting,
I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good dban
1.0.4 that I've used a bunch of times... but on this machine, it says
starting, then dies, saying dban has finished with non-fatal errors.
Check the log for more information It never gets to the interactive menu.
Now that
On 27/08/2010 15:19, m.r...@5-cent.us wrote:
I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good dban
1.0.4 that I've used a bunch of times... but on this machine, it says
starting, then dies, saying dban has finished with non-fatal errors.
Check the log for more information
Hi,
On 27/08/2010 15:19, m.r...@5-cent.us wrote:
I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good dban
1.0.4 that I've used a bunch of times... but on this machine, it says
starting, then dies, saying dban has finished with non-fatal errors.
Check the log for more
On Friday 27 August 2010, Kevin Thorpe wrote:
On 27/08/2010 15:19, m.r...@5-cent.us wrote:
I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good dban
1.0.4 that I've used a bunch of times... but on this machine, it says
starting, then dies, saying dban has finished with
m.r...@5-cent.us wrote:
I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good dban
1.0.4 that I've used a bunch of times... but on this machine, it says
starting, then dies, saying dban has finished with non-fatal errors.
Check the log for more information It never gets to the
On 08/27/2010 08:25 AM, Todd Denniston wrote:
m.r...@5-cent.us wrote, On 08/27/2010 10:57 AM:
Oh, and I *do* have to do at DOD full sanitization: I work at a US gov't
agency, and the machine's being surplused
Suggestion, check with your local DRMO (or whatever they are calling
m.r...@5-cent.us wrote, On 08/27/2010 10:57 AM:
m.r...@5-cent.us wrote:
I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good dban
1.0.4 that I've used a bunch of times... but on this machine, it says
starting, then dies, saying dban has finished with non-fatal errors.
Check the
Todd Denniston wrote:
m.r...@5-cent.us wrote, On 08/27/2010 10:57 AM:
m.r...@5-cent.us wrote:
I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good
dban
1.0.4 that I've used a bunch of times... but on this machine, it says
starting, then dies, saying dban has finished with
On Fri, 2010-08-27 at 09:17 -0700, Benjamin Franz wrote:
Given that modern hard drives can remap damaged sectors automatically,
it is quite possible for an 'erased' drive to still have data on it that
can't be removed by any software based erasure because it can't be
accessed by the OS.
JohnS wrote:
On Fri, 2010-08-27 at 09:17 -0700, Benjamin Franz wrote:
Given that modern hard drives can remap damaged sectors automatically,
it is quite possible for an 'erased' drive to still have data on it that
can't be removed by any software based erasure because it can't be
accessed
On 08/27/2010 10:27 AM, JohnS wrote:
*GRIN* take a Sledge Hammer to it.
Dban at once did not support HPA nor DCO it still may not.
It still doesn't.
There are just a *lot* of ways for a theoretically 'wiped' drive to not
actually be fully wiped.
As you said: Take a sledge hammer to
On Friday, August 27, 2010 02:14:52 pm Benjamin Franz wrote:
There are just a *lot* of ways for a theoretically 'wiped' drive to not
actually be fully wiped.
As you said: Take a sledge hammer to it.
obFridayHumor
www.harddrivedestruction.com
The videos are worth the look, especially
On 08/27/10 7:33 AM, Kevin Thorpe wrote:
Assuming the drive to kill is /dev/sda:
dd if=/dev/random of=/dev/sda
/dev/random is WAY to slow for this. byte at a time, gads, that would
take *days* (hint, use bs=65536 next time you use dd to bulk wipe something)
with modern drives, just
17 matches
Mail list logo
