As this is an SSD, you **don't ** want to do something like "dd if=/dev/zeo of=/dev/sda", and just leave it like that. This is due to the nature of an SSD having knowledge of which blocks are allocated. In essence it will think that the whole drive is allocated with useful information, when in fact it's all just zero's intended to wipe the drive. What this causes is a performance degradation when performing partial block writes because the SSD will first need to perform a read and then a write. when it should just be performing a write.
What you want to do is basically unallocate all of the blocks at the SSD firmware level by essentially performing a TRIM command across the whole disk.
if=/dev/zero of=/dev/sdX bs=1024k count=256; sync;blkdiscard /dev/sdX this command will basically wipe out the partition table, force the kernel to execute(if it didn't already), and then force unallocate everything within the SSD's firmware.
(This doesn't securely wipe the device, but it will make it seem as if it's a new unwritten drive to the operating system)
And can this command be entered in Windows? Because I no longer have any Linux installations?
Always good to keep a Linux live CD on a USB stick. Ventoy is a nice multi-boot installer that lets you just copy iso files over to the USB and then boot from them (windows installer iso can also be booted from).
A will reset everything, including the flash translation layer (FTL). It adds one wear level count but you're sure to not carry any performance baggage from previous use.
Trimming the entire drive with blkdiscard should in theory be just as good but if I'm starting fresh I do the extra step.
Sounds like the result I want. Thank you!
can anyone really do anything on windows? I've been using windows for work since the past 4-5 months and it's complete hot garbage. Just recently I've been trying to get it to report proper memory usage and it simply won't. I'm running a program that says it's using 12gb then when I look in the task manager it says it's using 1.6gb. When I look at the total memory usage it says it 24 gb but when I add up all the processes it's 3gb. It blocks off the memory usage into 4 groups: processes, "system librarys etc", "mem that needs written to disc before it can be used (even if you have swap turned off", and free. So block 2 that uses like 30% of 32gb you're just not allowed to know what the fuck is going there. Block 3 just I guess is dead memory if you have swap turned off. The third is like 8gb on a 32gb machine with supposedly 3gb of processes running.
On a 32gb machine if I turn off swap and memory compression, while only the browser is running there is only like a 50% chance the whole machine won't crash before I turn it on in the morning. What in the living f?
No, these are Linux commands. You could boot from a Linux live cd or thumb drive though. You also need to locate the disk drive logical location. The whole “/dev/sdX” part would be replaced with the address for the drive you want to erase. (I would physically disconnect any other drives before doing this to make sure you don’t erase the wrong drive)
Have to do something like “fdisk —list “first to get the addresses for your drives.
Ok I’ll study up and see what happens.
(post is archived)