dd if=/dev/null of=/dev/sdX
will this erase everything on an ssd? I know stuff like shred doesn't really work on ssds. Is the above valid?

or /dev/urandom
will this work?

>>106119917 (OP)
As far as I know, this will work. However, it leaves traces, meaning it can be deduced that something was written to it. No way to recover but it's not going to look "clean" in forensics.

>>106119925
urandom/random will be better than null for an ssd, yes
when decommissioning drives i usually do that and a sata secure erase/an "enhanced" secure erase if the drive supports it

>>106119963
what if I do it a few times? Would that make things much more difficult to recover?

>>106119991
Yes, govt agencies and other highly sensitive fields normally fill it with random bytes multiple times before discarding a drive

>>106120417
>Yes, govt agencies and other highly sensitive fields normally fill it with random bytes multiple times before discarding a drive
they just shred their drives (I mean physically not the shred command)

>>106120472
Usually done by 3rd parties, unless you're AWS scale. Several overwrites are done before hand off to the 3rd party.

>>106120506
Well there you go. That's table stakes if you want secure deletion.

>>106119917 (OP)
Use the secure erase feature instead.

>>106120590
>use the government snapshot feature instead

Using your SSD will erase everything.

>>106120851
luh
a
mao

>>106119917 (OP)
don't get rid of your 'p you'll regret it

>>106119917 (OP)
>stuff like shred doesn't really work on ssds.
Yes it does. /dev/sdx is a file. It can be written to by shred.
Yes to your first question as well

>>106119917 (OP)
There's no guarantee that even multiple passes of a full drive write will actually overwrite every block on modern drives. Use secure erase or a hammer.

>>106119917 (OP)
>dd if=/dev/null of=/dev/sdX
No, you stable genius, you cannot read from "/dev/null". What you want there is "/dev/zero".
That said, zeroing the drive only works as expected on HDDs. SSDs are special and need custom "secure erase" tools: https://www.tomshardware.com/how-to/secure-erase-ssd-or-hard-drive

>>106119917 (OP)
No, SSDs use overprovisioning so it's not guaranteed to clear everything. It'll also rape the endurance. You should use you're drive's secure erase feature.

>>106119917 (OP)
Just melt it in a volcano bro.

>>106120950
I don't have any cp you disgusting faggot.
I was just learning about SSD's and how they allocate blocks, so was wondering how proper wiping can be done on them.

>>106120971
it works if used on the whole drive, correct? Not on a specific file or block on the drive. Since SSD's do magic behind the scenes and realloxate already existing blocks in place of old ones when they get delete commands from an OS.

>>106121160
I got a gnu/hammer ready, but what's secure erase?

>>106121448
>what's secure erase?
https://wiki.archlinux.org/title/Solid_state_drive/Memory_cell_clearing

>>106119917 (OP)
I'm sorry not to answer the question, but why didn't you just encrypt it to begin with?

>>106121639
I know about encryption now. Not gonna lie I still don't use it 'cause I don't keep any sensitive info on my main machine. I have a separate laptop for banking and important stuff.

I was watching a podcast about tech and they mentioned something about how SSDs allocate blocks and it got me interested so started reading more about them, and that finally lead me to thinking about how someone can safely delete an SSD.

Anons already mentioned some good information above though.

>>106120942
What's so funny, retard? Wear leveling will overwrite all old data if you write like 120% of your disk's capacity by just fucking using it.
If you aren't going to use it anymore, then physically destroy it, and use encryption next time if you're a pedophile who has a lot to hide.

>>106119917 (OP)
$ sudo wipefs -a /dev/sdX1 # and for every other partition
$ sudo wipefs -a /dev/sdX
$ sudo blkdiscard /dev/sdX
$ sudo dd if=/dev/urandom of=/dev/sda bs=4M # three times
$ sudo blkdiscard /dev/sdX
# Feel free to do a SECURE ERASE or whatever
[/code

>>106119917 (OP)
$ sudo wipefs -a /dev/sdX1 # and for every other partition
$ sudo wipefs -a /dev/sdX
$ sudo blkdiscard /dev/sdX
$ sudo dd if=/dev/urandom of=/dev/sdX bs=4M # three times
$ sudo blkdiscard /dev/sdX
# Feel free to do a SECURE ERASE or whatever