logo elektroda
logo elektroda
X
logo elektroda

SATAFIRM S11 or How to bring an SSD to life on a Phison PS3111

a_jablon 122895 172
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #121 21441706
    Marvell_88i8945
    Level 15  
    >>21441699 This is a poor solution. Not sustainable.
  • ADVERTISEMENT
  • #122 21442780
    a_jablon
    Level 35  
    Maybe not sustainable but working ;) .

    By the way: it's not a test as 'unsustainable' as a colleague thinks.

    Overall summing up this statistic: 4 repaired, 3 nadaL walking (treated once with this procedure), 1 repaired in an "unsustainable" way (had to be treated the same way a second time - I'm waiting for another failure). In one of these "working" the SMART blew up - reports nothing, but no problems with either performance or data loss. Efficiency: realistically 75% and for the 'clingy' 50%. I was expecting an "unsustainable" effect and I am surprised myself that it is really good....
  • #123 21442786
    MM2X
    Level 26  
    a_jablon wrote:
    Effectiveness: 75% in real terms and for the 'clingy' 50%. I was expecting a "non-permanent" effect and am surprised myself
    .
    You've done a super-ancient job on this subject :) , the roadmap is there as someone wants to practice. I'm in the position of having it under warranty and will be aiming for a repeat of "Satafirm-s11", data removed from it 100%. If the drive were to go for a spare, a second or third copy then you could risk it. However, to give it to the system is too much discomfort.
  • #124 21442787
    a_jablon
    Level 35  
    On the contrary: give it to the system and plough on as much as you can. After all, you want to mess it up, don't you?
  • #125 21443016
    MM2X
    Level 26  
    a_jablon wrote:
    On the contrary: give it to the system and plough on as much as you can. After all, you want to mess it up, don't you?
    .
    Actually yes, because then it grinds all the time, but I would have to make a copy every day ... because I do not know the day nor the hour ;)
    Colleagues have suggested another solution: ... 'Fill it with some junk content >90%, then heavily rotate some junk data on the rest of the LBA address' ....
    I filled it with two files with the CMD command " fsutil file createnew C:\test1.txt " with 100GB each and intend to rotate on the rest. Only now I have another problem-chronically lack of time, I don't use mobile technology ;) /almost not at all/ and I'm only left free when I'm at the cottage.
  • #126 21443066
    a_jablon
    Level 35  
    If hardware allows: install 2 drives. Repaired = system one, but put user profile on the other one. The system one dies (goes under warranty), you replace it, put the system up, user profile data still intact ;) .

    https://tomaszgasior.pl/oprogramowanie/profil-uzytkownika-na-oddzielnej-partycji-w-windows-10

    As for the ideas of killing the drive by murdering it with the amount of data: beware of the MAX TBW in the warranty terms....
  • ADVERTISEMENT
  • #127 21443091
    kaleron

    HDD and data recovery specialist
    This is why I was proposing maximum clogging with static data and intensive rotation on the remaining free area, where with a relatively small number of writes you can exploit quite a few blocks, as long as you do it in a time short enough so that wear levelling does not have time to grasp that something bad is happening....
  • #128 21443102
    MM2X
    Level 26  
    a_jablon wrote:
    System crashes (goes under warranty), you replace it, put the system up, user profile data still intact
    .
    I like this :) , for me it is a novelty. So on cito it will be good not only for now but so in general. I must familiarise myself with it, thanks for reading :) .
    a_jablon wrote:
    be aware of the MAX TBW in the warranty terms and conditions...
    .
    Allegedly like "satafirm s11 "they don't check anything, on the other hand if someone hasn't received detailed claim conditions but only an invoice and will fly under warranty then no restrictions work, or so ;) .

    Added after 4 [minutes]:

    kaleron wrote:
    That's why I was proposing maximum clogging with static data and intensive rotation on the remaining free area, where a relatively small number of writes can exploit quite a few blocks,

    Hey @kaleron, well you know you can be relied on like Zawisza :) . I didn't mention you personally so as not to infringe on your rights and there you have it .... you can't hide anything from a ger, hehehe
  • #129 21443117
    a_jablon
    Level 35  
    Spec is always going to tell you how to kill the drive so that you don't see signs of premeditated murder ;P
  • ADVERTISEMENT
  • #130 21443160
    MM2X
    Level 26  
    a_jablon wrote:
    Spec is always going to tell you how to kill the drive so that there are no signs of premeditated murder ;P

    It's always been the case that the most perfect crimes are committed by law enforcement officers (read: law-and-order specialists), hehehe
  • #131 21449373
    Kapzet
    Level 2  
    Hi, I have a Gigabyte GP-GSTFS31110TNTD
    CrystalDisk detects the drive but the fw flasher dosent, ive tried with mptools and something similar happens, detects it but doesnt give out the option to flash it. Any ideas? Im using SBFM61.5 as the new firmware, thanks in advance.
    Screenshot of S11 firmware flasher v2.0 and CrystalDiskInfo 9.5.0 programs.
  • #132 21449568
    a_jablon
    Level 35  
    You connect the drive over SATA, no fiddling with USB-SATA adapters - that's fine.

    Firmware version SBFM61.5. If it doesn't go, load an older one (there are several SBFM61.3 files in the package). SBFM61 must match. - The rest is less important.
    If .5 doesn't go, test .3 using the same method,ie:

    -you put the firmware in the folder with the flasher
    -rename it
    -fire s11-flasher2-micron with low privileges
    -fire fw with admin rights

    If this doesn't help, you take apart the drive enclosure and look for the jumper that forces the controller mode. Short the jumper, boot the drive, then try to download the firmware.

    Don't you have a SATA RAID controller or some exotic solution? Does it behave the same on another motherboard?
  • #133 21449587
    lisek
    Service technician RTV
    There in the first ex: was a Phison PS3111-S11 ctrl + Toshiba 96L BiCS
    - then YMTC 256Gb TLC memory, ( YMN08TE1W00C3B )
    - they gave 3 years Warranty (TBW 200TB) Link_ SBFM61.5 .
    SATAFIRM S11 or How to bring an SSD to life on a Phison PS3111 .

    Use phison_flash_id > you will see the disk configuration

    You will find the necessary FW in this topic or Link
    - then Phison S11 firmware flasher v2 ...
    Quote:
    We remove the jumper from the disk, launch S11 Firmware Flasher v.2.0 and after successful firmware, disconnect the disk from the power supply. We reconnect, initialize the disk in Windows Disk Management, check the S.M.A.R.T., and do read and write tests.

    We remove the jumper from the disk, run S11 Firmware Flasher v.2. 0, and after successful programming, disconnect the disk via the power supply. Reconnect, initialise the drive in Windows Disk Management, check S. M. A. R. T., perform read and write tests.
    .

    Then you can update the firmware of the drive to version 1.3 C using Gigabyte SSD Toolbox to a newer version
  • #134 21450905
    hashin
    Level 11  
    MM2X wrote:
    I am in the position that I have it under warranty and will be pursuing a repeat of "Satafirm-s11", data removed from it 100%.
    .
    Did you manage to repeat Satafirm S11?
    I'm in a similar situation, as I want to delete data which surprisingly is normally accessible, no need to combine anything with recovery. On the drive plugged into the other computer I can view the data but cannot delete it. It's as if the controller doesn't let it go. When deleting directories from the right click they disappear, but when I select the format option, they appear again. I want to return it for a claim but there is company data there that I don't want to share, so I'm looking for a solution on how to delete it. I have until Monday to do this.
  • #135 21451152
    kaleron

    HDD and data recovery specialist
    If you have impaired programming and deletion operations, you probably won't do anything about it.
  • #136 21451277
    hashin
    Level 11  
    Looks like just such a case, which is a shame. I'll probably try to do the method described in this thread on it to erase the data, if no SATAFIRM occurs by the time the claim expires, I'll leave it for testing. I won't be sending the data drive out of the company.
  • #137 21451341
    MM2X
    Level 26  
    hashin wrote:
    Have you been able to replicate the Satafirm S11?
    .
    So far no, but I'm thinking good thoughts ;) , what model of drive?
  • #138 21451402
    hashin
    Level 11  
    The drive model is: PNY CS900 240 GB
  • ADVERTISEMENT
  • #139 21451585
    Kapzet
    Level 2  
    >>21449568 as soon as i connect it with the pins jumped not even crystal disk detects it ;(
  • #140 21452120
    a_jablon
    Level 35  
    Strange, it should go into controller mode, show an undersized capacity and allow itself to be reprogrammed with Flasher. CrystalDiskInfo should be able to see it.
  • #141 21452537
    hashin
    Level 11  
    I tried methods 1 and 2 today, unfortunately without success.
    First method: after selecting the failed disk and starting the process, it throws an ATA error: "ReadInfoBlock failed! Error: 0x51"
    Second method: unfortunately I could not find the right FW for my drive and could not go further with the procedure.

    Disk: PNY CS900 SSD 240 GB
    FW: SBFNT1W3


    Screenshot of the Phison S11 SSD repair tool with an ATA error message. .
  • #142 21458732
    rtj71
    IT specialist
    How to resurrect it? Goodram CX100 120GB
    Screenshot of SSD-Z program showing details of a malfunctioning Goodram CX100 120GB SSD. .
  • #143 21463619
    a_jablon
    Level 35  
    TC58NC1000 is a rebranded Phison PS3110

    Interested in the S10 Flasher and soft from here:

    https://www.elektroda.pl/rtvforum/topic3859967-30.html#20398375

    or (original):

    https://www.usbdev.ru/files/phison/ps3110fw/

    Instructions for proceeding unchanged (except for the flasher number) - post #1 from this topic, second path of proceeding.

    NOTE: the SARM1.2 software is not included in the package, but will fit another one w/ instructions:

    https://www.usbdev.ru/f/index.php?topic=4498.0

    When selecting the software, it is a good idea to look inside the drive to follow the directions:

    Select the binary files for the flash memory installed on the SSD using the following mask:
    SAFM00.*/safm01.*/safm02.* - for drives with mlc flash memory from various manufacturers (micron/sandisk/toshiba)
    SAFM22.* - for "ufs" (toshiba) mlc flash drives.
    SAFM32.* - for 1 to 2 TB flash mlc drives
    SAFM11.* - for 19 nm toshiba tlc flash drives
    SAFM12.* - for toshiba tlc 15 nm flash drives
    SAFM13.* - for toshiba tlc BiCS3 (3d) flash drives
  • #144 21464585
    rtj71
    IT specialist
    Unfortunately: after renaming the file to fw.bin and clicking build-s10-flasher, nothing happens.


    Screenshot showing a list of files in a directory related to s10-flasher, including applications and text files. .


    Command line of the Builder S10 firmware flasher showing usage instructions. .
  • #145 21465057
    a_jablon
    Level 35  
    I've had a look at this flasher and now I know why.... The secret is in the run-build-s10-flasher.cmd file

    Below its contents:

    build-s10-flasher SAFM01.6.exe SAFM01.6_30092015.BIN

    what does this mean? build-s10-flasher.exe expects 2 parameters: an exe output file (name) and a firmware file.

    Convert this to:

    build-s10-flasher fw.exe fw.BIN

    save

    and run run-build-s10-flasher.cmd

    Of course, the firmware should be named fw.bin and the resulting file will be fw.exe
  • #146 21466163
    rtj71
    IT specialist
    I came across this to preview it after writing the post.
    Yesterday after a reboot - without interfering with FW the system started repairing the partition with this drive after which I saw the data from this drive - but it was impossible to copy. On attempting to write FW the flasher crashed and that was it.

    After restarting flasher, unfortunately it doesn't detect the drive, only sometimes it shows up in diskpart/disk management


    Error message stating Can't detect any Device!! with an OK button. .

    In diskpart:

    Screenshot from diskpart showing a list of disks. .

    In disk management:

    Disk initialization window in Windows with MBR and GPT options. .
  • #147 21466775
    a_jablon
    Level 35  
    Sometimes these disks "get up" enough to be readable. This often saves ass in terms of data recovery. It's not a phenomenon - it happens.

    Yes, I confirm: access to the drive is then read-only. Neither move nor delete. Read-only access is possible (for the most part), although I have usually experienced "losses" when recovering data from such drives, which have only appeared for a short while.

    Definitely FLASHER will bring the drive back to life (I don't know for how long - although experience shows that it's not as 'impermanent' as I initially thought). The data after the flasher is applied is irrevocably and irretrievably lost. I've only ever had 2 drives so badly damaged that the flasher gave up, so I'd give it a go if I were you.
  • #148 21473948
    rtj71
    IT specialist
    It went in the end, but a really tough competitor:
    Goodram CX100 firmware upgrade tool interface. .

    Screenshot of CrystalDiskInfo showing the status of a GOODRAM CX100 120 GB drive.
  • #149 21492721
    elyisverantohan
    Level 1  
    Hello, I hope you have a nice day.

    I have a 512GB TeamGroup T-FORCE Vulcan Z SATA SSD.

    About 8 months ago it suddenly died with the well-known SATAFIRM S11 error, it turns out that 6 months ago I tried to repair it by rewriting the firmware (which was originally SBFM 61.5 05092022) SBFM 61.5 17062021 and it gave me an error when reaching 85% that said "AP-Key not enabled by the device" so then I tried to flash other firmwares with similar nomenclature which did flash but did not solve the problem, in short the SSD was left with another name "SATAFIRM SBRDTTEST" and when I tried to use the flashing tool again for the PS3111 with the SBFM 61.5 17062021 firmware it does not recognize the SSD, I attach the log that the Phison Flash ID program gave me, an image of how it currently appears in the equipment manager and an image taken from the internet of the "AP-key" error that it gave me at the beginning as a reference.

    Spoiler:
    v0.8a
    Drive: 1(ATA)
    OS: 10.0 build 19045
    Model: SATAFIRM SBRDTTEST
    Fw : SBSM6B.5
    Size : 488386 MB
    Bank00: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x1e - Toshiba TLC 16k 512Gb/CE 512Gb/die 2Plane/die
    Bank01: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x16 - Toshiba TLC 16k 512Gb/CE 512Gb/die 2Plane/die
    Bank04: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x1e - Toshiba TLC 16k 512Gb/CE 512Gb/die 2Plane/die
    Bank05: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x16 - Toshiba TLC 16k 512Gb/CE 512Gb/die 2Plane/die
    Bank08: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x1e - Toshiba TLC 16k 512Gb/CE 512Gb/die 2Plane/die
    Bank09: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x16 - Toshiba TLC 16k 512Gb/CE 512Gb/die 2Plane/die
    Bank12: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x1e - Toshiba TLC 16k 512Gb/CE 512Gb/die 2Plane/die
    Bank13: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x16 - Toshiba TLC 16k 512Gb/CE 512Gb/die 2Plane/die
    Controller : PS3108
    Flash CE : 8
    Flash Channel : 2
    Dram Size,MB : 1
    Block per Die : 3324
    Block per CE : 0
    Page per Block: 1344


    Defects All Early Later
    Bank00: 207207207
    Bank01: 207207207
    Bank04: 207207207
    Bank05: 207207207
    Bank08: 207207207
    Bank09: 207207207
    Bank12: 207207207
    Bank13: 207207207
    Total : 1656 1656 1656

    Early defect list
    Bank00: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank01: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank04: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank05: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank08: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank09: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank12: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank13: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

    Later defect list
    Bank00: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank01: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank04: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank05: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank08: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank09: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank12: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    Bank13: 207 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



    PS3111SB Update Tool interface with error messages.
    Screenshot showing an unknown 128 GB disk that is not initialized or assigned.
  • #150 21508033
    antonio0206z
    Level 2  
    I'm having a problem with a 480g Patriot Elite SSD. I'm getting the error "Sarafin S11." I don't know which one to run for that SSD.
    2.5" SATA III SSD
ADVERTISEMENT