secure deleting certain files on ssd (for hybrids)

>>61543615
>filling the ssd with data
That doesn't work due to wear leveling.
I believe you're looking for something called fstrim.

Well in your case, it seems pretty hard, because you dont seem to have direct access on the SSD part of your hard drive. Nethertheless, i would recomend to "nuke" your drive with DBAN, more than one pass wont be needed.

For the SSD Part, I would try to use GParted or partition magic. With it, you can in general use the ATA Secure Erase command to eradicate all data on a SSD

>>61543869
fugg i just want to secure delete a bitcoin address but I guess i have to nuke it all. Thanks.

File: 88b656574dbcdcb47df.png (10KB, 325x325px) Image search: [Google]

10KB, 325x325px

>>61543615

I have always wondered where is this photo taken. Does anyone know?

>>61543615
Should have encrypted the SSD first with a strong password before using it. That is the only way anything is secure. Good luck trying to nuke the data to oblivion.

>>61544358

Holy shit I found it.

It's the school from anime named The Melancholy of Haruhi Suzumiya (涼宮ハルヒの憂鬱 Suzumiya Haruhi no Yūutsu).

The photo is taken from the road which goes next to the school.

The same way I permanently delete any data.
Bullets through the drive. Make sure you hit the controller and all the nand chips. A blowtorch works too but is less fun.

For fuck's sake you drama queens.
>fstrim [-a] [-o offset] [-l length] [-m minimum-size] [-v] mountpoint
>fstrim is used on a mounted filesystem to discard (or "trim") blocks which are not in use by the filesystem. This is useful for solid-state drives (SSDs) and thinly-provisioned storage.
>By default, fstrim will discard all unused blocks in the filesystem. Options may be used to modify this behavior based on range or size, as explained below.
>The mountpoint argument is the pathname of the directory where the filesystem is mounted.
>Running fstrim frequently, or even using mount -o discard, might negatively affect the lifetime of poor-quality SSD devices. For most desktop and server systems a sufficient trimming frequency is once a week. Note that not all devices support a queued trim, so each trim command incurs a performance penalty on whatever else might be trying to use the disk at the time.