logo elektroda
logo elektroda
X
logo elektroda

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

xntxnt 69894 44
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #31 18423407
    kaleron

    HDD and data recovery specialist
    Firmware damage is most often caused by the wear of NANDs. A significant part of the firmware, including data-critical translation tables are found in NANDs. Uploading new software causes, among others the destruction of translation tables, and therefore the determination that the data was protected is quite inadequate. Yes, after such a repair, the medium may still work a little, but this type of repair is at high risk of repetition of the fault. That is why I am very skeptical about them. And of course you have to remember that they are destructive to data.
  • ADVERTISEMENT
  • #33 18430346
    Shark.93
    Level 7  
    lisek wrote:
    :!: 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)


    Hello, I have a Kingston A400 240GB [SA400S37/240G, native firmware on label: SBFK71B1] with the infamous SATAFIRM S11 problem, happened last week after 1,5 years of usage. I have backups of my data, so what I am looking for is to restore the health of the drive in order to keep using it; I don't care if the data is wiped in the process: I am prepared to reinstall the OS.

    I have tried running repairS11 utility by vlo (vlo.name): when using a SATA-to-USB adapter phison_flash_id detects PS3108 Controller so the repair utility refuses to run; when using built-in SATA port on my Laptop (AHCI mode set in BIOS) the detected Controller is PS3111, the repair utility ends correctly with a success message, but the problem remains. What else can I do?

    By any chance has anyone tried using PhisonToolBox v1.17 by usbdev.ru ? By all means I just want to exit from 'Safe Mode' state, restore 'Ready' state of the drive and just reinstall my operating system over it, I do not care about the data because I have backups.

    Another user claimed he restored the same drive model using SBFKB1C3.zip (media.kingston.com) and s11-flasher 2.0 (vlo.name). Does this actually give a new life to the SSD (even if it erases the data) and will it void the remaining warranty of the unit?

    Finally has anyone with this problem actually tried to perform a secure erase of the drive, perhaps from Linux like lisek writes in his post? Thank you very much.
  • #34 18430347
    fcasjc
    Level 2  
    lisek wrote:
    With understanding link then jump to Link_ SSDtool

    Sorry, i think my first message was too upfront and i did not explained it well. I did exactly what these links were instructing.
    The SSD was named satafirm s11 and i couldnt not format the disk in any way. The vlo S11 repair tool was telling that the protection was removed sucessfully but was not destructing the data.
    After many tries, ive decided to try the firmware upgrade. Ive used the s11 id tool, downloaded the fw and flashed it with the s11 flash tool. Since i couldnt find the SBFK71B1 fw, ive decided to try using the SBFKB1C3 fw.
    The upgrade failed at the last part and the disk is not detected by the windows anymore. It had and error similar to the one ive quoted on my last message.
    I want to know if its possible to try something else or the disk is gone. I just wanted to try to make the disk work again because 480gb ssd is kinda pricy here and it can be very useful.
    If its not possible at all, np. It was like a last resort since stuff werent working and kingston guarantee wont accept my rma because they dont accept stuff brought from other countries.
    Thanks in advance
  • ADVERTISEMENT
  • #35 18632119
    DrOzda
    Level 12  
    It may be useful to someone. During the firmware upgrade of the SiliconPower V70 120 GB disk on a Phison 3108 controller something went wrong and the disk did not want to initialize in the system. Although it was correctly detected by the BIOS and Windows. Because he was already quite old I put it in the drawer. Now, as part of killing time, I decided to resuscitate him. Because it was updated when upgrading to the latest S8FM08.3 firmware, the Windows Sata toolbox did not have a newer one and refused to overwrite it.
    Fortunately, it turned out that there is a DOS version with S8FM08.2 firmware and forcing with the -F option flashed the disk and works like new.
    The data disappeared but the disk was still plowed:
    https://www.usbdev.ru/files/phison/ps3108dosfwupgtool/
  • #36 18632328
    xntxnt
    Level 14  
    But this is rather a different case than the ones from the topic. In the sense that before flashing you didn't have "bad sectors" or other problems.
    But anyway, remember! You've got a crap company disk - make copies.
  • #37 18632406
    DrOzda
    Level 12  
    No exaggeration, this one is quite decent inside, MLC 19nm Toshiba bones, worked without a problem for 5 years, I just wanted to improve already good :)
  • ADVERTISEMENT
  • #38 19112303
    hatkey
    Level 16  
    I apologize in advance for uncovering the topic, but by accident I came across a program that is said to be able to resurrect the disk with the above-mentioned problem - description in English:

    Quote:
    This utility designed for repair Phison S11 based SSD from Protect Mode.
    The drive in this state detected as "SATAFIRM S11" or "INIC6081SSDWP".
    System requirements: windows xp sp2 or above, x86 or x64.
    Preferable using AHCI mode of disk controller, but possible work in SATA (IDE) mode and also usb via some bridge from asmedia or jmicron.
    Utility request disk number, which can be viewed in "Computer Managment" / "Disk Managment".
    After successfully complete you should do a power cycle for SSD.
    Run example:

    repairS11 2



    Only with this S11 file I was able to repair the SILICON POWER S55 drive. I had the disk connected via a USB -> SATA adapter. The drive was visible in the device manager as SATAFIRM 11.

    I fired up the file and chose the disk and after reconnecting the disk it was visible with all the data. I just had to assign letters to the partition.
    I don't know how much it is worth, because I have no way to test it.
  • #39 19112460
    Łukasz_W

    HDD and data recovery specialist
    hatkey wrote:
    atlantis2 wrote:

    I fired up the file and chose the disk and after reconnecting the disk it was visible with all the data. I just had to assign letters to the partition.
    I don't know how much it is worth, because I have no way to test it.

    I don't even know who to quote exactly.
    It was data or there is no way to test?
    Firmware update / padding initializes memory and erases data. Rolled on any topic related to PS3111.
  • #40 19113169
    xntxnt
    Level 14  
    Hatkey was to attach a file. Although ... there are so many variations of this disk model, and it breaks down in several different ways, it is not certain that one program will suit everyone.
    Just in case, in this collection, I found the tool you are talking about:
    http://vlo.name:3000/ssdtool/
  • ADVERTISEMENT
  • #41 19113191
    lisek
    Service technician RTV
    The Silicon Power S55 240GB SSD is on the SM2258XT controller

    Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery
    This forum has been written about him Link
    plus about Kingston (FIX Satafirm s11 on Kingston a400)
    Link
  • #42 19113198
    kaleron

    HDD and data recovery specialist
    xntxnt wrote:
    there are so many varieties of this disk model
    - firmware version and memory configuration, because on the sticker you can write anything, and even the most important, what is inside.
    xntxnt wrote:
    they break down in several different ways,
    - very similar.

    Repairs for the device do not give very permanent results, and Łukasz has already spoken about using software to repair firmware to recover data. Then there are situations such as "I have already repaired the drive with my brother-in-law, now just recover my data, it probably won't be expensive, because I have already done the most important part of the job for you ..."
  • #43 19113711
    xntxnt
    Level 14  
    The ones I have - the stickers are identical except for the s / n :) . But the firmware is numbered completely differently. There are at least 3 types of housing (one plastic and two metal). Understands also different. The photo he posted Fox is the content of one of these metal varieties.

    Without breaking down into versions, they break down in about 3 ways:
    - SATAFIRM S11 in BIOS and no data access
    - "bad sectors" -> unstable work
    - disappearing from the system after some time - even via the SATA-USB bridge
    In addition, some have a reduced SMART. Some are even cheated - for example, they show that they have a constant temperature of 30 * C.

    The second metal version looks like this:
    Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery

    The one in plastic is different:
    Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery

    Perhaps there are others, but apparently I only have them, or they just don't break.

    And what? Various controllers. Someone will surely fire some soft and surprise :) .

    There is really no point in saving these disks. It's junk. Pity the nerves. If something needs to be recovered - ok, they are from this company. But keep on using after a crash ??? Throw them away and you will do a good deed for yourself. Seriously.
    In less than 4 years, 50 out of 200 were lost. I suspect that many more, if not all, are damaged. Some equipment is simply rarely used.
    Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery
  • #44 19113796
    lisek
    Service technician RTV
    Of those who fell, most of them had controllers?
    - because in my kingston on SM2258 already 3rd year .. no problemos ... senior

    - used from Phison PS3111-S11
    - as above PS3110 * in 2015 (plus 128MB DDR3 cache from Nanya)
    Silicon Power S55 240GB SSD Issue - Visible as SATAFIRM S11, BIOS Detection, & Data Recovery
    * on early models of Phison PS3108-S8- Link

    The new PCIe4x3.0 uses the silicon Phison PS5012-E12
    * Link
  • #45 19114194
    xntxnt
    Level 14  
    I do not have all the disks that have fallen, but of the 32 that are waiting to be destroyed - 27 is the version in a metal housing with Silicon Motion SM2258XT. So what's yours.

    Does that mean the SM2258XT sucks? I do not know. Probably a lot depends on the memory and firmware used.

    Anyway, I don't think you should look for bargains at the lowest price, because then you don't know the day or the hour. I already know that I will only bet on companies with a 5-year warranty, even if it is apparently more expensive. Seemingly, because data recovery and system rebooting costs money and time.
    Although, unfortunately, Silicon Power also has a 5-year series.

Topic summary

The discussion revolves around issues with the Silicon Power S55 240GB SSD, which is recognized in BIOS as SATAFIRM S11 and fails to boot or initialize properly. Users report difficulties in data recovery, with various software tools like SP ToolBox and PhisonToolBox being ineffective. Firmware loss is suspected, and attempts to recover the SSD using different firmware versions often lead to further complications, including the drive becoming undetectable. Some users have shared experiences with similar SSDs, indicating a high failure rate and suggesting that the underlying problem may be related to low-quality memory cells and controller issues. Recommendations include avoiding firmware updates that could lead to data loss and considering alternative recovery methods, although success rates are low.
Summary generated by the language model.
ADVERTISEMENT