Seagate F3 NRG list Dangers

[higgsboson]

While standard practice for dealing with typical Seagate drives issues is --

1) Clear Smart
2) Erase Non resident G list
3) Erase ALT list
4) Recover translator

This is suggested method by ACELAB

However recently I have been told by a Professional GURU that NRG list may contain hidden Defects & by clearing those defects translator is not built fully. If NRG list is not taken into account it will be not give access to full data area due to loss of these records. He said never to erase NRG list directly.

What is true ? What should be done with typical issues --
1) SMART TRIP
2) Reallocation failed
3) BGMS DOS Rewrite

Disk tends to be busy or while copying suddenly starts giving all bad sectors.
Can someone pls shed light which might be useful for all.

[jermy]

While standard practice for dealing with typical Seagate drives issues is --

...
2) Erase Non resident G list
...
...

This is suggested method by ACELAB

only for the sake of an innocent person will pass by this thread, i'm replying
Sorry, but never was and never will be

[day1data]

While standard practice for dealing with typical Seagate drives issues is --

2) Erase Non resident G list

This is suggested method by ACELAB

ACE would never recommend that.

[drHDD]

As I can see Ace lab manual tell me not to erase Non resident G list. So you need to check yours sources.

[higgsboson]

Hi
Thanks all for valuable contribution.

Jermy : --- I did not understood what you mean.

Here is particular thread.- http://forum.acelaboratory.com/viewtopi ... ist#p28275

I am also attaching snapshot of the comments.

Attachments

[northwind]

m0,6,3 does not affect NRG entries.

[higgsboson]

Yes as per instructions in this thread , NRG list is erased prior to applying mo commands.(translator regeneration)

[higgsboson]

Should I edit NRG list and transfer defects to G list?
Do I need to regenerate translator after transferring defects ?

[H13]

Hi ,
He asked u to give him the safe steps to repair .. this type off seagate drives ..

thanks

[hpw333]

well , for Repair
m0,6,3,,,,,22 recover Translator prb
m0,6,2,,,,,22 Regen Translator

if you need to regen translator by m0,6,2,,,,,22 then you must Clear NRG Entries
or you will got partial access problem , where you can access some lba in begining of HDD and reset hdd full of bad sector

While standard practice for dealing with typical Seagate drives issues is --

1) Clear Smart
2) Erase Non resident G list
3) Erase ALT list
4) Recover translator

typical for what ?
you should diagnose problem first then decide typical solution for it

[higgsboson]

Thanks a lot hpwlab

I agree totally there is no typical and each case must be analysed seprately.

this paricular case gives access to data sectors but suddenly starts showing all bad sectors.
I want to recover data.
As you have mentioned should I erase NRG list and reg. translator by m0,6,2,,,,22 command ?
Is recover translator is meant for repair and regenerate for data recovery?
How to choose between recv. & regn

[higgsboson]

Here I have found warning on direct clearing NRG list

Attachments

[chipsang]

MRT lab has added P list into consideration in this issues ( Sector access interruption).
here is post --
viewtopic.php?f=28&t=31342&hilit=sector+access+interruption

Attachments

[hpw333]

why you judge that bad sector from corrupted translator ?
also @ chipsang,
plist have primary Flag 80 for SF entries
and Flag like C for entries come from other defect-lists
also can cause other error like 500E

@higgsboson,
Back up p-list ,NRG List , Translator to be safe
then upload picture for logical scan

[higgsboson]

Hi hpwlab
yes I dont know whether defects are coming from translator corruption or not.
I will better post all details.

[higgsboson]

Thanks to all particularly hpwlab , drive has become obedient. Earlier I was able to clear flags from 08F file.
I have beena ble to image required data sectors using 3 heads.
Only head 0 is remained .It is reading very slow. What could be the reason for this behaviour ?
Now Terminal output has also changed -

what should I do to speed up reading by Head 0

P) SATA Reset

RW: Error processing Performance Parameter File: 203A
Set Transfer Mode selected
Ultra DMA selected
Set Transfer Mode selected
Starting LBA of RW Request=0475ABC7 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0475AC9B Sense Code=43110081
Starting LBA of RW Request=0475ABC7 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0475AE04 Sense Code=43110081
Starting LBA of RW Request=0475ABC7 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0475AEB4 Sense Code=43110081
Starting LBA of RW Request=0475AEE7 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0475AF0F Sense Code=43110081
Starting LBA of RW Request=0475AEE7 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0475AF17 Sense Code=43110081
(S) SATA Reset

Send Status: COMRESET seen
(S) SATA Reset

Send Status: COMRESET seen
Starting LBA of RW Request=0475AEE7 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0475AEF0 Sense Code=43110081
Set Transfer Mode selected
Ultra DMA selected
Set Transfer Mode selected
Starting LBA of RW Request=0475AF4A Length=FFFFFFFF
ProcessRWError -Read- at LBA 0475AF4F Sense Code=43110081
(S) SATA Reset

Send Status: COMRESET seen
(S) SATA Reset

Send Status: COMRESET seen
Starting LBA of RW Request=0475AF4A Length=FFFFFFFF
ProcessRWError -Read- at LBA 0475AF81 Sense Code=43110081
Starting LBA of RW Request=0475AF82 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0475AF98 Sense Code=43110081
Set Transfer Mode selected
Ultra DMA selected

Attachments

terminal.txt

(2.64 KiB) Downloaded 1129 times

N8.txt

(26.34 KiB) Downloaded 1063 times

V4.txt

(173.73 KiB) Downloaded 956 times

V40.txt

(5.15 KiB) Downloaded 1083 times

[gps31]

I had already erased NRG list many times (Whenever i get Partial Access Problem), A clean sysfile 35 (without NRG entries) from same model with same size (firm version is not problem) and sysfile 28 uploaded to HDD both copies.

Then Power Reset then used m0,6,3,,,,,22 then clear SMART before format cleared G-List(i4,1,22) then applied pending fix

First time hdd took some time to detect (Less than min) then hdd imaged

I had succeeded this only on ST3500418AS and ST500DM002.

This process may be wrong but in my all cases for these two models it worked

Note: Always backup before apply anything

[higgsboson]

Hi gps31
Thanks for sharing your experience. I will try to clean these 2 files ( 28 & 35)

[higgsboson]

Despite clearing Flags of these 2 files disk is reading very slow only for Head 0. Is there any specific file which controls Head 0 ?
Thanks.

[MindMergepk]

could be problem with Head,
can you show us the resistance for all heads ?