Hi there!
I need some help
The faulty drive is a WD20EARX-00PASB0. The drive does not spins up. After i changed the PCB and transferred the rom the drive spins up, but clicks, and spins down.
With donor WD20EARX-00PASB0 i did a hot swap, and i read some firmware modules, but i cannot read all. Now i know the firmware map (0001.rpm) is not the same of the faulty drive, and the hot swap drive, thats why i cannot read all of the modules.
I made a hybrid firmware of hot swap and the patient drive, and i uploaded it to a patient drive. Now the patient drive recognized fine, but i cannot access to data.
With WDR i cleared the translator and the translator regeneration finished with this error message: "3C15 =FMT_PLIST_PSN_OUT OF RANGE"
When i upload the entire firmware of the hot swap drive, the translator regeneration could finish with no error.
Do anybody have any deal how to solve this problem?
Here are the patient and the hot swap drive's firmwares in one archive file: http://www68.zippyshare.com/v/19924685/file.html
The firmware was read out with Atola Insight.
Thanks for any help.

Hello,
Delete the unknown defects from P-list, then regenerate translator.
Don't delete the correct defect, if you delete the correct defect then you lose the data.

Thank you waqas I'm glad to see here!
How can i find the unknown defect from the p-list? Is it possible with "Edit P-list" button under the "Defect list" menu??

Thank you ismlamm for your answer.
The drive could recognize itself with the correct capacity, but i cannot access to any sectors with WDR or Atola Insight. Thats why i cannot make an image of the drive. I think there is some problem with the head zones map, and with the p-list too.

Hello,
It is very difficult to solve this error manually.
We have made this function in Sediv after a lot of research, and i think it is available in our trial version.
Try to find the non valid LBA (CHS) range in p-list and delete it. but first back up the original p-list module (33, 31).

http://www.sediv.net/forums/viewtopic.p ... 46ee5#p404

http://www.sediv.net/index.php?view=downloads

Regards
Waqas Ali

I think i have to buy the Sediv full version, because the trial version does not write anything to disk

To me it looks like this recovery is going directly to another level of complexity.

Maybe I didn't understand correctly what you are trying to do, but this will not work.
You should have extracted the defect list from original drive as thoroughly as possible and then reassemble it manually. Now you have a defect list from irrelevant hard drive, which will not help anyhow, as there should be no extrinsic records.

General answer is to handle them manually, but how do you know that some records are incorrect? If you have taken P-list from another hard drive, it will be of no use.

P.S.
Also doing a hot swap on Sadle G6 drives is unsafe - this can result in getting SA erased partially.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.

Dmitri

SIR,

can we say, hot swap will not work

Hello Dmitri!
The P-list and G-list and the translator are the original on the patient drive, but i cannot acces to the LBA sectors. When i want to regenerate the translator the WDR gives an error message : "3C15 =FMT_PLIST_PSN_OUT OF RANGE"
I have only overwrite only modules that i cannot read out from the patient drive. Now the drive identifiable, but i can't regenerate the translator. I think the head zone map is corrupt, because it's overwrited from the hot swap drive.

Hello,
What is head zone map ?

the p-list PSN out of range means that p-list has defect greater then its LBA, cylinder.

Regards
Waqas Ali

Hot swap doesn't work because DIR modules are different, but you can try to read the entire regions or first to read the original DIR , than load it (dir load from file option) and than read all modules.

P.S. By the way , not only DIR modules are different but also addaptives, zone tables, ARCO settings, etc. , so your drive could start working with your "hybrid" firmware only after running successfully ARCO and IBI tests... The data is gone of course.

Which ones then?

I didn't get your question, could you please restate it more precisely?

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.

Here are the modules list that have been overwrite from the donor drive:
mod0091
mod0093
mod0094
mod0096
mod0097
mod0098
mod0099
mod009A
mod009C
mod00A0
mod00A2
mod00A5
mod00A9
mod00AA
mod00AC
mod00AE
mod00B1
mod00B2
mod00B8
mod00B9
mod00BA
mod00BB
mod00BC
mod00BD
mod00BE
mod00BF
mod00C2
mod00C3
mod00C4
mod00C5
mod00C6
mod00C7
mod00C8
mod00C9
mod00CA
mod00CC
mod00CE
mod00CF
mod00D0
mod00D3
mod00D4
mod00D8
mod00D9
mod00DC
mod00E6
mod00E7
mod00E8
mod00E9
mod00EA
mod00EB
mod00EC
mod00ED
mod00EE
mod00F7
mod00FC
mod00FD
mod00FE
mod0128
mod0153
mod1000
mod1001
mod1002
mod1003
mod1004
mod1005
mod1007
mod1008
mod1009
mod100A
mod100B
mod100C
mod100D
mod100E
mod1100
mod1101
mod1102
mod1121
mod120F
mod1213
mod121F
mod1400
mod1430
mod1500
mod1501
mod1502
mod1503
mod1504
mod1505
mod1506
mod1507
mod150C
mod150D
mod150E
mod150F
mod1610
mod1800
mod1801
mod1802
mod1803
mod1804
mod2000
mod2001
mod2002
mod2003
mod2004
mod2005
mod2006
mod2007
mod2010
mod2011
mod2012
mod2013
mod2014
mod2015
mod2016
mod2017
mod2020
mod2021
mod2022
mod2023
mod2024
mod2025
mod2026
mod2027
mod2030
mod2031
mod2032
mod2033
mod2034
mod2035
mod2036
mod2037
mod2040
mod2041
mod2042
mod2043
mod2044
mod2045
mod2046
mod2047
mod2050
mod2051
mod2052
mod2053
mod2054
mod2055
mod2056
mod2057
mod2060
mod2061
mod2062
mod2063
mod2064
mod2065
mod2066
mod2067
mod2070
mod2071
mod2072
mod2073
mod2074
mod2075
mod2076
mod2077
mod2802
mod280A
mod2900
mod2901
mod2903
mod2904
mod2906
mod2908
mod2909
mod290A
mod2A02
mod2B00
mod2B11
mod2F00
mod3301
mod3302
mod3303
mod3304
mod3305
mod3307
mod3400
mod3401
mod3405
mod3406
mod3407
mod3408
mod3416
mod3417
mod3421
mod3422
mod3423
mod34E7
mod3500
mod3501
mod3502
mod3503
mod3504
mod3506
mod3511
mod3604
mod3605
mod3801
mod3802
mod3C00
mod3C10
mod3C11
mod3C12
mod3C13
mod3C14
mod3C15
mod3C20
mod3C21
mod3C22
mod3C23
mod3C24
mod3C25
mod3E00
mod3F00
mod3F01
mod3F03
mod8000
mod8001
mod8002
mod8003
mod8004
mod8005
mod8006
mod8007
mod8008
mod8009
mod800A
mod800B
mod800C
mod800D
mod800E
mod800F
mod8010
mod8011
mod8012
mod8013
mod8014
mod8015
mod8016
mod8017
mod8018
mod8019
mod801A
mod801B
mod801C
mod801D
mod801E
mod801F
mod8020
mod8021
mod8022
mod8023
mod8024
mod8025
mod8026
mod8027
mod8028
mod8029
mod802A
mod802B
mod802C
mod802D
mod802E
mod802F
mod8030
mod8031
mod8032
mod8033
mod8034
mod8035
mod8036
mod8037
mod8038
mod8039
mod803A
mod803B
mod803C
mod803D
mod803E
mod803F
mod8040
mod8041
mod8042
mod8043
mod8044
mod8045
mod8046
mod8047
mod8048
mod8049
mod804A
mod804B
mod804C
mod804D
mod804E
mod804F
mod8050
mod8051
mod8052
mod8053
mod8054
mod8055
mod8056
mod8057
mod8058
mod8059
mod805A
mod805B
mod805C
mod805D
mod805E
mod805F
mod8060
mod8061
mod8062
mod8063
mod8064
mod8065
mod8066
mod8067
mod8068
mod8069
mod806A
mod806B
mod806C
mod806D
mod806E
mod806F
mod80FC
mod80FE
mod80FF
mod8FFC
mod8FFD
mod8FFE

With such list of transplanted modules everything should be OK and working.
I'm out of things, which can be guessed blindly, without seeing the drive, however it's possible that either some mistake crept into your previous actions or an extra voodoo dance is required to reanimate the drive now.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.