5 ms·

Same as erasing any other type of disk. Why do you think its any different?

by db48x 5y ago

fsflover 5y ago
Because you need to trust its firmware that the data is actually gone. Unless it's free firmware, I wouldn't trust that.
- db48x 5y ago
  Like I said, no different from any other disk.
quijoteuniv 5y ago
It seems that SSD info can be recovered. https://itigic.com/safely-erase-an-ssd-before-selling-or-throwing-it-away/ https://itigic.com/safely-erase-an-ssd-before-selling-or-thr... https://www.zdnet.com/article/how-to-securely-erase-hard-drives-hdds-and-solid-state-drives-ssds/ https://www.zdnet.com/article/how-to-securely-erase-hard-dri... This company claims is not possible unless you use their software, DBAN will not work. https://www.blancco.com/ https://www.blancco.com/ I am trying to recycle unused computers from companies, and install Linux in them and there is a bit of vacuum in terms of how to erase/comply... som services use Blancco, some companies remove the hardrives before disposing of the computers, making recycling more expensive, need to buy a new hardrive and fix them.
- db48x 5y ago
  The classic Linux shred command will work just fine, same as on any type of disk. But what you should actually do use use the drive’s built–in instance secure erase feature. This changes the encryption key to a new one, so all existing data is rendered permanently unavailable. Not all drives have disk encryption, but when they do it works the same way whether it’s an SSD or spinning rust. Use hdparm’s --sanitize-crypto-scramble command–line option to do this. Some drives only have an older feature that does a secure erase that overwrites every block in the device. This is much slower, so use it only if your drive doesn’t support anything better. Use hdparm’s --sanitize-block-erase command–line option. These options exist for all ATA, SATA, SAS, SCSI, and NVMe drives (though I don’t believe that hdparm knows anything about NVMe, so you probably have to use the nvme command instead).
  - quijoteuniv 5y ago
    :)

Same as erasing any other type of disk. Why do you think its any different?

by db48x 5y ago

Same as erasing any other type of disk. Why do you think its any different?

Because you need to trust its firmware that the data is actually gone. Unless it's free firmware, I wouldn't trust that.

db48x 5y ago
Like I said, no different from any other disk.

quijoteuniv 5y ago

It seems that SSD info can be recovered. https://itigic.com/safely-erase-an-ssd-before-selling-or-throwing-it-away/ https://itigic.com/safely-erase-an-ssd-before-selling-or-thr... https://www.zdnet.com/article/how-to-securely-erase-hard-drives-hdds-and-solid-state-drives-ssds/ https://www.zdnet.com/article/how-to-securely-erase-hard-dri... This company claims is not possible unless you use their software, DBAN will not work. https://www.blancco.com/ https://www.blancco.com/ I am trying to recycle unused computers from companies, and install Linux in them and there is a bit of vacuum in terms of how to erase/comply... som services use Blancco, some companies remove the hardrives before disposing of the computers, making recycling more expensive, need to buy a new hardrive and fix them.

db48x 5y ago
The classic Linux shred command will work just fine, same as on any type of disk. But what you should actually do use use the drive’s built–in instance secure erase feature. This changes the encryption key to a new one, so all existing data is rendered permanently unavailable. Not all drives have disk encryption, but when they do it works the same way whether it’s an SSD or spinning rust. Use hdparm’s --sanitize-crypto-scramble command–line option to do this. Some drives only have an older feature that does a secure erase that overwrites every block in the device. This is much slower, so use it only if your drive doesn’t support anything better. Use hdparm’s --sanitize-block-erase command–line option. These options exist for all ATA, SATA, SAS, SCSI, and NVMe drives (though I don’t believe that hdparm knows anything about NVMe, so you probably have to use the nvme command instead).
- quijoteuniv 5y ago
  :)