That means it is subject to exactly the same limitations! That OS X daily article mentions but glosses over the fact that, as it says, the srm method is nothing more than equivalent to the now removed Disk Utility option. The irony of this is that Apple is in fact trying to discourage users from relying on "secure" erase options that are not really effective or reliable, thus making it much easier for those agencies the headlines scream about to recover data from users' drives if they rely on any of those methods, including command line tools like srm. I am suspect these days, given the headlines, when talking about security and everyday terms such as 'wear-and-tear' are used - as they seem to be convenient to placate the novices.
#SECURE ERASE EL CAPITAN FREE#
Underlying error: 1: POSIX reports: Operation not permittedīut better than erasing free disk space is secure erase - which is also still available in Terminal, and explained in this article. MacBook-Pro:~ $ diskutil secureErase freespace 1 /dev/disk1Įrror: -69847: Couldn't create temporary file Nevertheless, it worked as Wondershare's data recovery app found absolutely nothing. The error (69847) happened in Yosemite too (when I got my mac) so it looks like the same thing. I just did a 1 pass, but it took a LOT longer than when the feature was in Disk Utility. I am suspect these days, given the headlines, when talking about security and everyday terms such as 'wear-and-tear' are used - as they seem to be convenient to placate the novices.īelow is my experience from running the command. Thanks R C-R, and Old Toad, I stand corrected. I'm assuming this "Internal,virtual" drive has something to do with the fact that I enabled that FileVault encryption thing, so this is related to mounting the unencrypted drive (my guess).but if I DO perform secureErase, I'm supposed to do it to the Apple_CoreStorage (physical) Macintosh HD, right? Not the Apple_HFS (virtual) one? Complete NOOB question, sorry.
I also have a stupid (related) question.when I perform "diskutil list" in the terminal window (so I can find the exact name of the drive for which I want to erase the free space), I have two "Macintosh HD" volumes listed.one is "Apple_CoreStorage" under /dev/disk0 (internal,physical), and the other is "Apple_HFS" under dev/disk1 (internal, virtual). Has anyone that reads this thread been able to successfully run this command? Any pitfalls to look out for so I don't brick my laptop? DEFINITELY back up your computer first if you are considering using this command. I've read more than a few comments from people saying that running this utility creates a temp file to create the overwrite data to securely erase your free space, and that if your hard drive doesn't have enough free space to hold this temp file (someone said "More than half" of the hard drive should be free), you could end up with this situation where your computer locks up and bad things happen while running secureErase, so I'm sort of scared to try it.
I have discovered that you can perform the secure erase free space function from the terminal window using the diskutil secureErase freespace command, as described in the article below.
0 kommentar(er)
