How to wipe/erase hard drives clean so data cannot be recovered for privacy reasons

This is something many people and especially businesses worry about, or at least they should.  Before throwing away a hard drive, returning a hard drive, or especially Warrantying/RMAing it, you should wipe the drive.

Linux provides the "shred" and "dd" utlities which work quite well.  It seems even a single pass is good enough but by default shred will do 3 passes.

Here\'s an example of using shred in Linux (I use a custom made distribution from a USB key):

/shred -v /dev/sdd
./shred: /dev/sdd: pass 1/3 (random)...
./shred: /dev/sdd: pass 1/3 (random)...585MiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...1.0GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...1.4GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...1.8GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...2.3GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...2.7GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...3.1GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...3.6GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...4.0GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...4.5GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...4.9GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...5.4GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...5.8GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...6.3GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...6.7GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...7.2GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...7.6GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...8.0GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...8.5GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...8.9GiB/932GiB 0%
./shred: /dev/sdd: pass 1/3 (random)...9.4GiB/932GiB 1%
./shred: /dev/sdd: pass 1/3 (random)...9.8GiB/932GiB 1%
./shred: /dev/sdd: pass 1/3 (random)...10GiB/932GiB 1%
./shred: /dev/sdd: pass 1/3 (random)...11GiB/932GiB 1%
./shred: /dev/sdd: pass 1/3 (random)...12GiB/932GiB 1%
./shred: /dev/sdd: pass 1/3 (random)...13GiB/932GiB 1%
./shred: /dev/sdd: pass 1/3 (random)...14GiB/932GiB 1%
./shred: /dev/sdd: pass 1/3 (random)...15GiB/932GiB 1%
./shred: /dev/sdd: pass 1/3 (random)...16GiB/932GiB 1%
./shred: /dev/sdd: pass 1/3 (random)...17GiB/932GiB 1%

 

You can also use dd and some suggest it works just as well even once:

dd if=/dev/zero of=/dev/sdyourdrivedevice bs=16M


Tags:

erase, recovered, reasonsthis, businesses, warrantying, rmaing, linux, provides, quot, shred, dd, utlities, default, custom, usb, dev, sdd, mib, gib, sdyourdrivedevice, bs,

Latest Articles

  • VMWare Pro Workstation Nic Disconnected and No IP Using NAT
  • Linux How To Create A RamDisk
  • mdadm force resync when resync=PENDING solution
  • Proxmox Breaks Storage/LVM Backing If Killing QEMU-IMG
  • Proxmox trying to acquire lock... TASK ERROR: can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout
  • Debian 9 SSH root password authentication failure password not working problem / solution
  • QEMU / KVM How To Manually Create Basic Virtual Machine VM
  • Linux wlan0 check all wireless clients
  • PHP Issues With Decoding Strange Smart Quotes And Non-Standard ASCII Characters
  • /etc/iproute2/rt_tables default settings file in Linux Centos 6,7 and most other NIX's
  • bind named error solutions named[2169]: error (no valid DS) resolving / error (broken trust chain) resolving / : error (no valid RRSIG) resolving 'com/DS/IN':
  • iptables how to log ALL dropped incoming packets
  • How To Edit Linux Based NM Network Manager Connection Settings Without GUI
  • Linux Disable IPV6 Centos / Debian / Mint Howto
  • Linux use growisofs to burn a larger file on a BD-R / Bluray Disc
  • Linux partprobe/partx cannot access last and 4th partition
  • DRBD Errors Caused By Physical Corruption
  • mdadm: add new device failed for /dev/sdb4 as 3: Invalid argument solution
  • Linux named / bind how to dump, view and clear the cache!
  • Centos 6 / 7 / 8 How To Change Default nameservers in /etc/resolv.conf when using DHCP / dhclient