Kingston SSD 480GB Security Locked (E50 - Sandforce)
Posted: April 3rd, 2015, 8:21
Hi everyone.
First of all, this customer is from our contract base, a large national company that send us services on a monthly basis.
We asked him for the laptop invoice which he sent and proove that it belong to his company.
I explain this to remove the suspicion of stolen drive and etcetera.
The case is one Kingston SSD from the E50 series.
SE50S37/480G - Sandforce chip.
According to the customer, the laptop was hard powered off after the battery get disconected (notebook dropped by accident)
Then on the next reboot, the SSD returned with a password that he never set.
ATA password secutiy locked, not anything software related.
It seems to me like a reasonable occurrence for SA bug problem
Does anyone have faced issues like this with Kingston E50 series?
Do anyone know of a tool or method for clearing the password while preserving the data?
- Excluding having to rebuild using FE or similars -
ACE SSD doesn´t support Sandforce as of now.
We tried updating the firmware which also didn´t solve the problem.
Thank you
-BR-
First of all, this customer is from our contract base, a large national company that send us services on a monthly basis.
We asked him for the laptop invoice which he sent and proove that it belong to his company.
I explain this to remove the suspicion of stolen drive and etcetera.
The case is one Kingston SSD from the E50 series.
SE50S37/480G - Sandforce chip.
According to the customer, the laptop was hard powered off after the battery get disconected (notebook dropped by accident)
Then on the next reboot, the SSD returned with a password that he never set.
ATA password secutiy locked, not anything software related.
It seems to me like a reasonable occurrence for SA bug problem
Does anyone have faced issues like this with Kingston E50 series?
Do anyone know of a tool or method for clearing the password while preserving the data?
- Excluding having to rebuild using FE or similars -
ACE SSD doesn´t support Sandforce as of now.
We tried updating the firmware which also didn´t solve the problem.
Thank you
-BR-