585
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Aug 2025
585 points (100.0% liked)
Technology
74217 readers
3782 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
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?
Uh v lå p.