» Ремонт SSD накопителей на контроллерах SandForce

Hi there!
I can't speak Russian, that's why i will write in English.
I have a problematic OCZ, what is maybe an Agility3 60GB version, unfortunately its only the logic board itself. OCZ PCB-0135-X01 03-2011 equipped with 8 * PF412 AL1144.
I've tried the following 60GB versions,
22021-
22158-
22186-
22214-
22330-
22333-
22364-
22367-
22432-
22434-
22621-
22785-
22790-
and 120GB versions:
22187-
22321-
22405-
22451-
22626-
22758-
22853-
27232-
Almost every version ended up with DMESG errors.
However Agility drives are mostly with sync nands, I've tried
22214:
[root@fedoraToshiba SF_Genv170]$ su
Jelszó:
[root@fedoraToshiba SF_Genv170]# ./SF_Genesis -PROCESS_SSD 1:0:0:0 /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22214.0.driveconfig OCZ-AGILITY3 5707C18000021786 log=/home/root/Asztal/Agility3/120/marsai
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SandForce Genesis Utility v1.7.0.01020130612-fc14-32bit
SF_Core Library: v1.7.1.20130612-fc14-32bit

Copyright 2010-2012, LSI Corporation, All Rights Reserved Worldwide.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Sat 07/23/2016 19:53:24] - SF_Genesis has been invoked with the following parameters:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
argv[1]: -PROCESS_SSD
argv[2]: 1:0:0:0
argv[3]: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
argv[4]: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22214.0.driveconfig
argv[5]: OCZ-AGILITY3
argv[6]: 5707C18000021786
argv[7]: log=/home/root/Asztal/Agility3/120/marsai
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Sat 07/23/2016 19:53:24] - Instructing the operating system to purge any existing cached data for device: '1:0:0:0'
[Sat 07/23/2016 19:53:30] - Issuing a discovery command for device: '1:0:0:0'
[Sat 07/23/2016 19:53:35] - Discovery command completed...
[Sat 07/23/2016 19:53:35] - Waiting 5 seconds for the system to settle...
[Sat 07/23/2016 19:53:40] - Device designation string '1:0:0:0' is mapped to node '/dev/sg0'
[Sat 07/23/2016 19:53:40] - Proceeding to process SSD device with the following parameters:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DeviceName = /dev/sg0
MFP Package Filename = /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
Configuration File = /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22214.0.driveconfig
Serial No. = OCZ-AGILITY3
World Wide Name = 5707C18000021786
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Sat 07/23/2016 19:53:40] - Successfully received the IDENTIFY data from the drive...
[Sat 07/23/2016 19:53:40] - Validating Manufacturing Firmware Package: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
[Sat 07/23/2016 19:54:21] - Successfully opened the package: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
[Sat 07/23/2016 19:54:21] - file /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22214.0.driveconfig Loaded successfully
[Sat 07/23/2016 19:54:21] - Warning: Unable to query diagnostics information to perform power management settings check
[Sat 07/23/2016 19:54:21] - B01 Power Management configuration request detected
[Sat 07/23/2016 19:54:21] - Successfully extracted *.DriveConfig file: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22214.0.driveconfig
[Sat 07/23/2016 19:54:21] - Extracted Config_ID: 1 (22214) in DriveConfig file: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22214.0.driveconfig
[Sat 07/23/2016 19:54:21] - Extracted SerialOutputControl: 0
[Sat 07/23/2016 19:54:21] - Searching for flashware image for configuration 22214
[Sat 07/23/2016 19:54:21] - Manifest found for configuration 22214
[Sat 07/23/2016 19:54:21] - Flashware image extracted: 22214_fw_cl_mlc_Micron_64Gb_MT29F64G08CBAAAWP_2Q_1C_1D_PP_R00751_s512.vic
[Sat 07/23/2016 19:54:21] - Searching for manufacturing image for configuration 22214
[Sat 07/23/2016 19:54:21] - Manifest found for configuration 22214
[Sat 07/23/2016 19:54:21] - Manufacturing image extracted: 22214_mf_mlc_Micron_64Gb_MT29F64G08CBAAAWP_2Q_1C_1D_PP_R00751_s512.vic
[Sat 07/23/2016 19:54:21] - Proceeding in ROM mode, download feature 3...
[Sat 07/23/2016 19:59:12] - FATAL_ERROR: Could not download MFB to the drive...(0x11000001:SF_SG_DEVICE_CHECK_CONDITION_ERROR)


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Extended Error data:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ATA COMMAND : 0x0092 (146)
ATA FEATURE : 0x0003 (3)
Device Status: 0x0001 (1)
Driver Status: 0x0000 (0)
Host Status: 0x0008 (8)
~~~~~~~~~~~~~~
Sense Data:
~~~~~~~~~~~~~~
0 - No Sense: 114 (0x72) OK
1 - Recovered Error: 11 (0x0B) FAIL
2 - Not Ready: 0 (0x00) OK
3 - Medium Error: 0 (0x00) OK
4 - Hardware Error: 0 (0x00) OK
5 - Illegal Request: 0 (0x00) OK
6 - Unit Attention: 0 (0x00) OK
7 - Data Protect: 14 (0x0E) OK
8 - Blank Check: 9 (0x09) OK
9 - Vendor Specific: 12 (0x0C) OK
10 - Copy Aborted: 0 (0x00) OK
11 - Aborted Command: 0 (0x00) OK
12 - Equal Comparison: 0 (0x00) NA
13 - Volume Overflow: 0 (0x00) NA
14 - Miscompare: 0 (0x00) OK
15 - Reserved: 128 (0x80) NA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
System Trace:
~~~~~~~~~~~~~~~~

[ 348.558510] (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
[ 350.040357] wlan0: authenticate with 60:e3:27:c4:b6:f4 (try 1)
[ 350.240035] wlan0: authenticate with 60:e3:27:c4:b6:f4 (try 2)
[ 350.243409] wlan0: authenticated
[ 350.250269] wlan0: associate with 60:e3:27:c4:b6:f4 (try 1)
[ 350.450026] wlan0: associate with 60:e3:27:c4:b6:f4 (try 2)
[ 350.650045] wlan0: associate with 60:e3:27:c4:b6:f4 (try 3)
[ 350.850040] wlan0: association with 60:e3:27:c4:b6:f4 timed out
[ 353.048039] ata2: softreset failed (1st FIS failed)
[ 353.048057] ata2: hard resetting link
[ 358.207065] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 358.207077] ata2.00: link online but device misclassifed
[ 365.342519] wlan0: authenticate with 60:e3:27:c4:b6:f4 (try 1)
[ 365.542044] wlan0: authenticate with 60:e3:27:c4:b6:f4 (try 2)
[ 365.553524] wlan0: authenticated
[ 365.560507] wlan0: associate with 60:e3:27:c4:b6:f4 (try 1)
[ 365.572523] wlan0: RX AssocResp from 60:e3:27:c4:b6:f4 (capab=0x431 status=0 aid=3)
[ 365.572533] wlan0: associated
[ 365.576144] cfg80211: Calling CRDA for country: US
[ 365.610358] cfg80211: Regulatory domain changed to country: US
[ 365.610367] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 365.610376] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 365.610383] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 365.610390] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 365.610396] (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 365.610403] (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 365.610409] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 388.207073] ata2.00: qc timeout (cmd 0xec)
[ 388.207093] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 388.207100] ata2.00: revalidation failed (errno=-5)
[ 388.207109] ata2.00: disabled
[ 388.207142] ata2: exception Emask 0x40 SAct 0x0 SErr 0x800 action 0x6 frozen t4
[ 388.207150] ata2: SError: { HostInt }
[ 388.207164] ata2: hard resetting link
[ 396.729108] EXT4-fs error (device sdb1): ext4_mb_generate_buddy: EXT4-fs: group 18: 13922 blocks in bitmap, 13923 in gd
[ 398.207036] ata2: softreset failed (1st FIS failed)
[ 398.207051] ata2: hard resetting link
[ 408.208037] ata2: softreset failed (1st FIS failed)
[ 408.208052] ata2: hard resetting link
[ 443.209036] ata2: softreset failed (1st FIS failed)
[ 443.209054] ata2: hard resetting link
[ 448.412064] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 448.412076] ata2.00: link online but device misclassifed
[ 448.412124] ata2: EH complete

minicom:

<MFB> FlashQuadCtrlVerifyFlash: Lane 0 CE 0 Bus 0
<MFB> MarkBadRootIBA rblock0 bus0 ce0 Die0
<MFB> SetFeature=0x05, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 0 CE 0 Bus 1
<MFB> FlashQuadCtrlVerifyFlash: Lane 1 CE 0 Bus 0
<MFB> SetFeature=0x05, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 1 CE 0 Bus 1
<MFB> FlashQuadCtrlVerifyFlash: Lane 2 CE 0 Bus 0
<MFB> SetFeature=0x05, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 2 CE 0 Bus 1
<MFB> FlashQuadCtrlVerifyFlash: Lane 3 CE 0 Bus 0
<MFB> SetFeature=0x05, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 3 CE 0 Bus 1
<MFB> ********************************************
<MFB> ***** Detected failing FLASH device(s) *****
<MFB> ********************************************
<MFB>
<MFB> Failed to set async mode(returned feature value=00000000)
<MFB> Retrying Async timing change
<MFB> Failed to set async mode(returned feature value=00000000)
<MFB> Retrying Async timing change
<MFB> Failed to set async mode(returned feature value=00000000)
<MFB>
PANIC: file=src/flash/FlashQuadCtrl.c line=3208
PANIC: error=0x80030005
<MFB>
<MFB> Flash Ctrl IntReg(83004004) = 0x00000000
<MFB> Flash Stat IntReg(83000004) = 0x00000000
<MFB> PANIC: call stack [7]: 4002DB30
<MFB> PANIC: call stack [6]: 4002DAAF
<MFB> PANIC: call stack [5]: 4000E9B2
<MFB> PANIC: call stack [4]: 4000EB94
<MFB> PANIC: call stack [3]: 400107AD
<MFB> PANIC: call stack [2]: 40010CCC
<MFB> PANIC: call stack [1]: 40015280
<MFB> PANIC: call stack [0]: 4000100A
<MFB>
<MFB> *** MFB 582 Jul 3 2014 03:18:59 B:FW_PPRO_5_6_1_20140326_836378:FW_PPRO_5_8_20
<MFB> *** Build Option = cfg/cfg_MLC_Micron_64Gb_MT29F64G08CBAAAWP_2Q_1C_1D -tmits=2T
<MFB> *** System Clock = 300 MHz
<MFB> *** FLASH_DIV_BY = 6

<MFB>
FCTL REGS (at 8300_0000, 1024 bytes)

8300_0000: 00804090 00000000 20001DAC 00000003 &#65533;@&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533; &#65533;&#65533;&#65533;&#65533;

###I thought the Flash is maybe sync only, so tried the 22186:

[root@fedoraToshiba SF_Genv170]# ./SF_Genesis -PROCESS_SSD 1:0:0:0 /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22186.0. OCZ-AGILITY3 5707C18000021786 log=/home/root/Asztal/Agility3/120/marsai
22186.0.agility3.driveconfig 22186.0.driveconfig
22186.0.agility3.edriveconfig
[root@fedoraToshiba SF_Genv170]# ./SF_Genesis -PROCESS_SSD 1:0:0:0 /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22186.0.driveconfig OCZ-AGILITY3 5707C18000021786 log=/home/root/Asztal/Agility3/120/marsai
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SandForce Genesis Utility v1.7.0.01020130612-fc14-32bit
SF_Core Library: v1.7.1.20130612-fc14-32bit

Copyright 2010-2012, LSI Corporation, All Rights Reserved Worldwide.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Sat 07/23/2016 20:00:42] - SF_Genesis has been invoked with the following parameters:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
argv[1]: -PROCESS_SSD
argv[2]: 1:0:0:0
argv[3]: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
argv[4]: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22186.0.driveconfig
argv[5]: OCZ-AGILITY3
argv[6]: 5707C18000021786
argv[7]: log=/home/root/Asztal/Agility3/120/marsai
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Sat 07/23/2016 20:00:42] - Instructing the operating system to purge any existing cached data for device: '1:0:0:0'
[Sat 07/23/2016 20:00:47] - Issuing a discovery command for device: '1:0:0:0'
^C
[root@fedoraToshiba SF_Genv170]# ./SF_Genesis -PROCESS_SSD 1:0:0:0 /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22186.0.driveconfig OCZ-AGILITY3 5707C18000021786 log=/home/root/Asztal/Agility3/120/marsai
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SandForce Genesis Utility v1.7.0.01020130612-fc14-32bit
SF_Core Library: v1.7.1.20130612-fc14-32bit

Copyright 2010-2012, LSI Corporation, All Rights Reserved Worldwide.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Sat 07/23/2016 20:01:25] - SF_Genesis has been invoked with the following parameters:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
argv[1]: -PROCESS_SSD
argv[2]: 1:0:0:0
argv[3]: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
argv[4]: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22186.0.driveconfig
argv[5]: OCZ-AGILITY3
argv[6]: 5707C18000021786
argv[7]: log=/home/root/Asztal/Agility3/120/marsai
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Sat 07/23/2016 20:01:25] - Instructing the operating system to purge any existing cached data for device: '1:0:0:0'
[Sat 07/23/2016 20:01:30] - Issuing a discovery command for device: '1:0:0:0'
[Sat 07/23/2016 20:01:35] - Discovery command completed...
[Sat 07/23/2016 20:01:35] - Waiting 5 seconds for the system to settle...
[Sat 07/23/2016 20:01:40] - Device designation string '1:0:0:0' is mapped to node '/dev/sg0'
[Sat 07/23/2016 20:01:40] - Proceeding to process SSD device with the following parameters:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DeviceName = /dev/sg0
MFP Package Filename = /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
Configuration File = /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22186.0.driveconfig
Serial No. = OCZ-AGILITY3
World Wide Name = 5707C18000021786
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Sat 07/23/2016 20:01:40] - Successfully received the IDENTIFY data from the drive...
[Sat 07/23/2016 20:01:40] - Validating Manufacturing Firmware Package: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
[Sat 07/23/2016 20:01:58] - Successfully opened the package: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
[Sat 07/23/2016 20:01:58] - file /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22186.0.driveconfig Loaded successfully
[Sat 07/23/2016 20:01:58] - Warning: Unable to query diagnostics information to perform power management settings check
[Sat 07/23/2016 20:01:58] - B01 Power Management configuration request detected
[Sat 07/23/2016 20:01:58] - Successfully extracted *.DriveConfig file: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22186.0.driveconfig
[Sat 07/23/2016 20:01:58] - Extracted Config_ID: 1 (22186) in DriveConfig file: /home/root/Asztal/582_asiacom2012_2.25/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22186.0.driveconfig
[Sat 07/23/2016 20:01:58] - Extracted SerialOutputControl: 0
[Sat 07/23/2016 20:01:58] - Searching for flashware image for configuration 22186
[Sat 07/23/2016 20:01:58] - Manifest found for configuration 22186
[Sat 07/23/2016 20:01:58] - Flashware image extracted: 22186_fw_cl_mlc_Micron_64Gb_MT29F64G08CBAABWP_2Q_1C_1D_PP_R00712_s512.vic
[Sat 07/23/2016 20:01:58] - Searching for manufacturing image for configuration 22186
[Sat 07/23/2016 20:01:58] - Manifest found for configuration 22186
[Sat 07/23/2016 20:01:58] - Manufacturing image extracted: 22186_mf_mlc_Micron_64Gb_MT29F64G08CBAABWP_2Q_1C_1D_PP_R00712_s512.vic
[Sat 07/23/2016 20:01:58] - Proceeding in ROM mode, download feature 3...
[Sat 07/23/2016 20:06:49] - FATAL_ERROR: Could not download MFB to the drive...(0x11000001:SF_SG_DEVICE_CHECK_CONDITION_ERROR)


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Extended Error data:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ATA COMMAND : 0x0092 (146)
ATA FEATURE : 0x0003 (3)
Device Status: 0x0001 (1)
Driver Status: 0x0000 (0)
Host Status: 0x0008 (8)
~~~~~~~~~~~~~~
Sense Data:
~~~~~~~~~~~~~~
0 - No Sense: 114 (0x72) OK
1 - Recovered Error: 11 (0x0B) FAIL
2 - Not Ready: 0 (0x00) OK
3 - Medium Error: 0 (0x00) OK
4 - Hardware Error: 0 (0x00) OK
5 - Illegal Request: 0 (0x00) OK
6 - Unit Attention: 0 (0x00) OK
7 - Data Protect: 14 (0x0E) OK
8 - Blank Check: 9 (0x09) OK
9 - Vendor Specific: 12 (0x0C) OK
10 - Copy Aborted: 0 (0x00) OK
11 - Aborted Command: 0 (0x00) OK
12 - Equal Comparison: 0 (0x00) NA
13 - Volume Overflow: 0 (0x00) NA
14 - Miscompare: 0 (0x00) OK
15 - Reserved: 128 (0x80) NA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
System Trace:
~~~~~~~~~~~~~~~~

[ 620.016109] res 40/00:00:80:00:00/00:00:00:00:00/e0 Emask 0x4 (timeout)
[ 620.016116] ata2.00: status: { DRDY }
[ 620.016129] ata2: hard resetting link
[ 630.016037] ata2: softreset failed (1st FIS failed)
[ 630.016051] ata2: hard resetting link
[ 640.017031] ata2: softreset failed (1st FIS failed)
[ 640.017045] ata2: hard resetting link
[ 675.018034] ata2: softreset failed (1st FIS failed)
[ 675.018051] ata2: limiting SATA link speed to 1.5 Gbps
[ 675.018058] ata2: hard resetting link
[ 680.172057] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 680.172069] ata2.00: link online but device misclassifed
[ 685.172053] ata2.00: qc timeout (cmd 0xec)
[ 685.172072] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 685.172080] ata2.00: revalidation failed (errno=-5)
[ 685.172096] ata2: hard resetting link
[ 695.172039] ata2: softreset failed (1st FIS failed)
[ 695.172055] ata2: hard resetting link
[ 705.172041] ata2: softreset failed (1st FIS failed)
[ 705.172056] ata2: hard resetting link
[ 740.173039] ata2: softreset failed (1st FIS failed)
[ 740.173058] ata2: hard resetting link
[ 745.331657] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 745.331668] ata2.00: link online but device misclassifed
[ 755.331065] ata2.00: qc timeout (cmd 0xec)
[ 755.331085] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 755.331092] ata2.00: revalidation failed (errno=-5)
[ 755.331109] ata2: hard resetting link
[ 765.331057] ata2: softreset failed (1st FIS failed)
[ 765.331072] ata2: hard resetting link
[ 775.331137] ata2: softreset failed (1st FIS failed)
[ 775.331151] ata2: hard resetting link
[ 810.332057] ata2: softreset failed (1st FIS failed)
[ 810.332077] ata2: hard resetting link
[ 815.490058] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 815.490071] ata2.00: link online but device misclassifed
[ 845.490052] ata2.00: qc timeout (cmd 0xec)
[ 845.490072] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 845.490079] ata2.00: revalidation failed (errno=-5)
[ 845.490088] ata2.00: disabled
[ 845.490122] ata2: exception Emask 0x40 SAct 0x0 SErr 0x800 action 0x6 frozen t4
[ 845.490130] ata2: SError: { HostInt }
[ 845.490142] ata2: hard resetting link
[ 855.491040] ata2: softreset failed (1st FIS failed)
[ 855.491055] ata2: hard resetting link
[ 865.491041] ata2: softreset failed (1st FIS failed)
[ 865.491056] ata2: hard resetting link
[ 900.492041] ata2: softreset failed (1st FIS failed)
[ 900.492059] ata2: hard resetting link
[ 905.694065] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 905.694078] ata2.00: link online but device misclassifed
[ 905.694126] ata2: EH complete
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Sat 07/23/2016 20:06:49] - End of Genesis manufacturing log.
[Sat 07/23/2016 20:06:49] - Exiting...
[Sat 07/23/2016 20:06:50] - Overall Result for Device: /dev/sg0 ****** FAIL ******
[root@fedoraToshiba SF_Genv170]#

# Minicom:

<MFB> FlashQuadCtrlVerifyFlash: Lane 0 CE 0 Bus 0
<MFB> FLASH access error: busOfs 0 ceID 0 Lane0 FlshXfrSts=00000004 pCmdSeq=3FFE0D04
<MFB> MarkBadRootIBA rblock0 bus0 ce0 Die0
<MFB> Retrying ONFI2 init
<MFB> FLASH access error: busOfs 0 ceID 0 Lane0 FlshXfrSts=00000004 pCmdSeq=3FFE0D04
<MFB> Retrying ONFI2 init
<MFB> FLASH access error: busOfs 0 ceID 0 Lane0 FlshXfrSts=00000004 pCmdSeq=3FFE0D04
<MFB> Retrying ONFI2 init
<MFB> FLASH access error: busOfs 0 ceID 0 Lane0 FlshXfrSts=00000004 pCmdSeq=3FFE0D04
<MFB> Retrying ONFI2 init
<MFB> FLASH access error: busOfs 0 ceID 0 Lane0 FlshXfrSts=00000004 pCmdSeq=3FFE0D04
<MFB> Retrying ONFI2 init
<MFB> FLASH access error: busOfs 0 ceID 0 Lane0 FlshXfrSts=00000004 pCmdSeq=3FFE0D04
<MFB>
PANIC: file=src/flash/FlashQuadCtrl.c line=3177
PANIC: error=0x80030005
<MFB>
<MFB> Flash Ctrl IntReg(83004004) = 0x00000000
<MFB> Flash Stat IntReg(83000004) = 0x00000004
<MFB> PANIC: call stack [7]: 4002DCE0
<MFB> PANIC: call stack [6]: 4002DC5F
<MFB> PANIC: call stack [5]: 4000EB5B
<MFB> PANIC: call stack [4]: 4000EDE2
<MFB> PANIC: call stack [3]: 40010908
<MFB> PANIC: call stack [2]: 40010E80
<MFB> PANIC: call stack [1]: 40015438
<MFB> PANIC: call stack [0]: 4000100A
<MFB>
<MFB> *** MFB 582 Jul 3 2014 03:17:29 B:FW_PPRO_5_6_1_20140326_836378:FW_PPRO_5_8_20
<MFB> *** Build Option = cfg/cfg_MLC_Micron_64Gb_MT29F64G08CBAABWP_2Q_1C_1D -noenterT
<MFB> *** System Clock = 300 MHz
<MFB> *** FLASH_DIV_BY = 2

<MFB>
FCTL REGS (at 8300_0000, 1024 bytes)

8300_0000: 01A04090 00000004 20001DAC 00000003 &#65533;@&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533; &#65533;&#65533;&#65533;&#65533;

This two config shows any sign of activity.
Have you ever meet a problem like this?

Thanks

Цитата:

[Sat 07/23/2016 20:01:58] - Proceeding in ROM mode, download feature 3...
[Sat 07/23/2016 20:06:49] - FATAL_ERROR: Could not download MFB to the drive...(0x11000001:SF_SG_DEVICE_CHECK_CONDITION_ERROR)

Most probably your ssd have damaged cpu.

Сегодня попробовал залить комплект 22200, вот что получил
[more=Лог Генезиса]
<?xml version = "1.0"?>
<Genesis_Log>
<Log_Body>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Overall Summary:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Start Time: Sun, 07/24/2016 @ 21:42:23
End Time: Sun, 07/24/2016 @ 21:43:35
OverallResult: FAIL
ExitCode: (0x10090009:SF_GENESIS_CDU_ERROR)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Environment Settings:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Input Parameters:
argv[1]: -PROCESS_SSD
argv[2]: 0:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22200.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/log3/22200.LOG

Log File: /home/SSD_recovery/SSD/log3/22200.LOG
Hostname: localhost.localdomain
Host IP Address: 127.0.0.1
Port Number: 0
DeviceName: /dev/sg0
SF_Genesis Version: v1.5.21.20110919-fc14-32bit
SF_Core Library Version: v1.7.0.20110919-fc14-32bit
SF_OS_Information: Linux 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Post Processing Device Information:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
WWN OUI: UNKNOWN
WWN UniqueID: UNKNOWN
Serial No.: UNKNOWN
Model No.: UNKNOWN
Firmware Revision: UNKNOWN
ROM Revision: UNKNOWN
NAND Page Size: UNKNOWN
Number Of Chip Enable: UNKNOWN
Logical Sectors: UNKNOWN
NAND ID: UNKNOWN
Flash Manufacturer: UNKNOWN
Flash Device: UNKNOWN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SandForce Genesis Utility v1.5.21.20110919-fc14-32bit
SF_Core Library: v1.7.0.20110919-fc14-32bit

Copyright 2010-2011, SandForce Inc., All Rights Reserved Worldwide.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Sun 07/24/2016 21:42:23] - SF_Genesis has been invoked with the following parameters:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
argv[1]: -PROCESS_SSD
argv[2]: 0:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22200.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/log3/22200.LOG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Sun 07/24/2016 21:42:23] - Instructing the operating system to purge any existing cached data for device: '0:0:0:0'
[Sun 07/24/2016 21:42:31] - Issuing a discovery command for device: '0:0:0:0'
[Sun 07/24/2016 21:42:37] - Discovery command completed...
[Sun 07/24/2016 21:42:37] - Waiting 5 seconds for the system to settle...
[Sun 07/24/2016 21:42:42] - Device designation string '0:0:0:0' is mapped to node '/dev/sg0'
[Sun 07/24/2016 21:42:42] - Proceeding to process SSD device with the following parameters:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DeviceName = /dev/sg0
MFP Package Filename = /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
Configuration File = /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22200.0.driveconfig
Serial No. = 12345
World Wide Name = www_123
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Sun 07/24/2016 21:42:42] - Successfully received the IDENTIFY data from the drive...
[Sun 07/24/2016 21:42:54] - Successfully opened the package: /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
[Sun 07/24/2016 21:42:54] - Successfully extracted *.DriveConfig file: /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22200.0.driveconfig
[Sun 07/24/2016 21:42:54] - Extracted Config_ID: 1 (22200) in DriveConfig file: /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22200.0.driveconfig
[Sun 07/24/2016 21:42:54] - Extracted SerialOutputControl: 0
[Sun 07/24/2016 21:42:54] - Successfully extracted Config record: 22200
[Sun 07/24/2016 21:42:54] - Successfully extracted flashware image: 22200_fw_cl_mlc_Toshiba_32Gb_TH58NVG6D2FLA49_2Q_2C_1D_PP_R00744_s512.vic
[Sun 07/24/2016 21:42:54] - Successfully extracted manufacturing image: 22200_mf_mlc_Toshiba_32Gb_TH58NVG6D2FLA49_2Q_2C_1D_PP_R00744_s512.vic
[Sun 07/24/2016 21:42:54] - Proceeding in ROM mode, download feature 1...
[Sun 07/24/2016 21:43:12] - Successfully downloaded MFB to the drive...
[Sun 07/24/2016 21:43:12] - Waiting (5 sec) for the drive to settle...
[Sun 07/24/2016 21:43:17] - Successfully received the IDENTIFY data from the drive...
[Sun 07/24/2016 21:43:17] - Firmware revision reported to be: '582ABBM0'. This indicates MFB download was successful.
[Sun 07/24/2016 21:43:17] - Successfully enabled SMART capabilities...
[Sun 07/24/2016 21:43:35] - FATAL_ERROR: Could not perform the DiagUnlock() operation on the drive... (0x00100001:SF_SATA_DEVICE_NOT_PRESENT_ERROR)
[Sun 07/24/2016 21:43:35] - End of Genesis manufacturing log.
[Sun 07/24/2016 21:43:35] - Exiting...


</Log_Body>

<Overall_Summary>
<Start_Time> Sun, 07/24/2016 @ 21:42:23 </Start_Time>
<End_Time> Sun, 07/24/2016 @ 21:43:35 </End_Time>
<Overall_Result> FAIL </Overall_Result>
<Exit_Code> (0x10090009:SF_GENESIS_CDU_ERROR) </Exit_Code>
</Overall_Summary>

<Environment_Settings>
<Input_Parameters>
argv[1]: -PROCESS_SSD
argv[2]: 0:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/FW_PPRO_5_8_2_Release.906190.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/5.8.2/lic/asiacom_SF-2000_20120629_lic/FW_PPRO_5_8_2_Release.906190.release--0/Configuration_Files/22200.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/log3/22200.LOG
</Input_Parameters>
<Log_File> /home/SSD_recovery/SSD/log3/22200.LOG </Log_File>
<Hostname> localhost.localdomain </Hostname>
<Host_IP_Address> 127.0.0.1 </Host_IP_Address>
<Port_Number> 0 </Port_Number>
<Device_Name> /dev/sg0 </Device_Name>
<SF_Genesis_Version> v1.5.21.20110919-fc14-32bit </SF_Genesis_Version>
<SF_Core_Library_Version> v1.7.0.20110919-fc14-32bit </SF_Core_Library_Version>
<SF_OS_Information> Linux 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686 </SF_OS_Information>
</Environment_Settings>

<Post_Processing_Device_Info>
<WWN_OUI> UNKNOWN </WWN_OUI>
<WWN_UniqueID> UNKNOWN </WWN_UniqueID>
<Serial_Number> UNKNOWN </Serial_Number>
<Model_Number> UNKNOWN </Model_Number>
<Firmware_Revision> UNKNOWN </Firmware_Revision>
<ROM_Revision> UNKNOWN </ROM_Revision>
<NAND_Page_Size> UNKNOWN </NAND_Page_Size>
<Number_Of_Chip_Enable> UNKNOWN </Number_Of_Chip_Enable>
<Logical_Sectors> UNKNOWN </Logical_Sectors>
<NAND_ID> UNKNOWN </NAND_ID>
<Flash_Manufacturer> UNKNOWN </Flash_Manufacturer>
<Flash_Device> UNKNOWN </Flash_Device>
</Post_Processing_Device_Info>

</Genesis_Log>

[Sun 07/24/2016 21:43:35] - Overall Result for Device: /dev/sg0 ****** FAIL ******
[/more]

[more=Лог терминала]
[ROM] Chip ID 0x200026BB

*** ROM Rev 20D Dec 20 2010 Build 288571 ***
[ROM] Force Download: waiting for Download Microcode Command...
[ROM] Waiting for Link to come up...
[ROM] Link is UP.
[ROM] Undec Cmd 0xe0
[ROM] Soft Reset
[ROM] Cleared By Host
[ROM] Undec Cmd 0xec
[ROM] Undec Cmd 0xef
[ROM] Undec Cmd 0xec
[ROM] Undec Cmd 0xe0
[ROM] Hard Reset ===> Link is Down.
[ROM] PHY Ready
[ROM] Sig Sent
[ROM] Soft Reset
[ROM] Cleared By Host
[ROM] Undec Cmd 0xec
[ROM] Undec Cmd 0xef
[ROM] Undec Cmd 0xec
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Undec Cmd 0xec
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Undec Cmd 0xec
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Data Cmd
[ROM] READ CMD
[ROM] Undec Cmd 0xec
[ROM] Undec Cmd 0x92
[ROM] non-DMA
<MFB> FlashQuadCtrlVerifyFlash: Lane 0 CE 0 Bus 0
<MFB> MarkBadRootIBA rblock0 bus0 ce0 Die0
<MFB> FlashQuadCtrlVerifyFlash: Lane 0 CE 0 Bus 1
<MFB> MarkBadRootIBA rblock0 bus1 ce0 Die0
<MFB> FlashQuadCtrlVerifyFlash: Lane 0 CE 1 Bus 0
<MFB> MarkBadRootIBA rblock0 bus0 ce1 Die0
<MFB> SetFeature=0x04, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 0 CE 1 Bus 1
<MFB> MarkBadRootIBA rblock0 bus1 ce1 Die0
<MFB> SetFeature=0x04, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 1 CE 0 Bus 0
<MFB> FlashQuadCtrlVerifyFlash: Lane 1 CE 0 Bus 1
<MFB> FlashQuadCtrlVerifyFlash: Lane 1 CE 1 Bus 0
<MFB> SetFeature=0x04, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 1 CE 1 Bus 1
<MFB> SetFeature=0x04, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 2 CE 0 Bus 0
<MFB> FlashQuadCtrlVerifyFlash: Lane 2 CE 0 Bus 1
<MFB> FlashQuadCtrlVerifyFlash: Lane 2 CE 1 Bus 0
<MFB> SetFeature=0x04, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 2 CE 1 Bus 1
<MFB> SetFeature=0x04, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 3 CE 0 Bus 0
<MFB> FlashQuadCtrlVerifyFlash: Lane 3 CE 0 Bus 1
<MFB> FlashQuadCtrlVerifyFlash: Lane 3 CE 1 Bus 0
<MFB> SetFeature=0x04, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> FlashQuadCtrlVerifyFlash: Lane 3 CE 1 Bus 1
<MFB> SetFeature=0x04, GetFeature=0x00
<MFB> Retrying Async timing change
<MFB> ********************************************
<MFB> ***** Detected failing FLASH device(s) *****
<MFB> ********************************************
<MFB>
<MFB> ---> Sector size 0 bytes L-Page size 4096 bytes <---
Security: Disabled
H/w Decode enabled
<MFB>

*** MFB 582 Jul 3 2014 03:18:33 B:FW_PPRO_5_6_1_20140326_836378:FW_PPRO_5_8_2_Release-906190
*** Build Options : cfg/cfg_MLC_Toshiba_32Gb_TH58NVG6D2FLA49_2Q_2C_1D -noenterprise -asic -subdir SF-2281_Board -pdump -elog -ecli -release -ecliLevel0 -div2 -sysclk300 -nochipsocket -mfb -noecli -suffix PP_R00744_s512 ANYHOST
*** Chip RevId from HW: B01 (ID=288571), FW Targeted For: B02 ASIC ***
*** SysClk : 300 MHz
*** Packer : 500 MHz
*** Flash : 800 MHz
*** FlaDiv : 2
*** GP1011 : 0 (0=Async ONFI, 1=Toggle, 2=ONFI, 3=Async Toggle)
<MFB>
*** GPIO0 : 1
<MFB> Scap charge wait
<MFB> Scap charge done
<MFB User> libSfStartC enter cfg:3fff46b8
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB User> UserMain: CheckRetiredBlkCntAtClearSmart failed.
<MFB> Soft Reset
<MFB> ---> Sector size 0 bytes L-Page size 4096 bytes <---
<MFB> Soft Reset
<MFB> ---> Sector size 0 bytes L-Page size 4096 bytes <---
<MFB> Link Exception
<MFB> ATAINT:00000220
<MFB> Hard Reset
<MFB> ATAINT:02000200
<MFB> ---> Sector size 0 bytes L-Page size 4096 bytes <---
<MFB> Soft Reset
<MFB> ---> Sector size 0 bytes L-Page size 4096 bytes <---
<MFB> RootFileOpen(): not allowed yet [fid:10, mode:00000001, flags:00000003].
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB User> CtlGetSmartAttribute status = -1
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> READ CMD
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB User> CtlGetSmartAttribute status = -1
<MFB> RootFileOpen(): not allowed yet [fid:10, mode:00000001, flags:00000003].
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB User> CtlGetSmartAttribute status = -1
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB User> ConstructSmartData: 0 out of 0 attributes are filled out
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB User> CtlGetSmartAttribute status = -1
<MFB> RootFileOpen(): not allowed yet [fid:10, mode:00000001, flags:00000003].
<MFB> RootFileOpen(): not allowed yet [fid:8, mode:00000001, flags:00000003].
<MFB User> CtlGetSmartAttribute status = -1
<MFB User> ConstructSmartData: 0 out of 0 attributes are filled out
<MFB User> attributes[0].attributeNum == 0; THE END
[/more]

exwein

Цитата:

Detected failing FLASH

Комплект 22200 для флешек тошиба объемом на 32гб. Как организована память не знаю, т.к. в FW_Worksheet_SFI_SF-2000_140120_Confidential_Gold.xlsx нет его.

Получается все же какая-то флеш битая. На плате чипы памяти расположены в 2 ряда. Как можно определить какая именно флеш мертва?

22200    SF-2281    SF-2281 64GB Toshiba32 MLC LGA 8xTH58NVG6D2FLA49 (RAISE OFF)    Toshiba    32    MLC    TH58NVG6D2FLA49    LGA    8    64    DDP    64    64    125045424    0    MP1p1    TBD    2Q-2C-1D-4L    6    20000    252    0    PP-C00744    PP-R00744    1    External    Universal    0    SF-2281_Board

gnn1953, спасибо.
По корпусам не сходится, у меня TSOP, а я лью комплект для LGA.

gnn1953, если вам не сложно, могли бы вы поделится вашим файлом с описанием конфигураций.

Еще нашел обзор точно такого же ssd, но его там не вскрывали. По этому невозможно сравнить маркировки на чипах памяти.
https://www.overclockers.ru/lab/59571/Nemnogo_melochi_obzor_i_test_SSD_60-64_Gbajt_proizvodstva_Silicon_Power_i_SmartBuy.html
Но из описания ssd
Объем, Гбайт    60
Технический код модели    SP060GBSS3S60S25
Объем, фактически доступный пользователю после создания файловой системы, Гбайт, MBR, NTFS    55.9
Информация, сообщаемая диагностической программой CrystalDiskInfo                
Форм-фактор, дюймы    2.5”
Интерфейс подключения    SATA 6 Гбит/c
Тип памяти, интерфейс памяти    20 нм MLC NAND Micron, асинхронный/ONFi 1.0    20 нм MLC NAND IMFT
Контроллер    SandForce SF-2281
SandForce Signature number     190-0-27094
Версия микропрограммы    520AABF0
Заявленная производителем максимальная скорость чтения, Мбайт/с    550
Заявленная производителем максимальная скорость записи, Мбайт/с    500
Заявленная производителем максимальная скорость записи, IOPS    80 000
Гарантия производителя, лет    3

По сигнатуре должен подходить 27094, но на практике лог вот [more=такой]
<?xml version = "1.0"?>
<Genesis_Log>
<Log_Body>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Overall Summary:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Start Time: Thu, 07/21/2016 @ 19:16:50
End Time: Thu, 07/21/2016 @ 19:19:51
OverallResult: FAIL
ExitCode: (0x10090012:SF_GENESIS_IDENTIFY_ERROR)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Environment Settings:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Input Parameters:
argv[1]: -PROCESS_SSD
argv[2]: 2:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/firmware/27094.LOG

Log File: /home/SSD_recovery/SSD/firmware/27094.LOG
Hostname: localhost.localdomain
Host IP Address: 127.0.0.1
Port Number: 0
DeviceName: /dev/sg0
SF_Genesis Version: v1.5.21.20110919-fc14-32bit
SF_Core Library Version: v1.7.0.20110919-fc14-32bit
SF_OS_Information: Linux 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Post Processing Device Information:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
WWN OUI: UNKNOWN
WWN UniqueID: UNKNOWN
Serial No.: UNKNOWN
Model No.: UNKNOWN
Firmware Revision: UNKNOWN
ROM Revision: UNKNOWN
NAND Page Size: UNKNOWN
Number Of Chip Enable: UNKNOWN
Logical Sectors: UNKNOWN
NAND ID: UNKNOWN
Flash Manufacturer: UNKNOWN
Flash Device: UNKNOWN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




<?xml version = "1.0"?>
<Genesis_Log>
<Log_Body>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Overall Summary:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Start Time: Thu, 07/21/2016 @ 17:45:37
End Time: Thu, 07/21/2016 @ 17:47:05
OverallResult: FAIL
ExitCode: (0x10090014:SF_GENESIS_FW_DOWNLOAD_ERROR)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Environment Settings:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Input Parameters:
argv[1]: -PROCESS_SSD
argv[2]: 2:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/firmware/27094.LOG

Log File: /home/SSD_recovery/SSD/firmware/27094.LOG
Hostname: localhost.localdomain
Host IP Address: 127.0.0.1
Port Number: 0
DeviceName: /dev/sg0
SF_Genesis Version: v1.7.0.01020130612-fc14-32bit
SF_Core Library Version: v1.7.1.20130612-fc14-32bit
SF_OS_Information: Linux 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Post Processing Device Information:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
WWN OUI: UNKNOWN
WWN UniqueID: UNKNOWN
Serial No.: UNKNOWN
Model No.: UNKNOWN
Firmware Revision: UNKNOWN
ROM Revision: UNKNOWN
NAND Page Size: UNKNOWN
Number Of Chip Enable: UNKNOWN
Logical Sectors: UNKNOWN
NAND ID: UNKNOWN
Flash Manufacturer: UNKNOWN
Flash Device: UNKNOWN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




<?xml version = "1.0"?>
<Genesis_Log>
<Log_Body>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Overall Summary:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Start Time: Thu, 07/21/2016 @ 17:44:20
End Time: Thu, 07/21/2016 @ 17:44:42
OverallResult: FAIL
ExitCode: (0x10090012:SF_GENESIS_IDENTIFY_ERROR)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Environment Settings:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Input Parameters:
argv[1]: -PROCESS_SSD
argv[2]: 2:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/firmware/27094.LOG

Log File: /home/SSD_recovery/SSD/firmware/27094.LOG
Hostname: localhost.localdomain
Host IP Address: 127.0.0.1
Port Number: 0
DeviceName: /dev/sg0
SF_Genesis Version: v1.7.0.01020130612-fc14-32bit
SF_Core Library Version: v1.7.1.20130612-fc14-32bit
SF_OS_Information: Linux 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Post Processing Device Information:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
WWN OUI: UNKNOWN
WWN UniqueID: UNKNOWN
Serial No.: UNKNOWN
Model No.: UNKNOWN
Firmware Revision: UNKNOWN
ROM Revision: UNKNOWN
NAND Page Size: UNKNOWN
Number Of Chip Enable: UNKNOWN
Logical Sectors: UNKNOWN
NAND ID: UNKNOWN
Flash Manufacturer: UNKNOWN
Flash Device: UNKNOWN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SandForce Genesis Utility v1.7.0.01020130612-fc14-32bit
SF_Core Library: v1.7.1.20130612-fc14-32bit

Copyright 2010-2012, LSI Corporation, All Rights Reserved Worldwide.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Thu 07/21/2016 17:44:20] - SF_Genesis has been invoked with the following parameters:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
argv[1]: -PROCESS_SSD
argv[2]: 2:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/firmware/27094.LOG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Thu 07/21/2016 17:44:20] - Instructing the operating system to purge any existing cached data for device: '2:0:0:0'
[Thu 07/21/2016 17:44:25] - Issuing a discovery command for device: '2:0:0:0'
[Thu 07/21/2016 17:44:31] - Discovery command completed...
[Thu 07/21/2016 17:44:31] - Waiting 5 seconds for the system to settle...
[Thu 07/21/2016 17:44:36] - Device designation string '2:0:0:0' is mapped to node '/dev/sg0'
[Thu 07/21/2016 17:44:36] - Proceeding to process SSD device with the following parameters:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DeviceName = /dev/sg0
MFP Package Filename = /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
Configuration File = /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
Serial No. = 12345
World Wide Name = www_123
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Thu 07/21/2016 17:44:42] - FATAL_ERROR: Could not get the IDENTIFY data from the drive... (0x11000001:SF_SG_DEVICE_CHECK_CONDITION_ERROR)


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Extended Error data:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ATA COMMAND : 0x00EC (236)
ATA FEATURE : 0x0000 (0)
Device Status: 0x0001 (1)
Driver Status: 0x0000 (0)
Host Status: 0x0008 (8)
~~~~~~~~~~~~~~
Sense Data:
~~~~~~~~~~~~~~
0 - No Sense: 114 (0x72) OK
1 - Recovered Error: 11 (0x0B) FAIL
2 - Not Ready: 0 (0x00) OK
3 - Medium Error: 0 (0x00) OK
4 - Hardware Error: 0 (0x00) OK
5 - Illegal Request: 0 (0x00) OK
6 - Unit Attention: 0 (0x00) OK
7 - Data Protect: 14 (0x0E) OK
8 - Blank Check: 9 (0x09) OK
9 - Vendor Specific: 12 (0x0C) OK
10 - Copy Aborted: 0 (0x00) OK
11 - Aborted Command: 0 (0x00) OK
12 - Equal Comparison: 0 (0x00) NA
13 - Volume Overflow: 1 (0x01) NA
14 - Miscompare: 0 (0x00) OK
15 - Reserved: 0 (0x00) NA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
System Trace:
~~~~~~~~~~~~~~~~

[ 658.476111] ata3: hard resetting link
[ 664.399076] ata3: link is slow to respond, please be patient (ready=0)
[ 693.521078] ata3: SRST failed (errno=-16)
[ 693.521113] ata3: hard resetting link
[ 698.526080] ata3: SRST failed (errno=-16)
[ 698.526110] ata3: reset failed, giving up
[ 698.526137] ata3: hard resetting link
[ 704.449078] ata3: link is slow to respond, please be patient (ready=0)
[ 708.529078] ata3: SRST failed (errno=-16)
[ 708.529093] ata3: hard resetting link
[ 714.452079] ata3: link is slow to respond, please be patient (ready=0)
[ 718.532078] ata3: SRST failed (errno=-16)
[ 718.532093] ata3: hard resetting link
[ 724.455075] ata3: link is slow to respond, please be patient (ready=0)
[ 753.576081] ata3: SRST failed (errno=-16)
[ 753.576120] ata3: limiting SATA link speed to 1.5 Gbps
[ 753.576131] ata3: hard resetting link
[ 758.581076] ata3: SRST failed (errno=-16)
[ 758.581104] ata3: reset failed, giving up
[ 758.581115] ata3: EH complete
[ 870.636567] ata3: exception Emask 0x10 SAct 0x0 SErr 0x1950000 action 0xe frozen
[ 870.636582] ata3: SError: { PHYRdyChg CommWake Dispar LinkSeq TrStaTrns }
[ 870.636603] ata3: hard resetting link
[ 871.510131] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 871.510400] ata3.00: ATA-8: SandForce{200026BB}, 20DABBR0, max UDMA/133
[ 871.510412] ata3.00: 64 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 871.513415] ata3.00: configured for UDMA/133
[ 871.513440] ata3: EH complete
[ 871.513760] scsi 2:0:0:0: Direct-Access ATA SandForce{200026 20DA PQ: 0 ANSI: 5
[ 871.514635] sd 2:0:0:0: [sda] 64 512-byte logical blocks: (32.7 kB/32.0 KiB)
[ 871.514644] sd 2:0:0:0: [sda] 4096-byte physical blocks
[ 871.514754] sd 2:0:0:0: [sda] Write Protect is off
[ 871.514762] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 871.514809] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 871.519459] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 871.520517] sda: unknown partition table
[ 871.525524] sd 2:0:0:0: [sda] Attached SCSI disk
[ 887.008318] ata3: drained 512 bytes to clear DRQ.
[ 887.008337] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 887.008350] ata3.00: failed command: IDENTIFY DEVICE
[ 887.008367] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[ 887.008370] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 887.008377] ata3.00: status: { DRDY }
[ 887.008392] ata3: hard resetting link
[ 887.008396] ata3: nv: skipping hardreset on occupied port
[ 887.462130] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 887.465436] ata3.00: configured for UDMA/133
[ 887.465484] ata3: EH complete
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Thu 07/21/2016 17:44:42] - End of Genesis manufacturing log.
[Thu 07/21/2016 17:44:42] - Exiting...


</Log_Body>

<Overall_Summary>
<Start_Time> Thu, 07/21/2016 @ 17:44:20 </Start_Time>
<End_Time> Thu, 07/21/2016 @ 17:44:42 </End_Time>
<Overall_Result> FAIL </Overall_Result>
<Exit_Code> (0x10090012:SF_GENESIS_IDENTIFY_ERROR) </Exit_Code>
</Overall_Summary>

<Environment_Settings>
<Input_Parameters>
argv[1]: -PROCESS_SSD
argv[2]: 2:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/firmware/27094.LOG
</Input_Parameters>
<Log_File> /home/SSD_recovery/SSD/firmware/27094.LOG </Log_File>
<Hostname> localhost.localdomain </Hostname>
<Host_IP_Address> 127.0.0.1 </Host_IP_Address>
<Port_Number> 0 </Port_Number>
<Device_Name> /dev/sg0 </Device_Name>
<SF_Genesis_Version> v1.7.0.01020130612-fc14-32bit </SF_Genesis_Version>
<SF_Core_Library_Version> v1.7.1.20130612-fc14-32bit </SF_Core_Library_Version>
<SF_OS_Information> Linux 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686 </SF_OS_Information>
</Environment_Settings>

<Post_Processing_Device_Info>
<WWN_OUI> UNKNOWN </WWN_OUI>
<WWN_UniqueID> UNKNOWN </WWN_UniqueID>
<Serial_Number> UNKNOWN </Serial_Number>
<Model_Number> UNKNOWN </Model_Number>
<Firmware_Revision> UNKNOWN </Firmware_Revision>
<ROM_Revision> UNKNOWN </ROM_Revision>
<NAND_Page_Size> UNKNOWN </NAND_Page_Size>
<Number_Of_Chip_Enable> UNKNOWN </Number_Of_Chip_Enable>
<Logical_Sectors> UNKNOWN </Logical_Sectors>
<NAND_ID> UNKNOWN </NAND_ID>
<Flash_Manufacturer> UNKNOWN </Flash_Manufacturer>
<Flash_Device> UNKNOWN </Flash_Device>
</Post_Processing_Device_Info>

</Genesis_Log>

[Thu 07/21/2016 17:44:42] - Overall Result for Device: /dev/sg0 ****** FAIL ******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SandForce Genesis Utility v1.7.0.01020130612-fc14-32bit
SF_Core Library: v1.7.1.20130612-fc14-32bit

Copyright 2010-2012, LSI Corporation, All Rights Reserved Worldwide.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Thu 07/21/2016 17:45:37] - SF_Genesis has been invoked with the following parameters:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
argv[1]: -PROCESS_SSD
argv[2]: 2:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/firmware/27094.LOG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Thu 07/21/2016 17:45:37] - Instructing the operating system to purge any existing cached data for device: '2:0:0:0'
[Thu 07/21/2016 17:45:45] - Issuing a discovery command for device: '2:0:0:0'
[Thu 07/21/2016 17:45:51] - Discovery command completed...
[Thu 07/21/2016 17:45:51] - Waiting 5 seconds for the system to settle...
[Thu 07/21/2016 17:45:56] - Device designation string '2:0:0:0' is mapped to node '/dev/sg0'
[Thu 07/21/2016 17:45:56] - Proceeding to process SSD device with the following parameters:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DeviceName = /dev/sg0
MFP Package Filename = /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
Configuration File = /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
Serial No. = 12345
World Wide Name = www_123
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Thu 07/21/2016 17:45:56] - Successfully received the IDENTIFY data from the drive...
[Thu 07/21/2016 17:45:56] - Validating Manufacturing Firmware Package: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
[Thu 07/21/2016 17:45:59] - Successfully opened the package: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
[Thu 07/21/2016 17:45:59] - file /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig Loaded successfully
[Thu 07/21/2016 17:45:59] - Warning: Unable to query diagnostics information to perform power management settings check
[Thu 07/21/2016 17:45:59] - B01 Power Management configuration request detected
[Thu 07/21/2016 17:45:59] - Successfully extracted *.DriveConfig file: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
[Thu 07/21/2016 17:45:59] - Extracted Config_ID: 1 (27094) in DriveConfig file: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
[Thu 07/21/2016 17:45:59] - Extracted SerialOutputControl: 0
[Thu 07/21/2016 17:45:59] - Searching for flashware image for configuration 27094
[Thu 07/21/2016 17:45:59] - Manifest found for configuration 27094
[Thu 07/21/2016 17:45:59] - Flashware image extracted: 27094_fw_cl_mlc_MIC_64Gb_MT29F64G08CBABAWPES_2Q_1C_1D_PP_R01106_s512.vic
[Thu 07/21/2016 17:45:59] - Searching for manufacturing image for configuration 27094
[Thu 07/21/2016 17:45:59] - Manifest found for configuration 27094
[Thu 07/21/2016 17:45:59] - Manufacturing image extracted: 27094_mf_mlc_MIC_64Gb_MT29F64G08CBABAWPES_2Q_1C_1D_PP_R01106_s512.vic
[Thu 07/21/2016 17:45:59] - Proceeding in ROM mode, download feature 3...
[Thu 07/21/2016 17:47:05] - FATAL_ERROR: Could not download MFB to the drive...(0x11000001:SF_SG_DEVICE_CHECK_CONDITION_ERROR)


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Extended Error data:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ATA COMMAND : 0x0092 (146)
ATA FEATURE : 0x0003 (3)
Device Status: 0x0001 (1)
Driver Status: 0x0000 (0)
Host Status: 0x0008 (8)
~~~~~~~~~~~~~~
Sense Data:
~~~~~~~~~~~~~~
0 - No Sense: 114 (0x72) OK
1 - Recovered Error: 11 (0x0B) FAIL
2 - Not Ready: 0 (0x00) OK
3 - Medium Error: 0 (0x00) OK
4 - Hardware Error: 0 (0x00) OK
5 - Illegal Request: 0 (0x00) OK
6 - Unit Attention: 0 (0x00) OK
7 - Data Protect: 14 (0x0E) OK
8 - Blank Check: 9 (0x09) OK
9 - Vendor Specific: 12 (0x0C) OK
10 - Copy Aborted: 0 (0x00) OK
11 - Aborted Command: 0 (0x00) OK
12 - Equal Comparison: 0 (0x00) NA
13 - Volume Overflow: 1 (0x01) NA
14 - Miscompare: 0 (0x00) OK
15 - Reserved: 224 (0xE0) NA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
System Trace:
~~~~~~~~~~~~~~~~

[ 945.009059] scsi 2:0:0:0: rejecting I/O to dead device
[ 945.009078] scsi 2:0:0:0: rejecting I/O to dead device
[ 945.009094] scsi 2:0:0:0: rejecting I/O to dead device
[ 945.009107] scsi 2:0:0:0: rejecting I/O to dead device
[ 945.009116] scsi 2:0:0:0: [sda] Asking for cache data failed
[ 945.009122] scsi 2:0:0:0: [sda] Assuming drive cache: write through
[ 945.009143] sda: detected capacity change from 0 to 32768
[ 945.009795] ata3.00: disabled
[ 950.015674] ata3: hard resetting link
[ 950.889131] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 950.889401] ata3.00: ATA-8: SandForce{200026BB}, 20DABBR0, max UDMA/133
[ 950.889412] ata3.00: 64 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 950.892417] ata3.00: configured for UDMA/133
[ 950.892441] ata3: EH complete
[ 950.892759] scsi 2:0:0:0: Direct-Access ATA SandForce{200026 20DA PQ: 0 ANSI: 5
[ 950.893264] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 950.893563] sd 2:0:0:0: [sda] 64 512-byte logical blocks: (32.7 kB/32.0 KiB)
[ 950.893571] sd 2:0:0:0: [sda] 4096-byte physical blocks
[ 950.893679] sd 2:0:0:0: [sda] Write Protect is off
[ 950.893686] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 950.893735] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 950.894104] sda: unknown partition table
[ 950.903874] sd 2:0:0:0: [sda] Attached SCSI disk
[ 970.008138] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 970.008153] ata3.00: failed command: DOWNLOAD MICROCODE
[ 970.008171] ata3.00: cmd 92/03:80:00:00:00/00:00:00:00:00/00 tag 0 pio 65536 out
[ 970.008175] res 40/00:01:e0:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 970.008183] ata3.00: status: { DRDY }
[ 970.008197] ata3: hard resetting link
[ 970.008202] ata3: nv: skipping hardreset on occupied port
[ 975.511076] ata3: link is slow to respond, please be patient (ready=0)
[ 980.051087] ata3: SRST failed (errno=-16)
[ 980.051117] ata3: hard resetting link
[ 980.051125] ata3: nv: skipping hardreset on occupied port
[ 985.554080] ata3: link is slow to respond, please be patient (ready=0)
[ 990.094075] ata3: SRST failed (errno=-16)
[ 990.094107] ata3: hard resetting link
[ 990.094115] ata3: nv: skipping hardreset on occupied port
[ 995.597077] ata3: link is slow to respond, please be patient (ready=0)
[ 1025.126095] ata3: SRST failed (errno=-16)
[ 1025.126110] ata3: limiting SATA link speed to 1.5 Gbps
[ 1025.126120] ata3: hard resetting link
[ 1025.126126] ata3: nv: skipping hardreset on occupied port
[ 1030.170080] ata3: SRST failed (errno=-16)
[ 1030.170092] ata3: reset failed, giving up
[ 1030.170099] ata3.00: disabled
[ 1030.170145] ata3: EH complete
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Thu 07/21/2016 17:47:05] - End of Genesis manufacturing log.
[Thu 07/21/2016 17:47:05] - Exiting...


</Log_Body>

<Overall_Summary>
<Start_Time> Thu, 07/21/2016 @ 17:45:37 </Start_Time>
<End_Time> Thu, 07/21/2016 @ 17:47:05 </End_Time>
<Overall_Result> FAIL </Overall_Result>
<Exit_Code> (0x10090014:SF_GENESIS_FW_DOWNLOAD_ERROR) </Exit_Code>
</Overall_Summary>

<Environment_Settings>
<Input_Parameters>
argv[1]: -PROCESS_SSD
argv[2]: 2:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/firmware/27094.LOG
</Input_Parameters>
<Log_File> /home/SSD_recovery/SSD/firmware/27094.LOG </Log_File>
<Hostname> localhost.localdomain </Hostname>
<Host_IP_Address> 127.0.0.1 </Host_IP_Address>
<Port_Number> 0 </Port_Number>
<Device_Name> /dev/sg0 </Device_Name>
<SF_Genesis_Version> v1.7.0.01020130612-fc14-32bit </SF_Genesis_Version>
<SF_Core_Library_Version> v1.7.1.20130612-fc14-32bit </SF_Core_Library_Version>
<SF_OS_Information> Linux 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686 </SF_OS_Information>
</Environment_Settings>

<Post_Processing_Device_Info>
<WWN_OUI> UNKNOWN </WWN_OUI>
<WWN_UniqueID> UNKNOWN </WWN_UniqueID>
<Serial_Number> UNKNOWN </Serial_Number>
<Model_Number> UNKNOWN </Model_Number>
<Firmware_Revision> UNKNOWN </Firmware_Revision>
<ROM_Revision> UNKNOWN </ROM_Revision>
<NAND_Page_Size> UNKNOWN </NAND_Page_Size>
<Number_Of_Chip_Enable> UNKNOWN </Number_Of_Chip_Enable>
<Logical_Sectors> UNKNOWN </Logical_Sectors>
<NAND_ID> UNKNOWN </NAND_ID>
<Flash_Manufacturer> UNKNOWN </Flash_Manufacturer>
<Flash_Device> UNKNOWN </Flash_Device>
</Post_Processing_Device_Info>

</Genesis_Log>

[Thu 07/21/2016 17:47:05] - Overall Result for Device: /dev/sg0 ****** FAIL ******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SandForce Genesis Utility v1.5.21.20110919-fc14-32bit
SF_Core Library: v1.7.0.20110919-fc14-32bit

Copyright 2010-2011, SandForce Inc., All Rights Reserved Worldwide.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Thu 07/21/2016 19:16:50] - SF_Genesis has been invoked with the following parameters:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
argv[1]: -PROCESS_SSD
argv[2]: 2:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/firmware/27094.LOG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Thu 07/21/2016 19:16:50] - Instructing the operating system to purge any existing cached data for device: '2:0:0:0'
[Thu 07/21/2016 19:16:56] - Issuing a discovery command for device: '2:0:0:0'
[Thu 07/21/2016 19:17:02] - Discovery command completed...
[Thu 07/21/2016 19:17:02] - Waiting 5 seconds for the system to settle...
[Thu 07/21/2016 19:17:07] - Device designation string '2:0:0:0' is mapped to node '/dev/sg0'
[Thu 07/21/2016 19:17:07] - Proceeding to process SSD device with the following parameters:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DeviceName = /dev/sg0
MFP Package Filename = /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
Configuration File = /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
Serial No. = 12345
World Wide Name = www_123
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Thu 07/21/2016 19:17:07] - Successfully received the IDENTIFY data from the drive...
[Thu 07/21/2016 19:17:15] - Successfully opened the package: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
[Thu 07/21/2016 19:17:15] - Successfully extracted *.DriveConfig file: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
[Thu 07/21/2016 19:17:15] - Extracted Config_ID: 1 (27094) in DriveConfig file: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
[Thu 07/21/2016 19:17:15] - Extracted SerialOutputControl: 0
[Thu 07/21/2016 19:17:15] - Successfully extracted Config record: 27094
[Thu 07/21/2016 19:17:15] - Successfully extracted flashware image: 27094_fw_cl_mlc_MIC_64Gb_MT29F64G08CBABAWPES_2Q_1C_1D_PP_R01106_s512.vic
[Thu 07/21/2016 19:17:15] - Successfully extracted manufacturing image: 27094_mf_mlc_MIC_64Gb_MT29F64G08CBABAWPES_2Q_1C_1D_PP_R01106_s512.vic
[Thu 07/21/2016 19:17:15] - Proceeding in ROM mode, download feature 1...
[Thu 07/21/2016 19:19:46] - Successfully downloaded MFB to the drive...
[Thu 07/21/2016 19:19:46] - Waiting (5 sec) for the drive to settle...
[Thu 07/21/2016 19:19:51] - FATAL_ERROR: Could not get the IDENTIFY data from the drive... (0x12000004:SF_SG_HOST_BAD_TARGET_ERROR)
[Thu 07/21/2016 19:19:51] - End of Genesis manufacturing log.
[Thu 07/21/2016 19:19:51] - Exiting...


</Log_Body>

<Overall_Summary>
<Start_Time> Thu, 07/21/2016 @ 19:16:50 </Start_Time>
<End_Time> Thu, 07/21/2016 @ 19:19:51 </End_Time>
<Overall_Result> FAIL </Overall_Result>
<Exit_Code> (0x10090012:SF_GENESIS_IDENTIFY_ERROR) </Exit_Code>
</Overall_Summary>

<Environment_Settings>
<Input_Parameters>
argv[1]: -PROCESS_SSD
argv[2]: 2:0:0:0
argv[3]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/FW_PPRO_5_2_2_Release.672199.release.0.mfp
argv[4]: /home/SSD_recovery/SSD/firmware/FW_PPRO_5_2_2_Release.672199.release--0/Configuration_Files/27094.0.driveconfig
argv[5]: 12345
argv[6]: www_123
argv[7]: LOG=/home/SSD_recovery/SSD/firmware/27094.LOG
</Input_Parameters>
<Log_File> /home/SSD_recovery/SSD/firmware/27094.LOG </Log_File>
<Hostname> localhost.localdomain </Hostname>
<Host_IP_Address> 127.0.0.1 </Host_IP_Address>
<Port_Number> 0 </Port_Number>
<Device_Name> /dev/sg0 </Device_Name>
<SF_Genesis_Version> v1.5.21.20110919-fc14-32bit </SF_Genesis_Version>
<SF_Core_Library_Version> v1.7.0.20110919-fc14-32bit </SF_Core_Library_Version>
<SF_OS_Information> Linux 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686 </SF_OS_Information>
</Environment_Settings>

<Post_Processing_Device_Info>
<WWN_OUI> UNKNOWN </WWN_OUI>
<WWN_UniqueID> UNKNOWN </WWN_UniqueID>
<Serial_Number> UNKNOWN </Serial_Number>
<Model_Number> UNKNOWN </Model_Number>
<Firmware_Revision> UNKNOWN </Firmware_Revision>
<ROM_Revision> UNKNOWN </ROM_Revision>
<NAND_Page_Size> UNKNOWN </NAND_Page_Size>
<Number_Of_Chip_Enable> UNKNOWN </Number_Of_Chip_Enable>
<Logical_Sectors> UNKNOWN </Logical_Sectors>
<NAND_ID> UNKNOWN </NAND_ID>
<Flash_Manufacturer> UNKNOWN </Flash_Manufacturer>
<Flash_Device> UNKNOWN </Flash_Device>
</Post_Processing_Device_Info>

</Genesis_Log>

[Thu 07/21/2016 19:19:51] - Overall Result for Device: /dev/sg0 ****** FAIL ******
[/more]

какие конфигурационные настройки нужны в 28214? подскажите пожалуйста, так файла не нашел но попробую изменить другой может получится

понял спасибо ))

Топчусь на одном месте с этим ssd... Кто-нибудь может поделится комплектом под 22868?

Цитата:

romashko1978
Реболдинг обычно не надолго помогает.
В самих микросхемах проблема, как правило.

две недели сутками
полет нормальный
smart моего диска
[more=Читать дальше..]
[ SPCC Solid State Disk (0042500001) ]

01 Raw Read Error Rate 50 95 95 4895722 OK: Значение нормальное
05 Retired Block Count 3 100 100 1 OK: Значение нормальное
09 Power-On Hours Count 0 98 98 1994 OK: Всегда пройдено
0C Device Power Cycle Count 0 100 100 934 OK: Всегда пройдено
AB Program Fail Count 0 100 100 0 OK: Всегда пройдено
AC Erase Fail Count 0 100 100 0 OK: Всегда пройдено
AE Unexpected Power Loss Count 0 0 0 130 OK: Всегда пройдено
B1 Wear Range Delta 0 0 0 99 OK: Всегда пройдено
B5 Program Fail Count 0 100 100 0 OK: Всегда пройдено
B6 Erase Fail Count 0 100 100 0 OK: Всегда пройдено
BB Reported Uncorrectable Errors 0 100 100 0 OK: Всегда пройдено
C2 Temperature 0 30 30 30, 30, 30 OK: Всегда пройдено
C3 On-the-Fly ECC Uncorrectable Error Count 0 120 120 4895722 OK: Всегда пройдено
C4 Reallocation Event Count 3 100 100 1 OK: Значение нормальное
C9 Uncorrectable Soft Read Error Rate 0 120 120 4895722 OK: Всегда пройдено
CC Soft ECC Correction Rate 0 120 120 4895722 OK: Всегда пройдено
E6 Life Curve Status 0 100 100 100 OK: Всегда пройдено
E7 Remaining Drive Life 10 97 97 12884901889 OK: Значение нормальное
E9 Lifetime Compressed Writes (GB) 0 0 0 3194 OK: Всегда пройдено
EA <зависит от поставщика> 0 0 0 3725 OK: Всегда пройдено
F1 Lifetime Writes from Host (GB) 0 0 0 3725 OK: Всегда пройдено
F2 Lifetime Reads from Host (GB) 0 0 0 4381 OK: Всегда пройдено
[/more]

romashko1978
В постоянной работе не показатель для реболдинга, он обычно косячит когда то включают, то выключают, температурные перепады опять приводят к неконтакту.
Но может вам и повезло. Чаще нет.

он изначально грелся сильно
может поэтому и вышел из строя
сейчас температура выше 35 не поднимается

Пока забил на ssd с неизвестными чипами.
Сейчас ковыряю другой на msata. Toshiba THSNS128GMCP 128GB, определяется как 0GB.
Маркировка на контроллере TC58NC5HJ8GSB-01, по команде lsscsi пишит что SandForce.
Стоят 4 чипа памяти TH58TEG8DBHBASC.

Должна подойти одна из конфигураций.
27006 SF-2281-Python TH58TEG8DBHBA8C 121 0E200000
27018 SF-2281-Gold TH58TEG8DBHBA8C 120 0DF94BB0
27030 SF-2281-Toshiba TH58TEG8DBHBA8C 128 0EE7C2B0 КОМПЛЕКТ ПОДОШЕЛ
27118 SF-2281-Toshiba TH58TEG8DBHBA8C 120 0DF94BB0
27275 SF-2281-Toshiba TH58TEG8DBHBA8C 128 0EE7C2B0
27278 SF-2281-Toshiba TH58TEG8DBHBA8C 120 0DF94BB0
27283 SF-2281-Python TH58TEG8DBHBA8C 121 0E200000
27289 SF-2281-Toshiba TH58TEG8DBHBA8C 128 0EE7C2B0

В распакованной 5.2.2 их нет. В распакованной мной 5.8.2, из доступных 3-х лицензий, тоже нет. Был бы при много благодарен, если бы подкинули файлы. Откопал в ранее скачанных архивах.

Обновлено
Подошел комплект 27030.

Теперь вернусь к ssd с неизвестными чипами.

Цитата:

Most probably your ssd have damaged cpu.

I thought its not possible, but thanks anyway. I saw slavaart1990's post before:
Ссылка

I've meet with many custom labeled flash chips before. And I'd like to make a google-docs like database, to help other guys.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SandForce Genesis Utility v1.7.0.01020130612-fc14-32bit
SF_Core Library: v1.7.1.20130612-fc14-32bit

Copyright 2010-2012, LSI Corporation, All Rights Reserved Worldwide.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Wed 07/27/2016 23:20:31] - SF_Genesis has been invoked with the following parameters:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
argv[1]: -READ_FLASH_ID
argv[2]: 1:0:0:0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


[Wed 07/27/2016 23:20:31] - Instructing the operating system to purge any existing cached data for device: '1:0:0:0

после любой команды в генезисе такая ошибка и винт отваливается и lsscsi его не видит.
что не так?

Добавлено:
[more] потом везде в логе соответственно
[Wed 07/27/2016 23:20:31] - Instructing the operating system to purge any existing cached data for device: '1:0:0:0'
[Wed 07/27/2016 23:23:36] - Issuing a discovery command for device: '1:0:0:0'
[Wed 07/27/2016 23:23:41] - Discovery command completed...
[Wed 07/27/2016 23:23:41] - Waiting 5 seconds for the system to settle...
[Wed 07/27/2016 23:23:46] - End of Genesis manufacturing log.
[Wed 07/27/2016 23:23:46] - Exiting...


</Log_Body>

<Overall_Summary>
<Start_Time> Wed, 07/27/2016 @ 23:20:31 </Start_Time>
<End_Time> Wed, 07/27/2016 @ 23:23:46 </End_Time>
<Overall_Result> FAIL </Overall_Result>
<Exit_Code> (ECode: 10090024) </Exit_Code>
</Overall_Summary>

<Environment_Settings>
<Input_Parameters>
argv[1]: -READ_FLASH_ID
argv[2]: 1:0:0:0
</Input_Parameters>
<Log_File> SF_Genesis_Main_Log__Wed_07.27.2016_23.20.31.log </Log_File>
<Hostname> localhost.localdomain </Hostname>
<Host_IP_Address> 127.0.0.1 </Host_IP_Address>
<Port_Number> UNKNOWN </Port_Number>
<Device_Name> UNKNOWN </Device_Name>
<SF_Genesis_Version> v1.7.0.01020130612-fc14-32bit </SF_Genesis_Version>
<SF_Core_Library_Version> v1.7.1.20130612-fc14-32bit </SF_Core_Library_Version>
<SF_OS_Information> Linux 3.3.0-4.fc16.i686 #1 SMP Tue Mar 20 18:45:14 UTC 2012 i686 </SF_OS_Information>
</Environment_Settings>

<Post_Processing_Device_Info>
<WWN_OUI> UNKNOWN </WWN_OUI>
<WWN_UniqueID> UNKNOWN </WWN_UniqueID>
<Serial_Number> UNKNOWN </Serial_Number>
<Model_Number> UNKNOWN </Model_Number>
<Firmware_Revision> UNKNOWN </Firmware_Revision>
<ROM_Revision> UNKNOWN </ROM_Revision>
<NAND_Page_Size> UNKNOWN </NAND_Page_Size>
<Number_Of_Chip_Enable> UNKNOWN </Number_Of_Chip_Enable>
<Logical_Sectors> UNKNOWN </Logical_Sectors>
<NAND_ID> UNKNOWN </NAND_ID>
<Flash_Manufacturer> UNKNOWN </Flash_Manufacturer>
<Flash_Device> UNKNOWN </Flash_Device>
</Post_Processing_Device_Info>

</Genesis_Log>

[Wed 07/27/2016 23:23:46] - Overall Result for Device: ****** FAIL ****** [/more]

belgien
Не вижу argv[3], это log.

Цитата:

 -READ_FLASH_ID : Collect manufacturer identifying information about flash devices .    
./SF_Genesis -READ_FLASH_ID [DEVICE] [LOG=FILENAME]

Из двух ссд, которые ковырял в последнее время, команда так же не проходит. И после этого сам ссд висит. Помогает передернуть питание.

даже если ссд передерну его не видно lsscsi не видит. а лог в корне папки в которой сама прога создается,я это копировал из лога

Добавлено:
прога создаст даже если не укажешь


Добавлено:
попробовал еще пару раз, лог не создался, даже при том ,что прописал куда.
не пойму ,проблема в проге ,федоре, или во мне, но не проходит ни какая команда отваливается и всё

Добавлено:
а нет)) перезапустил диспетчер файлов и появились оба))

Добавлено:
-FIND_SF_DRIVES -ALL ничего не находит хоть lsscsi и видит

Была такая проблема с потерей SSD после любой команды.
Помогла смена железа. то есть установил Fedora на другой компьютер.

А нет другого (((

Добрый день.
Не подскажете, какой комплект использовать
для VERTEX-2 50GB SF-1222 с микросхемами памяти IF16G2GAGA 01103 73323123.002?
Перебпробовал все на емкость 40-50GB - Test Fail

sashalogout
А с чего вы взяли, что в файле с лицензиями есть конфиг под вашу память?

[more] Всем доброго времени суток. Прошу помощи в восстановлении SSD.

История диска (для общей статистики):
Вначале этот диск поставил на рабочий ноут: отваливания по 10 раз в сутки. После обновлений 3 года назад лаги пропали. Потом ноут пришлось утилизировать в силу своей старости(слабости), а SSD установил в стационарный домашний ПК. Поставил на него Win7 со всеми примочками для недискоубийства. Через некоторое время система испортила мне все нервы посредством непредсказуемых BSOD (в это время писал диссер). Перенес раздел на старенький IDE диск и радовался жизни. На SSD вначале собрал Gentoo, потом ставил несколько дебианообразных дистрибутивов, потом форматнул начисто и поставил Debian. После работы без единой ошибки и бага этого SSD, во время apt upgrade забыл отключить убунтовские репы и в итоге убил систему. Два месяца назад поставил свежую убунту, все работало замечательно (на всех линукс дистрибутивах своп был отключен, tmp в tmpfs(ram) и естественно вся вся вся времянка в ram, ext4 с блочной записью, раздел выровнен на 512). Т.к. мною было замечено что в Linux диск не сбоит и по слухам SSD будет в крайнем случае всегда доступен для readonly, я совершил самую большую ошибку в моей жизни - скинул все важное на него! Неделю назад БаЦ! Отключилось электричество. Ничего не подозревая я включаю комп... убунта взлетает за 2 секунды как обычно. Через примерно 10минут все повисло - нажимаю reset. Жду... на плате SSD загорается красный светодиод (fault) на 5-10 секунд. И убунта снова загрузилась. На этот раз проработала минуты две и... reset. Только на этот раз диск не определяется биосом, красный светодиод не горит, только зеленый (power).

Вот уже неделю пытаюсь что-то с этим сделать. Разумеется, очень важно не потерять данные на нем.

По делу:

Сам диск:
OCZ Vertex (VTX3MI-25SAT3-120G)
Процессор: SF-2281VB1-SDC
Память: TH58TAG6D2FBA49

Все что смог раздобыть в сети по данному вопросу:

Номер конфигурации нашел в таблице выложенной здесь:
22006    SF-2281    SF-2281 120GB Toshiba32 hMLC BGA 16xTH58TAG6D2FBA49

Лицензия есть (в 3 найденных в сети файлах *.lic): <configuration_id id="22006" />

Набор SF_1.7:
SF_ConfigurationManager
SF_FieldUpdater
SF_Genesis
SF_GenesisDashboard
SF_OEM_PackageManager

Система: Fedora (RFRemix-17-i686-Live-LXDE.iso)
Дополнительные пакеты:
lsscsi-0.23-2.fc14.i686.rpm
mailx-12.5-1.fc14.i686.rpm
sg3_utils-1.29-1.i386.rpm
smartmontools-5.40-5.fc14.i686.rpm

Припаял UART, на 115200 получил следующий выхлоп:

[ROM] PORRST
[ROM] Chip ID 0x200026BB
*** ROM Rev 20D Dec 20 2010 Build 288571 ***
[ROM] Load CRP
*** CRP Rev 101 Oct 11 2011 Build 345997 ***
[ROM] Load FWR
<далее нечитабельно>

При подключении перемычки (J5):

[ROM] PORRST
[ROM] Chip ID 0x200026BB
*** ROM Rev 20D Dec 20 2010 Build 288571 ***
[ROM] Force Download: waiting for Download Microcode Command...
[ROM] Waiting for Link to come up...
[ROM] Link is UP.
[ROM] Hard Reset ===> Link is Down.
[ROM] PHY Ready
[ROM] Sig Sent
[ROM] Undec Cmd 0xec
[ROM] Undec Cmd 0xe1
[ROM] Undec Cmd 0xef
[ROM] Undec Cmd 0xb0
[ROM] Undec Cmd 0xec
<далее нечитабельно>

Остается дело за прошивкой. На данный момент нашел следующее:
1) На этом форуме 5.2.2: http://forum.ru-board.com/topic.cgi?forum=84&topic=4797&start=0&limit=1&m=4#1
Я так полагаю там нет моей конфигурации 22006 и файла *.dfp
2) Есть файл FW_SF-2000_MP_5-0-7_Client.dfp
3) Есть файл FW_SF-2000_MP_5-0-B_Client.dfp
4) Есть что-то здесь (но качать за золото): http://chomikuj.pl/wibi/Dysk+SSD-Naprawa*2cRemont*2cFirmware/ssd

Найденные мной торрент раздачи не работают.
Меня интересует (как мне кажется) версия FW_PPRO_5_8_2_Release.906190.release, которую везде разрекламировали, но где качать непонятно Возможно в этом пакете есть конфигурация для моего диска.

Вот собственно такая проблема: Как НЕ ПОВРЕДИТЬ раздел на диске при прошивке?
Если это невозможно, то перепаивать я его не буду Похороню данные, но диск все-же однозначно желаю восстановить из спортивного интереса.

Прошу помочь разобраться с этим OCZ, возможно я неправильно понимаю процесс перепрошивки (в т.ч. процесс подготовки FW). Мне в конечном итоге нужен полный пакет FW_PPRO_5_8_2********* (ну или другой версии) в котором присутствует конфигурация 22006 или *.dfp из которого я буду подготавливать эту конфигурацию? В пакете должны быть файл *.mfp, *.ffp? Или они создаются отдельно? Есть ли способ узнать что за прошивка залита в него на данный момент? И зачем там JTAG+UART контакты?
Можете кто-нибудь поделиться пакетами и подсказать что делать со всем этим добром?

Извиняюсь за длинный пост и много вопросов и ошибки/опечатки, т.к. в 3 ночи писал.

Заранее огромное спасибо!
[/more]

qwinnt

Забудьте про данные.
Во первых, данная ветка посвящена ремонту SSD на SandForce посредством запуска на последнем заводского техпроцесса, который, естественно, уничтожит всю вашу информацию, причем не единожды. Этот момент я поясню далее.

Во вторых, информация на SSD с контроллером SF2281 шифруется по алгоритму AES-128. Т.е. вам не поможет даже распаивание SSD и вычитывание дампов с последующей ручной сборкой транслятора.

Если же вы запустите техпроцесс, или как вы говорите прошивку, то в этом случае заново сформируются ключи шифрования, транслятор (система перевода физических координат PBA в логические LBA) и кроме того, будут отформатированы микросхемы Nand Flash. Любое из этих трех действий уже ведет к потере вашей информации. Все это, конечно, очень упрощенно, но в общих чертах верно. На данный момент (по слухам), есть лишь несколько человек, которые берутся за восстановление данных с SSD на SanForce с "упавшей" прошивкой, но работа крайне сложная, долгая, баснословно дорогая и нет гарантии, что все получится. В общем, примите мои соболезнования...

Что же касается ремонта, то в ветке уже 100500 раз все рассказали, в том числе и где взять все для этого необходимое.

mars070
Спасибо Вам за пояснение и соболезнования. Придется инициировать заводской техпроцесс. По поводу 100500 раз я видел, поиском шерстил всю ветку. Большинство ссылок на пакеты битые. Поэтому решил написать здесь, может у кого есть этот пакет. (FW_PPRO_5_8_2_Release.906190.release). Ну а в целом с точки зрения реанимации я на верном пути? (то что я ищу именно этот пакет и *.dfp файл для создания конфигурации и самого ПО)

qwinnt
Ищите у китайцев. У них этого добра на всех облаках валом. А насчет верного пути, так простите, какие тут еще могут быть вопросы, если в шапке есть пошаговая инструкция?

Хорошо. Всю неделю искал везде, в том числе у китайцев - ничего вразумительного, но видимо я туговат на ум и недели мне мало. Есть подозрение что меня провайдер специально не пускает именно на те сайты, где есть ответы Сейчас посмотрел на китайских поисковиках - 1 ссылка на форум, где просто выложены логи.
Искал так http://pan.haoii123.com/k/FW_PPRO_5_8_2.

У меня есть папка с таким содержимым:

Configuration_Files
FW_PPRO_5_8_2_Release.906190.release.0.ffp
FW_PPRO_5_8_2_Release.906190.release.0.mfp
VIC_Files

Но в ней нет моей конфигурации. И нет как видите *.dfp.

Цитата:

qwinnt OCZ Vertex (VTX3MI-25SAT3-120G)
Процессор: SF-2281VB1-SDC
Память: TH58TAG6D2FBA49

Все что смог раздобыть в сети по данному вопросу:

Номер конфигурации нашел в таблице выложенной здесь:
22006 SF-2281 SF-2281 120GB Toshiba32 hMLC BGA 16xTH58TAG6D2FBA49

22006_582.rar

Добавлено:

Цитата:

sashalogout Не подскажете, какой комплект использовать
для VERTEX-2 50GB SF-1222 с микросхемами памяти IF16G2GAGA 01103 73323123.002?

надо пробовать любой похожий и смотреть -READ_FLASH_ID:

Цитата:

[Sun 11/29/2015 13:46:20] - 16 Flash IDs
[Sun 11/29/2015 13:46:20] - Bus Count: 2
[Sun 11/29/2015 13:46:20] - Chip Enable Count: 2
[Sun 11/29/2015 13:46:20] - Lane Count: 4
[Sun 11/29/2015 13:46:20] -
[Sun 11/29/2015 13:46:20] - Bus Chip Enable Lane Flash ID
[Sun 11/29/2015 13:46:20] - ------------------------------------------------
[Sun 11/29/2015 13:46:20] - 0 0 0 2C 84 64 3C A5 00 00 00
[Sun 11/29/2015 13:46:20] - 0 0 1 2C 84 64 3C A5 00 00 00

или просто гуглом...




Цитата:

A642=Intel,64Gbit (8KP),JS29F64G08AAME1-ES, 89,88,04,4B,A9,00

Цитата:

12522 SF-1200 80GB Intel25 MLC TSOP 12xJS29F64G08AAME1
12563 SF-1200 50GB Intel25 MLC TSOP 8xJS29F64G08AAME1
...