N40P full OK with loader but not alone....
February 23rd, 2007, 9:28
Hello everybody... this thing is driving me mad : I was able to make a N40P work again ( ok... not fully at this stage... 
) by repairing the SA and rewriting good modules.... but the drive is operational ONLY starting in safe mode with loader. If you do this, the drive recalibrates, is correctly recognised by BIOS, MHDD works, you can use it normally. If you give power to the drive as normal , the drive is recognised with his factory alias and obviously no SA operation is possible.
As - if you start with loader - all modules are OK, what could it be ?
I have also tried PCB exchange with same code form another IDENTICAL N40P (same identifier, same PCB, same !!! - only production date is slightly different).
Any suggestions ? Data inside is not important and already gone (G- and P-list cleared).
Thanks.
) by repairing the SA and rewriting good modules.... but the drive is operational ONLY starting in safe mode with loader. If you do this, the drive recalibrates, is correctly recognised by BIOS, MHDD works, you can use it normally. If you give power to the drive as normal , the drive is recognised with his factory alias and obviously no SA operation is possible.
As - if you start with loader - all modules are OK, what could it be ?
I have also tried PCB exchange with same code form another IDENTICAL N40P (same identifier, same PCB, same !!! - only production date is slightly different).
Any suggestions ? Data inside is not important and already gone (G- and P-list cleared).
Thanks.
February 23rd, 2007, 10:42
Hi BlackST,
can you post the contents(HEX) of 48h.
Also check Overlays for trash
can you post the contents(HEX) of 48h.
Also check Overlays for trash
February 23rd, 2007, 11:26
Thanks Samo, I don't have te exact OVL so I could not restore them at the moment, only a loader that work.
The drive is 6K040L0510205 AAA , KMGA , microcode NAR61HA0 production 03aug2005. Take a look if you have groups or modules. I'll post the content of 48h.
Many many thanks.
The drive is 6K040L0510205 AAA , KMGA , microcode NAR61HA0 production 03aug2005. Take a look if you have groups or modules. I'll post the content of 48h.
Many many thanks.
February 23rd, 2007, 11:57
This is the content of the module in HEX
4B 31 30 46 59 58 59 47 1D 00 50 5A D7 03 10 0C 02 00 00 69 08 03 17 34 00 00 00 00 58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4E 32 32 34 00 D8 01 50 36 35 31 41 00 30 32 41 00 00 00 00 00 00 00 00 00 00 00 30 35 41 00 4B 43 47 41 00 40 10 04 00 CB D3 6A BC 8E 00 8E 00 00 00 30 35 41 00 00 00 00 00 00 00 00 00 00 00 00 00 42 E8 F0 42 00 00 00 36 4B 30 34 30 4C 30 35 31 30 32 30 35 43 75 4A 00 00 00 00 00 00 4E 41 52 36 31 48 41 30 FF 3F 10 00 3F 00 00 00 00 00 00 00 00 00 CE 00 01 00 07 00 80 2D C9 04 50 47 54 41 50 4F 47 38 30 33 00 00 00 00 00 00 36 4B 30 34 30 4C 31 00 00 00 02 00 30 44 69 61 6D 6F 6E 64 4D 61 78 20 50 6C 75 73 20 38 00 00 00 00 00 00 00 00 41 54 41 2F 31 33 33 20 48 44 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 34 30 47 42 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 36 34 37 2D 37 39 30 00 00 00 00 00 00 00 00 00 00 00 00 00 69 08 02 10 04 69 08 03 17 1A 69 08 03 17 1D 00 00 00 00 00 00 00 00 00 00 00 66 00 00 00 00 00 00 00 50 19 41 32 47 4B 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 38 2E 34 35 41 3D
And in ASCII :
K10FYXYG PZ× i4 X N224 ØP651A 02A 05A KCGA @ ËÓj¼Ž Ž 05A BèðB 6K040L0510205CuJ NAR61HA0ÿ? ? Î €-ÉPGTAPOG803 6K040L1 0DiamondMax Plus 8 ATA/133 HDD 40GB 647-790 iii f PA2GKA Q8.45A=
4B 31 30 46 59 58 59 47 1D 00 50 5A D7 03 10 0C 02 00 00 69 08 03 17 34 00 00 00 00 58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4E 32 32 34 00 D8 01 50 36 35 31 41 00 30 32 41 00 00 00 00 00 00 00 00 00 00 00 30 35 41 00 4B 43 47 41 00 40 10 04 00 CB D3 6A BC 8E 00 8E 00 00 00 30 35 41 00 00 00 00 00 00 00 00 00 00 00 00 00 42 E8 F0 42 00 00 00 36 4B 30 34 30 4C 30 35 31 30 32 30 35 43 75 4A 00 00 00 00 00 00 4E 41 52 36 31 48 41 30 FF 3F 10 00 3F 00 00 00 00 00 00 00 00 00 CE 00 01 00 07 00 80 2D C9 04 50 47 54 41 50 4F 47 38 30 33 00 00 00 00 00 00 36 4B 30 34 30 4C 31 00 00 00 02 00 30 44 69 61 6D 6F 6E 64 4D 61 78 20 50 6C 75 73 20 38 00 00 00 00 00 00 00 00 41 54 41 2F 31 33 33 20 48 44 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 34 30 47 42 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 36 34 37 2D 37 39 30 00 00 00 00 00 00 00 00 00 00 00 00 00 69 08 02 10 04 69 08 03 17 1A 69 08 03 17 1D 00 00 00 00 00 00 00 00 00 00 00 66 00 00 00 00 00 00 00 50 19 41 32 47 4B 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 38 2E 34 35 41 3D
And in ASCII :
K10FYXYG PZ× i4 X N224 ØP651A 02A 05A KCGA @ ËÓj¼Ž Ž 05A BèðB 6K040L0510205CuJ NAR61HA0ÿ? ? Î €-ÉPGTAPOG803 6K040L1 0DiamondMax Plus 8 ATA/133 HDD 40GB 647-790 iii f PA2GKA Q8.45A=
February 23rd, 2007, 16:07
This is a RoHS drive....
If you have checked it with known good PCB and the situation is the same, at your place i would check the overlays for trash, also all the translator stuff, DISK ... i.e. everything that is loaded at start up and is critical for drive operation. Do not check only C.S. but contetnt too. Also in those drive G-list may not be this you expect it to be.
Have you done regen translator?
What is the c.s. of the OVL for the drive you are looking for?
If you have checked it with known good PCB and the situation is the same, at your place i would check the overlays for trash, also all the translator stuff, DISK ... i.e. everything that is loaded at start up and is critical for drive operation. Do not check only C.S. but contetnt too. Also in those drive G-list may not be this you expect it to be.
Have you done regen translator?
What is the c.s. of the OVL for the drive you are looking for?
February 23rd, 2007, 18:36
Right it's RoHS compliant. I have already tried translator regeneration, clearing P- and G-list and translator regen.... nothing.
Probably there's a problem in the overlays, an identical (or close as possible) drive is needed to get the groups and write into the defective one. I am close to the solution, because HD unparks the heads, read some of the modules and then hangs (does NOT complete recalibration). After a few seconds READY is set but every attempt on accessing the drive in this state returns ABRT - module tables are not loaded! Then, sending the LDR, the drive COMPLETE the remainder of the RECALIBRATION and is fully functional. So, the problem at 99% is on the loadable part of the FW or can't load module table.
Which modules / groups are involved ?
Hint : scanning the system area (groups) seems that some blocks are a little slower in reading, this change clearing the P- and G-list.
Can't be a head stack / preamp problem because when functional the drive has normal operation speed and MHDD works.
After starting with LDR and initializing from the SA the drive is fully functional.
The closest drive I found is a 6K040L01 (01 not 05!!) AAA - KMGA same microcode NAR61HA0 (the loader built with that drive works) PCB A2GKA.
Do you think "cloning" this drive into the defective except the specific modules like SRV, zone table and DISK will work ?
This thing is driving me mad, at this point I MUST be the winner....not the drive it's just for experimental purposal.
Thanks for your attention.
Probably there's a problem in the overlays, an identical (or close as possible) drive is needed to get the groups and write into the defective one. I am close to the solution, because HD unparks the heads, read some of the modules and then hangs (does NOT complete recalibration). After a few seconds READY is set but every attempt on accessing the drive in this state returns ABRT - module tables are not loaded! Then, sending the LDR, the drive COMPLETE the remainder of the RECALIBRATION and is fully functional. So, the problem at 99% is on the loadable part of the FW or can't load module table.
Which modules / groups are involved ?
Hint : scanning the system area (groups) seems that some blocks are a little slower in reading, this change clearing the P- and G-list.
Can't be a head stack / preamp problem because when functional the drive has normal operation speed and MHDD works.
After starting with LDR and initializing from the SA the drive is fully functional.
The closest drive I found is a 6K040L01 (01 not 05!!) AAA - KMGA same microcode NAR61HA0 (the loader built with that drive works) PCB A2GKA.
Do you think "cloning" this drive into the defective except the specific modules like SRV, zone table and DISK will work ?
This thing is driving me mad, at this point I MUST be the winner....not the drive
it's just for experimental purposal.
Thanks for your attention.
February 23rd, 2007, 19:15
Dear BlackST,
getting mad with drives is not a good idea
People that get mad start to think less....
Imho you still did not need nothing to write in the drive. You must figure out the problem first.
Just do me a favour. Pay attention to the underlined words up and here!
Can I see the log of SA?
getting mad with drives is not a good idea
People that get mad start to think less....
Imho you still did not need nothing to write in the drive. You must figure out the problem first.
Just do me a favour. Pay attention to the underlined words up and here!
Can I see the log of SA?
February 24th, 2007, 8:25
Hi,
I would check things in DATA copy 1 and CODE copy 1 as well, there are some drives running from copy 1 by default.
Are U sure the PCB is the original? Or it might have been swapped by somebody else before. This means the ROM code on the PCB might be incompatible too.
Have U tried to create an LDR from the patient drive and starting with that one?
pepe
I would check things in DATA copy 1 and CODE copy 1 as well, there are some drives running from copy 1 by default.
Are U sure the PCB is the original? Or it might have been swapped by somebody else before. This means the ROM code on the PCB might be incompatible too.
Have U tried to create an LDR from the patient drive and starting with that one?
pepe
Powered by phpBB © phpBB Group.