this post was submitted on 18 Aug 2025
648 points (98.2% liked)
Technology
74247 readers
4272 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yesterday I got into the process of installing Windows 10 onto my laptop because I am selling it tomorrow. I asked the buyer if he wanted it with an OS or not, and he replied that he wanted Windows 10 Pro. I downloaded the ISO and installed it to one of my M.2 SATA SSD drives with a USB adapter.
Before installing Windows over my Linux installation, I did a SecureErase to wipe out my drive with the Linux installation because that is the SSD I am selling with the computer.
After installing Windows 10 from the M.2 SATA SSD with a USB adapter to the SecureErased drive, I instantly got multiple error messages about SMART checks saying that the SSD was broken/corrupted. I had never seen this POST error message when booting that computer with a Linux installation.
Well, I obviously had to change the drive to another one where I got the Windows installation to work normally without the BIOS POST error message.
I really cannot be sure what caused that. Can SecureErase do that so SMART checks report the drive as corrupted? Or was it the Windows installation?
SecureErase would overwrite the whole drive (potentially multiple times). So if the ssd was close to dead, it might have just triggered it.
I see. Well the SSD was used and few years old. Some Samsung SSD from a OEM build. I did run SMART tests on it like year ago and it was ok/healthy.
Time to fill it with linux isos and seed them with torrentz until it breaks completely.
Hm...Weird way to shift blame.
where is the user error? is this user error with us in the room?
Fully overwriting an SSD is so archaic.
Example from hdparm:
I think the all caps warnings say it all.
This is only for the trim sectors of the disk but I can't imagine it being much different overwriting a whole disk.
Not to mention, as OP said, an old and very used disk.
Quick formatting should be enough to prevent any normal user from extracting meaningful data from the flash storage as only the controller knows how to piece together the flash cells to a file.
If the controller forgets it, the files are toast anyway.
At best write some random data to a quarter of the disk or something lile that.
File recovery may only be possible if you give it to a drive recovery facility. But remember: Those ain't exactly cheap.
A client paid some 4 figure price because an HDD died. Just for a small amount of files.
@zer0bitz@lemmy.world did a SecureErase, which is an entirely different function. It was exactly made to be used in this scenario: user is selling their laptop.
other than that,
hdparm --trim-sector-rangeis most probably only marked dangerous because with a slight miscalculation you can wipe some of your data and you won't even know how much damage you did. I'm pretty sure thefstrimcommand relies on this, which is executed every few weeks on my system, by default. check systemctl status fstrim.timer, maybe on yours too.what do you mean by quick formatting? how do you do that on linux? I have only heard this term with te windows disk management tool.
on windows quick formatting only deletes the partition entry from the partition table. that's why it's quick. all the former data is there and can be easily recovered, given you know the former partition boundaries, which can also be recovered by tools. the ssd controller won't know a thing, it won't forget where it should look for each LBA address.
Uh v lå p.