Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery

Question

Friends, SSD of the company Silicon Power , model S55 240GB . It stopped booting overnight and is visible in the BIOS as SATAFIRM S11. When inserted into another computer as a second, in Disk Management it is uninitialized, but the capacity is surprisingly correct. It can not be initiated. In...

kaleron · Accepted Answer

The problem is not so much the controller as the low quality of the memory, usually 3D NAND TLC 15 nm, I could still give the company name. To ensure correct operation of the controller, the controller needs not only the basic microcode stored in ROM, but also dynamically changing information about assigning LBA addresses to specific blocks, damaged blocks ... etc. This information is stored in NANDs and if there are errors there - the media breaks down, usually described as controller damage. In fact, the controller itself, as a system, is electronically functional all the time, but due to errors in information relevant to locating specific data, it loses the ability to manage the media and exchange data with the computer. Therefore, instead of the model defined by the manufacturer, the stickers on the housing are presented with text prepared by the author of the firmware. In the case of Phison, controllers are sold together with the firmware and documentation including the topology of the PCB - that's why the disks removed from the housings of various manufacturers are practically indistinguishable, and the serial numbers returned by the carrier often differ from those printed on the sticker. In the case of low (calculated in MB) capacities - they are often the capacities of some buffers, and access to NANDs is cut off. Data recovery is possible but not easy. PS3111 uses dynamic data randomization, which makes it necessary to get along with its firmware without disturbing the damaged, but still useful tables of translation of physical addresses into logical. Probably obvious that the variety of firmware versions only complicates this process. The last Phison controller we used to desolder for mathematical systems and methods was the PS-3110. As progress in SSD, unfortunately, the failure rate increases and data recovery is getting more and more difficult.

pidar · Answer

Check the detection of efficient and damaged in PhisonToolBoxCompletev1.05.exe .

xntxnt · Answer

Ooo, Russian sites are amazing . By: ... program version 1.05 (Complete) does not yet support the S11 controller, which is probably a disk, so I started from 1.15, running with two S55 disks connected (good and damaged): He detected both, although at first the clicking between the disks did not change (SMART readings as well), and after running the program, SSD2 disappears (although, for example, in Disk Management - he was still there). Computer restart and returned to normal. Good and damaged: An attempt to upgrade from the program, regardless of the disk, shows: I also launched 1.05 (Complete). Both disks are connected. The result is this: I guess something does not play, because there is nothing active to click on, not counting X to close. The Standard version shows more (but also only a working drive): I thought Win10 might spoil something, but under Win7 the same, also when there is only one disk. In the meantime, the manufacturer sent me a new firmware (I attach the file UpgradeFW_SBFM21.2 (DLMC) _v1.00_180413.exe - all in all I do not know exactly what it suits): However, this error crashes: Also for the time being lime.

pidar · Answer

But did this damaged SSD also be detected

xntxnt · Answer

The program you have given is not detecting either a damaged or a working disk (whether Win10x64 or Win7x86):

A newer version (103), downloaded for free from the manufacturer's website ( http://www.silicon-power.com/web/pl/firmware ) responds to a working drive with the following message: "this firmware is the latest version."

... and damaged: "No new firmware is available or drive is not recognized."

That is the same as if I launched the program without any disk of this company.

pidar · Answer

Unfortunately, knowledge costs (files added by me). At your own risk (at your peril ) start now:

xntxnt · Answer

That was not allusion Well, unfortunately, I've lost my grandfather . And it was like this: I admit that without knowing what to do, I let go again (without rebooting). Maybe it was a mistake: And after a reboot, the disk was already like this (the system detected the disk as SATA BURN): And another attempt gave such an effect: And now the best part of the program . After I finished the drive, I got an e-mail to support Silicon Power with the following content: And that's one of the grandfathers! As you can guess, it was a bit too late and the bottle delivered by them came out on me: I wonder if the program has a -force switch to force flush? Or is there a rescue way to get out of this version in which I am. Probably yes, but does anyone know? Well, nothing. I still have a lot of this stuff, so it's just a matter of time until another one falls. Maybe this program will be useful for him. I am enclosing him for free ... I am so extravagant ... I have the 6.97 point in the end . Electrode spot beggars, unite! And seriously, I am for free and unheeded knowledge. I have enough profits from those who do not want to use what is at their fingertips out of laziness.

pidar · Answer

And so it was already in poor condition.

xntxnt · Answer

Well, I do not know if these values were true. Number of cycles in millions, not to mention over 31 years worked, when komp was a typical office building for less than a year. In addition, with an efficient anti-virus and limited user rights (it can be assumed that he did not finish it with scrambling cycles).
I warn you the question: there is a guarantee. But for me it's a bit of a sunset with shipments, considering that there are 200 computers, and data loss.

So out of curiosity: did you happen that after the disk drive on Phison, you managed to not only improve the disk, but also the content? I mean just fw, and not just bone discharges and off-disk readings.

Interesting fact: HD Tune was able to scan the surface without problems (the disk had 20MB). I regret that I did not suspect DMDE what was in these sectors.

xntxnt · Answer

Another second, identical disc fell on me. That's what I tried to treat with what the producer finally sent me (as a reminder: they did not immediately send the right FW). Unfortunately, it crashes:

... or not so FW. I have no ideas what to do with these crap.

been added:
The above image was from a program that will not fix THIS specific disk - not the firmware, hence the error.
The second one had firmware: SBFM71W0, so it's no wonder that what they sent to the previous disk, did not want to fire. The program did not find anything to update. To make it more fun, this second drive is practically a new drive without a waveform. As I was able to advertise it, it went to the complaint.

djbpm · Answer

In the post # 7 it looks like you uploaded the SBFM firmware 51.2 on SBFM firmware 71W1 what you caused him to perish. Probably, UpgradeFW_SBFM should be uploaded to it 71.2 (DLMC) _v1.00_180413.exe
The second disk that you lost, what are the firmware versions now?

I came across this topic because I have a similar problem, only that I have the SBFM50W8 firmware

Device Model:     SATAFIRM   S11
Serial Number:    8E31076B0508061*****
LU WWN Device Id: 5 000000 000000000
Firmware Version: SBFM50W8

The program from the link https://www.silicon-power.com//web/pl/firmware in my case detects everything and recommends uploading SBFM51.2 with the fact that the title of the window has the word "force_erase" which would suggest that the update erases the data. Is this really the case, and the data is already unrecoverable?

xntxnt · Answer

It probably is as you say, but it was too late. It's a bit weird that the manufacturer's program did not download this firmware. Now I can not do it to download the proper firmware - I do not know of any -force switch. Unless it is too late. I completed the previous entry. As the moderator approves, it will appear. And now one more curiosity. The third S55 240GB drive . Firmware, just like you: SBFM50W8. This time the user reported a reluctant system start and restarts. I regret that I did not take pictures with my phone, but sometimes it was a funny effect on the Win10 login screen - instead of letters, there were rectangles. I entered the Device Manager and there ... SATAFIRM S11. And the system as-tako competed: As you can see, only one disk, which is the system I am running from. As there was no pressure on the data, I downloaded what I could to a USB drive under the system. Just like you, the program has found a file that updates it to SBFM51.2 without any problems - it went well: I attach a program. You've got one, but maybe someone will need it: UpgradeFW_..._v1.00.exe Download (4.14 MB) Here is the answer to your question: Yes, the data is deleted. But I do not know if it would be possible to recover anything, it did not occur to me to run after the update of DMDE or TestDisk, and the computer returned to the user. He has to observe and make copies. We'll see if he'll come back. Djbpm , can you tell if your disk is still alive (the system is booting), has it completely died (no possibility to set up partitions, etc.)? I am curious if it is not a coincidence that the manufacturer's program finds a new firmware only when the disk still works. I also have an interesting observation. I have looked at a few efficient computers with these disks and, for example, such FW versions I noticed: V3.3 P1222A SBFM71.1 ... that is completely from the cap. Each of the other parish. Rather, there is no universal way to revive any art of the S55 drive. Yessame serial numbers - they are not made according to any meaningful key, in addition the numbers from the decals on disks do not match the numbers seen by the diagnostic programs. In my life I would not buy a Silicon Power disc for myself. The worst Intel or Samsung, but not that.

atlantis2 · Answer

Hello, I apologize in advance for unearthing the topic, but by accident I came across a program that is supposedly able to resurrect the disk with the above mentioned problem - a description in English: I do not know how much it is worth it, because I have no way to test it.

darek_s · Answer

Does anyone have an SBFM71W1 firmware for S55, because FW_SBFM71.2 (DLMC) _v1.00_180413.exe does not accept - crashes This Tool only support Device Firmware Version: SBFM71.0, SBFM71.1 !!!

Arqus75 · Answer

I tested the soft of the last but one post, it does not work. My disk is in read-only mode and no changes are saved. Of course, the message all OK oO rehearsal still satafirm s11

xntxnt · Answer

I will not answer the above question, but I will write generally as the author of the topic.
I left the topic of rescuing these disks. Too very uncertain.

For 200 pieces of computers, in 7 there were discs. Of which the majority for "good morning", after a very short and delicate operation as a typewriter. In addition, one disk was saved - the manufacturer's software wanted to update it firmware when it was already detected as "SATAFIRM S11", but it could still be read from it. Preventive firmware upgrade on floppy disks is a weak idea, because the software almost always claims that it has not found a new version.

Disks get spoiled mainly in one of two ways:
- detection as "SATAFIRM S11" and negligible capacity
- the correct name, but the drive only works for a dozen or so seconds and hangs (when read by the USB adapter, because the SATA disk will hang before the system starts from the second disk)

The problem with the possible rescue of disks is that they occur in many different versions of the firmware, with the numbering of the version being completely different (as if the other guts). With curiosities, they are found both in a metal housing and in plastic. Or the fact that the serial number from the sticker is completely different than the serial number detected by any diagnostic software (even in the case of a working drive!).

In general: equipment not worth the attention and no money.

If you buy, for example, a post-leasing Dell from one of the big companies (for example, what starts with "A" and ends with "About"

) and you feel tempted by the low price for SSD equipment, it's better to let go - buy at a disk auction and buy even and used Intel for MLC (series 520, 525, 530, 535, 1500 and 2500).

Przemek_79 · Answer

Is this AMSO company ???

djbpm · Answer

Yes, it's AMSO, they push these SSDs everywhere, and it's not so cheap. (At least they pressed). I gave up the data from this disk, AMSO replaced it with a warranty. When I wanted to buy a laptop with another SSD, they gave me the information that they actually do not know what SSD will be mounted, because they assemble different according to availability. I wrote in the comments in the order that I categorically do not want a SP disk, and so the laptop came with the SP disk. In the complaint they said they would exchange for another, but I have to send a laptop to them. I was in a hurry and I gave up. However, I will not buy an SSD again if they do not specify exactly what it will be. I will buy myself and exchange. Generally, the cheapest SSD is for them the performance decreases as a function of filling, they are like HDD when 90% full, and it's hard for me to talk about the failure, because I do not get enough of these disks in my hands.

xntxnt · Answer

I do not know, I will not say, but it fits what I wrote earlier: A few days ago, the eighth disc came out. Detected as SATAFIRM S11, but the capacity was good. However, it was not possible to initiate it and no soft diagnostic did not want to scan it. In general, I recommend taking such compilations with a disk or without a disk. After all, if they put in the cheapest GoodRAM, it will not be much better.

Karollus · Answer

Welcome,
I didn't want to start a new thread so I decided to hook up here. Well, I got a Silicon Power S55 120GB disk and it is detected as SATAFIRM S11. I can't create any partitions on it and I get the impression that it turns itself off (or maybe this is a wrong impression). His FW is SBFM21W1. Now the question: which FW do you recommend to start with?

lisek · Answer

As the company wrote recovering data from disks

Quote:
If an SSD is recognized as SATAFIRM S11 (Phison S11 Controller (PS3111-S11)), it means that the firmware information of the SSD has been rewritten.
It's probably that the SSD is dead.
And all your data in the SSD are hard to get back.

Specification of this Phison ctrl in appendix
* he also visited KINGSTON 120 -480 GB series sa400xxxx

You have a 2% chance that you will regain ..... link
and from a known forum
link
:!:

WARNING: This procedure is data destructive!

Like the failure with this ctrl in more than 75-85% of cases

Does not help: Phison toolbox, Victoria / HDD Low Level Format Tool

Apparently (apparently?) Helps (not always) Secure Erase on Linux

People "from behind the Great Wall" have medicine (PS3111SB Firmware Upgrade Tool) link
* min. behind link

Karollus · Answer

I would add that I do not care about data, but only hobbyist will be able to bring it to working order. Just enough. If it's really not worth wasting time at all, I'll give up

Łukasz_W · Answer

Damage is associated with the degradation of memory cells and from my experience I will say that it is not worth wasting time putting models based on these controllers on their feet.

lisek · Answer

It's a waste of time ... that is, as it is written above. Before buying an exotic SSD check .. what controller is built in there!

xntxnt · Answer

Meanwhile, I reported to the seller today damage 15 (fifteenth) of 200 Silicon Power S55 240GB disks. 7.5% of the dead.

I also confirm: better give it to children to play or something

.

The total pad number (i.e., a 20MB capacity is released and released as SATAFIRM S11) may be repairable with a new firmware, but the problem is choosing the right one, in a situation where Silicon Power can release one series of disks with quite different firmware.
With the rest, for me, such cases have basically ended - apparently it fell what was supposed to happen in the first months. Now dominated are "bad sectors" or basically memory cells. Most often at the beginning of the disk, so usually user data can be ripped because they get Windows files. But this is also not the rule - sometimes the disk is visible only a few seconds (when connecting via a SATA-USB bridge), and then hangs. Connecting via SATA is not possible then, because the system from another disk never wants to boot if it feels that it has Silicon Power down next to it on Phison S11.

Also Karollus I would give up. Even if you fix it and it is cool and fast, it will fall in the least expected moment and you will lose data. See Intel SSD prices on Allegro - I've already bought several stimulants from the 2500 or 535 series (and 1500 and 530) - sometimes for more than the new Silicon Powery. Passed, several years old, and do not want to spoil. There is something about it.

xntxnt · Answer

If not a secret, how many working days did such action take?

kaleron · Answer

It is difficult for me to answer exactly - the development of the first extended to almost three months, of course, in the meantime, we did other things as well. Then, when we knew what to expect, it was a matter of up a few days, at the end a solution appeared in the PC-3000, but when you could start using the cash, the PS-3110 almost stopped coming.

fcasjc · Answer

Hi, i had the same error trying to upgrade fw of a broken kingston ssd from a client of mine. S11 repair utility was sucessful but the data was still protected so ive tried a fw upgrade and it failed. Now the ssd isnt detected by the system. Is there a way to fix it?

Łukasz_W · Answer

When updating the firmware, the data on the disk is deleted, so what access are you talking about?

Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Post #30

Topic summary