Defense in depth is the reason.
Okay, but a single pass of /dev/zero will destroy all the data beyond hope of recovery.
Encrypting the hard drive and then removing the key has a better chance of rendering the data unusable.
11–20 of 153 posts
Defense in depth is the reason.
Okay, but a single pass of /dev/zero will destroy all the data beyond hope of recovery.
Encrypting the hard drive and then removing the key has a better chance of rendering the data unusable.
Defense in depth is the reason.
Okay, but a single pass of /dev/zero will destroy all the data beyond hope of recovery.
There's almost certainly secure ways to delete. But not worth it for a five year old drive that may have had sensitive information on it.
Defense in depth is the reason.
Okay, but a single pass of /dev/zero will destroy all the data beyond hope of recovery.
Defense in depth is the reason.
Okay, but a single pass of /dev/zero will destroy all the data beyond hope of recovery.
[1] https://nascompares.com/2022/09/12/wd-red-pro-22tb-hard-driv...
Since when does bbc run ads pretending to be articles? This is an ad for cdi.
Defense in depth is the reason.
Okay, but a single pass of /dev/zero will destroy all the data beyond hope of recovery.
There are methods available that will allow recovery of second, third or even fourth generation data to be recovered from magnetic disks. Writing /dev/zero "over" an SSD won't necessarily accomplish what you expect either.
Defense in depth is the reason.
Earlier quoted context omitted.
Okay, but a single pass of /dev/zero will destroy all the data beyond hope of recovery.
For an actual HDD, maybe that would work. For any solid state drive, it would definitely not work. SSDs and similar spread writes across pools of blocks for 'endurance', so a 1TB drive might actually have 2TB worth of flash on it.