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?
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.
Uh v lå p.