Seagate barracuda Antipending solution

[kamyabi.h]

Special thanks dear Igor, it Worked for me

[mojimorady]

Dear guru
hi
is there any solution to repair H.D.D which suffers from pending problem ?
i mean a solution that can repair the H.D.D to use after that .( recovering data is not important )
best regards

[RescueDRL@gmail.com]

Hi, I have this same problem after swapping controller card due to blown chips.
There was NO ROM chip to transplant, but I was able to create Loader with this
method.

However, in DE, the Utility check box is NOT checkable! It will not accept it.

What now?

-Drew
=================================================================

[Takanashi_Hina]

Dear guru
hi
is there any solution to repair H.D.D which suffers from pending problem ?
i mean a solution that can repair the H.D.D to use after that .( recovering data is not important )
best regards

Not "safe" to do if you want to recover the data, but it still works most of the time;

http://malthus.mooo.com/viewtopic.php?f=83&t=175

T>T4E

and

T>N50,,22

Only try this when you already have all the data and you just need the drive. Otherwise use PC3K UDMA load from Loader as described on the start of this topic.

[Takanashi_Hina]

Hi, I have this same problem after swapping controller card due to blown chips.
There was NO ROM chip to transplant, but I was able to create Loader with this
method.

However, in DE, the Utility check box is NOT checkable! It will not accept it.

What now?

-Drew
=================================================================

Can you post a terminal LOG of the drive powering up with the "compatible" PCB ?
Maybe ROM version on your PCB is not compatible with the app code ?

[RescueDRL@gmail.com]

Hi, thanks for your response. I left the drive plugged into PC3K
overnight. When I started the Seagate utility to display the
Terminal errors, the drive instantly initialized fast, and NO errors
were seen on the Terminal screen!

So, I left that utility and went immediately to Data Extractor and
was shown a proper directory tree! (before, the tree was incomplete
and incorrect, possibly a prior installation?)

I am now copying the necessary files for the data recovery and very happy...

BTW, the Donor was an exact match, formware, datecode, everything.

Lucky? What happened to the Patient drive with the Donor controller
card to "heal" overnight?

Recall, this is one of those controllers with no separate ROM chip.
I did not have to apply a loader.

-Drew
===================================================================

[Takanashi_Hina]

Hi, thanks for your response. I left the drive plugged into PC3K
overnight. When I started the Seagate utility to display the
Terminal errors, the drive instantly initialized fast, and NO errors
were seen on the Terminal screen!

So, I left that utility and went immediately to Data Extractor and
was shown a proper directory tree! (before, the tree was incomplete
and incorrect, possibly a prior installation?)

I am now copying the necessary files for the data recovery and very happy...

BTW, the Donor was an exact match, formware, datecode, everything.

Lucky? What happened to the Patient drive with the Donor controller
card to "heal" overnight?

Recall, this is one of those controllers with no separate ROM chip.
I did not have to apply a loader.

-Drew
===================================================================

Well, i guess that you can consider ourself lucky !!!
Glad that you have all the data back.
Regarding your question about how the drive was able to "heal" itself ... well, i don't have enought data to come to any conclusions. Maybe some re-location happened, or the temperature of the drive working overnight might have changed something, etc, etc ....
Right now just be glad that you were able to recover the data !!!

[RescueDRL@gmail.com]

Update: After I copied the files I wanted, I powered down restarted the Seagate utility on PC3K.
The problem has returned! - the drives takes a few seconds to initialize now and this Terminal log:
----------------------------------------------------------------------------------------------------
Niwot: 110e7c19 18 110e7c19.0.000 0627 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001b

CE Log ErrCode=43 LBA=110e7c19 Type=5 Add To Pending 110e7c19
AT Er 00 Nwt Er 43 RdWr 12640.00.001c
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1a 18 110e7c1a.0.000 0626 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001c

CE Log ErrCode=43 LBA=110e7c1a Type=5 Add To Pending 110e7c1a
AT Er 00 Nwt Er 43 RdWr 12640.00.001d
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1b 18 110e7c1b.0.000 0625 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001d

CE Log ErrCode=43 LBA=110e7c1b Type=5 Add To Pending 110e7c1b
AT Er 00 Nwt Er 43 RdWr 12640.00.001e
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1c 18 110e7c1c.0.000 0624 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001e

CE Log ErrCode=43 LBA=110e7c1c Type=5 Add To Pending 110e7c1c
AT Er 00 Nwt Er 43 RdWr 12640.00.001f
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1d 18 110e7c1d.0.000 0623 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001f

CE Log ErrCode=43 LBA=110e7c1d Type=5 Add To Pending 110e7c1d
AT Er 00 Nwt Er 43 RdWr 12640.00.0020
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1e 18 110e7c1e.0.000 0622 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.0020

CE Log ErrCode=43 LBA=110e7c1e Type=5 Add To Pending 110e7c1e
Eng Rev = .068
Compat/Hardware = .0T9
NHPLUS2HD - 1_Disk 3.AHC 05-14-08_16:44 AHA,NP_1D_2H_S,3A
CERT Rev = .03U
NONE
Mask Rom Rev = S-1N
Orig Code = AHZ3A0 NHAWK_NP_3A0.068.03U
AT Er 00 Nwt Er 43 RdWr 12640.00.0021
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1f 18 110e7c1f.0.000 0621 1841 2699 0000 ca96a6
Eng Rev = .068
Compat/Hardware = .0T9
NHPLUS2HD - 1_Disk 3.AHC 05-14-08_16:44 AHA,NP_1D_2H_S,3A
CERT Rev = .03U
NONE
Mask Rom Rev = S-1N
Orig Code = AHZ3A0 NHAWK_NP_3A0.068.03U
--------------------etc....-------------------------------------------------------------------

Comments?? (I would like to actually image this drive now in DE)

-Drew
===============================================================================

[Takanashi_Hina]

Update: After I copied the files I wanted, I powered down restarted the Seagate utility on PC3K.
The problem has returned! - the drives takes a few seconds to initialize now and this Terminal log:
----------------------------------------------------------------------------------------------------
Niwot: 110e7c19 18 110e7c19.0.000 0627 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001b

CE Log ErrCode=43 LBA=110e7c19 Type=5 Add To Pending 110e7c19
AT Er 00 Nwt Er 43 RdWr 12640.00.001c
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1a 18 110e7c1a.0.000 0626 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001c

CE Log ErrCode=43 LBA=110e7c1a Type=5 Add To Pending 110e7c1a
AT Er 00 Nwt Er 43 RdWr 12640.00.001d
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1b 18 110e7c1b.0.000 0625 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001d

CE Log ErrCode=43 LBA=110e7c1b Type=5 Add To Pending 110e7c1b
AT Er 00 Nwt Er 43 RdWr 12640.00.001e
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1c 18 110e7c1c.0.000 0624 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001e

CE Log ErrCode=43 LBA=110e7c1c Type=5 Add To Pending 110e7c1c
AT Er 00 Nwt Er 43 RdWr 12640.00.001f
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1d 18 110e7c1d.0.000 0623 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.001f

CE Log ErrCode=43 LBA=110e7c1d Type=5 Add To Pending 110e7c1d
AT Er 00 Nwt Er 43 RdWr 12640.00.0020
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1e 18 110e7c1e.0.000 0622 1841 2699 0000 ca96a6
DiskAccess ReadSector EC=43 at 0167f7.00.0020

CE Log ErrCode=43 LBA=110e7c1e Type=5 Add To Pending 110e7c1e
Eng Rev = .068
Compat/Hardware = .0T9
NHPLUS2HD - 1_Disk 3.AHC 05-14-08_16:44 AHA,NP_1D_2H_S,3A
CERT Rev = .03U
NONE
Mask Rom Rev = S-1N
Orig Code = AHZ3A0 NHAWK_NP_3A0.068.03U
AT Er 00 Nwt Er 43 RdWr 12640.00.0021
ATA St 50 Er 00 Op ec a,0000/0/00,01 00 00
Niwot: 110e7c1f 18 110e7c1f.0.000 0621 1841 2699 0000 ca96a6
Eng Rev = .068
Compat/Hardware = .0T9
NHPLUS2HD - 1_Disk 3.AHC 05-14-08_16:44 AHA,NP_1D_2H_S,3A
CERT Rev = .03U
NONE
Mask Rom Rev = S-1N
Orig Code = AHZ3A0 NHAWK_NP_3A0.068.03U
--------------------etc....-------------------------------------------------------------------

Comments?? (I would like to actually image this drive now in DE)

-Drew
===============================================================================

On terminal window :

CTRL+Z

T>T4E

(wait for it to finish)

and

T>N50,,22

This will run self-scan test 4E and will "repair" the cert logs. Then N50 will return drive to age 50 - ATA. Now power off and on. Pending bug should be gone.

[Takanashi_Hina]

If you use the UDMA Seagate utility you can save the app code, force the drive to F> and then load the app code from file. This will provide a way for you to extract the data or clone the drive in the safest way up until you re-power the drive, because you are not changing anything on the drive (LOGS). This solution is safer for the data but it will not fix the drive.

The method that I've provided on the other post will actually "fix" the drive for re-use if the problem with it is just the CE error described.

If the drive have further complications and you need to re-use the drive you can try a full self-scan N2,AA,22 (you will loose all data and will be required to copy back vendor and ata tracks) or depop a bad head.

But for now just try the commands that I've published and see if that solves the pending bug issue.

[RescueDRL@gmail.com]

Hey, thanks for your reply! However when I run the T4E command, I get (no waiting)
instant response: "Command Inactive - No VALID Cert Code Detected"
I ran the last commands, repowered and the same Terminal errors persist, twice.

I am interested in that post after the commands, where you say to save the app code
and force the drive to F>. Would you please elaborate?

Thanks again!

-drew
=============================================================================

[Takanashi_Hina]

Hey, thanks for your reply! However when I run the T4E command, I get (no waiting)
instant response: "Command Inactive - No VALID Cert Code Detected"
I ran the last commands, repowered and the same Terminal errors persist, twice.

I am interested in that post after the commands, where you say to save the app code
and force the drive to F>. Would you please elaborate?

Thanks again!

-drew
=============================================================================

Ohhhh, it was a silly mistake from my part,

You have to press CTRL+R first to LOAD CERT, if you don't do that you can't use the self test command (and a huge amount of other commands too)...

Because of the fact that CERT wasn't loaded to RAM, the command didn't execute at all, and so when you re-power the drive the error is still there; it's the expected behavior !!!

[Takanashi_Hina]

I am interested in that post after the commands, where you say to save the app code
and force the drive to F>. Would you please elaborate?

Regarding that it's simple.

When the drive is working normally it will load the firmware overlays from the drive itself, first the ROM on PCB then the SA tracks are read and loaded, if the versions are compatible with ROM, etc ...

Compare this to loading windows os from the hard drive.

Now if your windows have damaged system files and crash at boot, you can still place a boot cd or a boot pen drive with something like BartPe or Hiren's Boot Cd mini windows XP, etc and load windows from that, and repair the damaged system files on the main installation.

The same is true with Seagate Firmware. Even if your drive have damaged firmware you can prevent it from loading from the drive and load the firmware from a file containing the same app code that should be loaded from SA.

The instructions to do so with UDMA tool are already posted on the start of this thread, where you create a loader to load the drive from there.

Ok, now if you extract the app code from your drive (that is not damaged) you will have the perfect code to load on your drive from F> . This file will be 100% compatible with your drive because you extracted it from your drive to start with.

By loading from the app code, even if it's the same, you are preventing other parts of the code from being loaded, you are not loading CERT code, for instance, neither CERT tables, etc .... You are only loading to RAM the code necessary for the drive to work and for you to extract data from it. That is why the pending bug on the Cert table will not manifest when you use the procedure at the start of the post to run the drive. But the problem will be back again when you power off the drive and on again, as you haven't done any change to it.

Compare this as booting from a live CD to extract some data from your windows HDD without fixing the problem with the disk.

The other set of commands that I provided will fix the log and the problem by running the self-scan factory test that re-create the log and solve (hopefully) the issue that you are having.

Hope that this makes some sense.

[Takanashi_Hina]

Well, it's kind of hard to explain by posting what I understand of this pending bug issue and what I understand about the workings of Seagate (prior to F3 arch) code loading.
If you need further assistance or if you need me to explain what I know in a better way add me to skype and I will talk to you and even show you by teamviewer if you want. You don't need to share access to a machine with PC3K UDMA. As long as you have the adaptor or any TTL adaptor for that matter and a drive prior to F3 Arch connected to that computer I can exemplify how to save the app code, place the drive in F> mode and load the saved app code from the saved file.
Check PM for my skype ID.
Of course, it will be free of charge.
Best regards.

[RescueDRL@gmail.com]

Hey Takanashi_Hina , or may I call you Data Monk?

Thanks for the explanations, very clear now.

As it turns out, I left the Seagate patient on the PC3K
overnight and was able to re-start and try a DE Data Copy .

Strange how this drive 'heals' overnight.....

However, this Copy was a New task and the Drive is 'bad' again.

Let me try some of your commands...I'll report later...

-Drew
==============================================