UPDATE: with TRIM now available for those SSDs that support it (as most do nowadays) this procedure is no longer required. If you have an early drive (eg Intel G1) then you will want to do this secure erase perhaps once a year to keep your SSD at top performance. For those not familiar, secure-erase is an ATA command that most SSD controllers will recognize (i.e. Intel) that will mark all NAND blocks as free, thus returning the drive to the "factory" state and maximum performance. Unfortunately, executing this command can be extremely troublesome as it turns out. HDDErase is the most common utility, but requires a BIOS equipped computer to run (aka a PC). Even then, SATA controller and BIOS support for this utility is spotty at best... it wouldn't work on my friends Dell PC and there are numerous reports across a variety of forums of all kinds of motherboards failing to work with this utility. Fortunately, I was able to piece a couple of nuggets together from a couple of different sources that actually allowed me to execute the secure-erase on my 2009 Mac Pro. (BTW, I can't see why this won't work on any Intel Mac from laptops to workstations). Here's what's required: To keep things simple, I would recommend you pull all your other SSD's and HDD's from your Mac Pro... only use the optical drive and the target drive (one at a time if you have multiple). #1 Prep your SSD's by ensuring their firmware is up to date. For Intel SSD's this thread may help in that regard (post #11)... http://forums.macrumors.com/showthread.php?t=686672 #2 Unfreeze your SSD: This is required because the firmware for the on-board SATA connectors "freezes the drive" (to use the ATA nomenclature) making it unable to accept the secure-erase command. There are at at least 3 reported ways to solve this... Option A: Attaching the target drive via a USB enclosure eliminates this issue. This is the method I used. Get A USB enclosure or dock for your SSD. Apparently eSATA enclosures may also work if that's more convenient for you. Option B: Use the Disconnect/Reconnect method. There are a few people reporting success with unfreezing their drives using the technique of disconnecting and reconnecting them to the Sata connection during boot... Here's the process in detail from post #69: Option C: Sleep the computer to unfreeze the drive? This hasn't been verified with the Linux disk recommended below but people have reported success with this method using Ubuntu 10.04 LTS (see post #100 and post #142 and post #168 and post #169) #3 Prep a GParted Live bootable Linux CD. Burn the following ISO to a blank CD or DVD to boot with (using either Disk Utility or your favorite burning utility)... http://sourceforge.net/projects/gparted/files/gparted-live-stable/ Of course, to boot this you have to hold the "Option" key during startup to invoke the startup disk options... select the CD. At the end of the boot sequence, you have the option to use the X GUI or command line. The GUI mode does not support widescreen display resolutions. So unless you have an old-school 4:3 monitor around (like I did), or your display supports 4:3 resolutions (the 24" ACD does not), you will have to use the command line. If you get to the GUI, you will get a screen that looks like this... The key benefit of the GUI is getting the device ID for the drive as circled above. However, if you don't get the GUI, and you only have one drive (the target SSD) connected as I recommended, then it will always assign the device ID of "/dev/sda" so you don't really need the GUI. #4 Command Line Steps. Armed with the device ID or assuming "/dev/sda" if you never got to the GUI, you then follow these instructions exactly... (you can get to the command line from the GUI by double-clicking the "Terminal" icon) http://peter.membrey.hk/2011/09/11/...structions-on-how-to-securely-erase-your-ssd/ Notes on the command line steps: - These steps will wipe all your data... be sure you have backed up or don't care about loosing the contents of your drive - Step 1: the first time I entered the hdparm command at the command line, I got an error. Try again. For some reason, it always gave me an error the first time but then worked properly for all subsequent commands. - Step 1A: This is enabled by using the USB enclosure mentioned above. If you try to do this operation with the SSD connected to your main board SATA ports, you will find the drive "frozen" - Step 2: This password assignment step is left out of most tutorials on this subject which is odd, because it won't work without it. Simply follow the instructions exactly as shown and it will work fine. I think that covers it... of course, YMMV and I'm not responsible if you blow up your computer and all that crap!