Seagate Barracude 7200.7 8GB - ST380011A - died

[atzensepp]

I read the Vendor track from my other drive which has a FW 8.01.
Found two copies at 0x0800 and 0x1200; S/N is always blank; but on 0x0E00 there is a 9 digit code (ASCII numbers). On 0x1000 there is also something (I should not say stuff).
This information does not help further, does it?

[atzensepp]

Ok I did it:
T>F
SetStuff->ASCIFE
Setting Stuff to defaults
T>

Resetting the drive: Auto Read Errors remain.

AutoRd Err 43 at 00f6ba.00.0002,008b,008e,009d,0118...
Read Ver Retrys

and many others like:
CE Log EC=43 Rtype=26 OV=0 STStatus79
Not handled software path:
AT Er 00 Nwt Er 00 RdWr f6ba.00.0001
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 40705bb7 ff 00005bb7.4070.000 00db 0000 e6b0 000

This vendor track is worn out I guess. The drive tries to access sectors in defective areas on this track for some reasons.

[SAjunky]

Why you are so impatient and risk losing data. I wrote, I would try on my drive fiirst...
What you found above, it is exactly what I wrote. A good drive have identical copies of STUFF in sector 4 (0x800) and 9 (0x1200). A corrupted firmware overwrites STUFF1 with smething else and creates more copies of itself. My STUFF is less corrupted, difference is only in one place (plus checksum). Your shows more destruction and includes serial number. As there are identical copies of corrupted STUFF1, I am pretty sure it is intentional work, otherwise you would see garbage, not your correct serial number. In my opinion error messages come, as G-List has overflown and firmware is unable to handle that, it switches to failover routine and STUFF is modified to reflect it.
However I didn't want you to regenerate translator, before I could make tests how it takes impact on data on my drive. Now it can be too late. Did you read these comments from poehere? He was talking about newer drives, but we are in the same situation. Solution might be here but we are walking in darkness like poehere on newer drives. So mabe start copying as long you can!!!

BTW, What is your type now? Command ';'. And what is Stuff? Command ^U (before loading CERT).

[SAjunky]

I read the Vendor track from my other drive which has a FW 8.01.
Found two copies at 0x0800 and 0x1200; S/N is always blank; but on 0x0E00 there is a 9 digit code (ASCII numbers). On 0x1000 there is also something (I should not say stuff).
This information does not help further, does it?

No. Sector 7 (0xE00) has a number displayed on the bottom of ^U command (on the healthly drive):
Configured-1
Part #: [this number]

Sector 8 (0x1000) is DCO.

[atzensepp]

Hello SAJunky. Actually I had tried copying with ddrescue under Linux several times - before the STUFF-regeneration - with different starting blocks using a IDE-USB adapter since if I boot with drive connected with PATA the PC does not boot at all.

The copying speed has decreased to 0. Could try to copy raw sectors with the ST_MEM but transfer speed of serial is far too low and one needs to know how the raw sectors are mapped to the logical blocks.

[atzensepp]

^U : Stuff still empty; says not configured
; : Age=60 Type=20 MxCyl=16358 MxHd=0 MxSct=44C BSz=0000 TCode=000
^L : :6000000020000000 AX' ' "000000000000"0E306-0E385
SRAM OVly = Diag

Drive detected by HDTune "ST1Disk2Head", 0mB capacity; HDTune crashes on any disk operation.

[atzensepp]

If I restart the drive sometimes I am getting:
; :Age=50 Type=21 MxCyl=16358 MxHd=1 MxSct=44C BSz=0000 TCode=0000
So the reading is inconsistent.

[SAjunky]

ATA interface working only at age 50. Also look that your Base coordinates shifted to safe mode "0E306-0E385. It means that system track hasn't been loaded and initialised.
It probably needed power cycling. Now is better. Is Base cylinder correct now? Still STUFF ^U empty?

If you had separate power supply for hard drive, you would see power-on message:

Code:

Interface task reset
1024k x 16 buffer detected
ALPINE - 1_Disk    M.14  01-16-03 11:51

Buzz  - Head Mask 0000 - Switch to full int.
              Spin Ready
3.06  10-21-03 15:53
(P)PATA Reset
Master


Master/Slave indicates that ATA interface is initialized.

Focus on STUFF values. If ^U shows empty, check values from new copy of the Vendor track. Check and enter correct values at least the following:
Key 1B - drive name.
Key 9E (Type) must be the same as displayed by ';' command
Keys 3C and 83 must be identical, according of the table at the end of the manual. This is LBA value is reported on ATA interface (and printed on HDD label).

Hopefully you get ATA interface working back.

Asking again, wise people for advice about rewriting STUFF sector with defaullt copy 2 (or alternatively writing back the whole Vendor area 12h sectors). It would be easier than fixing ASCIFE mess.

[SAjunky]

Chapter 15 of the manual has a bug. Key 3c and 83 value f8b10950 is wrong, correct value is f8b00950

LBA value is 156,301,488= 0x0950F8B0
It is stored in the STUFF sector at offset 0x78 and 0x106 as B0F85009 (little endian first).

[SAjunky]

Just made ASCIFE on my drive just to see how to recover. Here is the log of typing (after couple unsuccessful attempts).
Worth to note:
- No backspace is parsed. If error is made, it needs to invalidate command line with ^Z
- Setting a name gives SET-STUFFED
- Key 3C doesn't seem to be accepted, but setting key 83 sets also key 3C with the same value.
After this operation, drive is back online and data still intact. You can copy/paste, there are the same values.
Tried surface scan, the same delays, in my case some areas are normal, other slow, there are errors too (in the same places).

Code:

T>F
SetStuff->ASCIFE
Setting stuff to defaults
3.06  10-21-03 15:53
(P)PATA Reset
Master
(
T>F
SetStuff->ASCI1B53543338303031314120202020202020202020202020202020202020202020202020202020202020
Stuff key 1b -> 53 54 33 38 30 30 31 31 41 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
T>
T>AT Stuff
0000: 0c5a  3fff  0000  0010   0000  0000  003f  0000 
0008: 0000  0000  354a  5634   4348  3541  2020  2020 
0010: 2020  2020  2020  2020   0000  1000  0000  332e 
0018: 3036  2020  2020  5354   3338  3030  3131  4120 
0020: 2020  2020  2020  2020   2020  2020  2020  2020 
0028: 2020  2020  2020  2020   2020  2020  2020  8010 
0030: 0000  2f00  0000  0200   0200  0007  3fff  0010 
0038: 003f  0000  0000  0010   ffff  0fff  0000  0007 
0040: 0003  0078  0078  00f0   0078  0000  0000  0000 
0048: 0000  0000  0000  0000   0000  0000  0000  0000 
0050: 001e  0000  3069  4001   4000  0060  0000  0000 
0058: 003f  0000  0000  0000   0000  404b  0000  0000 
0060: 0000  0000  0000  0000   ffff  ffff  0000  0000 
0068: 0000  0000  0000  0000   0000  0000  0000  0000 
0070: 0000  0000  0000  0000   0000  0000  0000  0000 
0078: 0000  0000  0000  0000   0000  0000  0000  0000 
0080: 0000  0000  0000  ffff   ffff  2020  0002  02b6 
0088: 0000  198a  3c24  3c02   ffff  07c6  0100  0800 
0090: 06c0  0500  0002  0000   0000  0000  0000  0000 
0098: 0000  0000  0000  0000   0000  0000  0021  000b 
00a0: 000e  0019  0002  0000   0032  0014  0032  0024 
00a8: 000e  001e  0032  0000   0012  00c1  0032  0014 
00b0: 0022  0000  001a  0000   0012  0000  0010  0000 
00b8: 003e  0000  0000  0000   0032  0000  0000  0000 
00c0: 0000  0000  0000  0000   0000  0000  0000  0000 
00c8: 0000  0000  0000  0000   0000  0000  0000  0000 
00d0: 0000  0000  0000  0000   0000  0000  0000  0000 
00d8: 0000  0000  0000  0000   0000  0000  0000  0000 
00e0: 0000  0030  0003  07d0   1770  3c0a  0000  0000 
00e8: 0000  07d0  03e8  ffff   00bd  0000  0006  0096 
00f0: 0000  0000  0000  0000   0000  0000  0000  0000 
00f8: 0000  0000  0000  0000   0000  0000  0000  0000 



DRIVE HAS BEEN SET-STUFFED -
T>F
SetStuff->ASCI83F8B00950
Stuff key 83 -> f8 b0 09 50
T>AT Stuff
0000: 0c5a  3fff  0000  0010   0000  0000  003f  0000 
0008: 0000  0000  354a  5634   4348  3541  2020  2020 
0010: 2020  2020  2020  2020   0000  1000  0000  332e 
0018: 3036  2020  2020  5354   3338  3030  3131  4120 
0020: 2020  2020  2020  2020   2020  2020  2020  2020 
0028: 2020  2020  2020  2020   2020  2020  2020  8010 
0030: 0000  2f00  0000  0200   0200  0007  3fff  0010 
0038: 003f  0000  0000  0010   f8b0  0950  0000  0007 
0040: 0003  0078  0078  00f0   0078  0000  0000  0000 
0048: 0000  0000  0000  0000   0000  0000  0000  0000 
0050: 001e  0000  3069  4001   4000  0060  0000  0000 
0058: 003f  0000  0000  0000   0000  404b  0000  0000 
0060: 0000  0000  0000  0000   f8b0  0950  0000  0000 
0068: 0000  0000  0000  0000   0000  0000  0000  0000 
0070: 0000  0000  0000  0000   0000  0000  0000  0000 
0078: 0000  0000  0000  0000   0000  0000  0000  0000 
0080: 0000  0000  0000  f8b0   0950  2020  0002  02b6 
0088: 0000  198a  3c24  3c02   ffff  07c6  0100  0800 
0090: 06c0  0500  0002  0000   0000  0000  0000  0000 
0098: 0000  0000  0000  0000   0000  0000  0021  000b 
00a0: 000e  0019  0002  0000   0032  0014  0032  0024 
00a8: 000e  001e  0032  0000   0012  00c1  0032  0014 
00b0: 0022  0000  001a  0000   0012  0000  0010  0000 
00b8: 003e  0000  0000  0000   0032  0000  0000  0000 
00c0: 0000  0000  0000  0000   0000  0000  0000  0000 
00c8: 0000  0000  0000  0000   0000  0000  0000  0000 
00d0: 0000  0000  0000  0000   0000  0000  0000  0000 
00d8: 0000  0000  0000  0000   0000  0000  0000  0000 
00e0: 0000  0030  0003  07d0   1770  3c0a  0000  0000 
00e8: 0000  07d0  03e8  ffff   00bd  0000  0006  0096 
00f0: 0000  0000  0000  0000   0000  0000  0000  0000 
00f8: 0000  0000  0000  0000   0000  0000  0000  0000 



DRIVE HAS BEEN SET-STUFFED -

[atzensepp]

Hi SAJunky, many thanks for your exhaustive research! I have tried to repeat your steps. The drive has errors on the vendor track. So I had to repeat some settings. Drive is stuffed but the read errors at reset time remain. Here my log:

Interface task reset
1024k x 16 buffer detected
ALPINE - 1_Disk M.14 01-16-03 11:51
Head Mask 0000 - Switch to full int.
Spin Ready
3.06 02-17-04 10:59
(P)PATA Reset

CE Log EC=0 Rtype=36 OV=0 STStatus0
AutoRd Err 43 at 00f6ba.00.008f

Read Ver Retrys
AutoRd Err 43 at 00f6ba.00.008f

Read Ver Retrys
AutoRd Err 43 at 00f6ba.00.008f

Read Ver Retrys
AutoRd Err 43 at 00f6ba.00.008f

Read Ver Retrys
AutoRd Err 43 at 00f6ba.00.008f

Read Ver Retrys

Read Ver Failure!
AutoRd Err 43 at 00f6ba.00.0002

Read Ver Retrys
AutoRd Err 43 at 00f6ba.00.0002

Read Ver Retrys
Master

T>F
SetStuff->ASCIFE
Setting stuff to defaults

T>F
SetStuff->ASCI1B5354333830303131412020202020202020202020202020202020202020202020
Stuff key 1b -> 53 54 33 38 30 30 31 31 41 20 20 20 20 20 20 20 20 20 20 20 20 2
0 20 20 20 20 20 20 20 20 20 20 ff ff ff ff ff ff ff ff

T>F
SetStuff->ASCI83F8B00950
Stuff key 83 -> f8 b0 09 50
AutoRd Err 43 at 00f6ba.00.0007

Read Ver Retrys
T>F
SetStuff->ASCI83F8B00950
Stuff key 83 -> f8 b0 09 50
T>
T>AT Stuff
0000: 0c5a 3fff 0000 0010 0000 0000 003f 0000
0008: 0000 0000 354a 5638 4e58 5251 2020 2020
0010: 2020 2020 2020 2020 0000 1000 0000 332e
0018: 3036 2020 2020 5354 3338 3030 3131 4120
0020: 2020 2020 2020 2020 2020 2020 2020 2020
0028: 2020 2020 2020 ffff ffff ffff ffff 8010
0030: 0000 2f00 0000 0200 0200 0007 3fff 0010
0038: 003f 0000 0000 0010 f8b0 0950 0000 0007
0040: 0003 0078 0078 00f0 0078 0000 0000 0000
0048: 0000 0000 0000 0000 0000 0000 0000 0000
0050: 001e 0000 3069 4001 4000 0061 0000 0000
0058: 003f 0000 0000 0000 0000 404b 0000 0000
0060: 0000 0000 0000 0000 f8b0 0950 0000 0000
0068: 0000 0000 0000 0000 0000 0000 0000 0000
0070: 0000 0000 0000 0000 0000 0000 0000 0000
0078: 0000 0000 0000 0000 0000 0000 0000 0000
0080: 0000 0000 0000 f8b0 0950 2020 0002 02b6
0088: 0000 198a 3c24 3c0a ffff 07c6 0100 0800
0090: 06c0 0500 0002 f8b0 0000 0000 0000 0000
0098: 0000 0000 0000 0000 0000 0000 0021 000b
00a0: 000e 0019 0002 0000 0032 0014 0032 0024
00a8: 000e 001e 0032 0000 0012 00c1 0032 0014
00b0: 0022 0000 001a 0000 0012 0000 0010 0000
00b8: 003e 0000 0000 0000 0032 0000 0000 0000
00c0: 0000 0000 0000 0000 0000 0000 0000 0000
00c8: 0000 0000 0000 0000 0000 0000 0000 0000
00d0: 0000 0000 0000 0000 0000 0000 0000 0000
00d8: 0000 0000 0000 0000 0000 0000 0000 0000
00e0: 0000 0030 0003 07d0 1770 3c0a 0000 0000
00e8: 0000 07d0 03e8 ffff 00bd 0000 0006 0096
00f0: 0000 0000 0000 0000 0000 0000 0000 0000
00f8: 0000 0000 0000 0000 0000 0000 0000 0000



DRIVE HAS BEEN SET-STUFFED -

Is it necessary to get rid of these errors? I'd think so. But how?

[BlackST]

The drive has errors on the vendor track.

What if it's ONLY YOUR IDEA ?

In any case, why concentrate on that "stuff" ?

[atzensepp]

- the drive is producing hundreds of read errors on the vendor track f6ba:
Read Ver Retrys
AutoRd Err 43 at 00f6ba.00.0096

- the drive is still in Master mode and cannot be recognized via PATA. Terminal mode is the only possibility to communicate with the drive at all

- It is not possible to set the correct type or head number:
;
Age=50 Type=21 MxCyl=16358 MxHd=1 MxSct=44C BSz=0000
TCode=0000
%
:5000000821000001 AX`5JV8NXRQ' "000000000000"0F68E-0F70D
SRAM Ovly = AT

- if I am not getting a clue from SAJunky, you or another pro perheps the best idea at the moment - with my admittedly limited knowledge of the matter - is to read out the drive sectors with terminal mode for several months and find out how to map the sectors. But maybe the very best idea is to forget the data in the drive's permanent coma.

[SAjunky]

Hi,
I see STUFF type is correct. Model name has changed, but missing 8 spaces, had been replaced by FF FF....
See, when command is accepted, drive respond with "Stuff key 1b ->.....".
If doesn't respond such way, command is ignored. See below that the first attempt of setting a key 83 is accepted, but second ignored. But you had been perhaps distracted by independent message, so tried again.

Code:

T>F
SetStuff->ASCI1B5354333830303131412020202020202020202020202020202020202020202020
Stuff key 1b -> 53 54 33 38 30 30 31 31 41 20 20 20 20 20 20 20 20 20 20 20 20 2
0 20 20 20 20 20 20 20 20 20 20 ff ff ff ff ff ff ff ff

T>F
SetStuff->ASCI83F8B00950
Stuff key 83 -> f8 b0 09 50
AutoRd Err 43 at 00f6ba.00.0007

Read Ver Retrys
T>F
SetStuff->ASCI83F8B00950
Stuff key 83 -> f8 b0 09 50



You need to enter key 1B again, it might be a reason that "master" do not appear on the power-on message. Count carefully, it has to be 40 Hex double digits after ASCI1b. Your typing can be mixed with outgoing messages,don't worry, only your keystrokes count.
All other fields seem to be set properly. If you fix name, watch this 'master' or 'slave' word. If it appears, then should be fine.

[atzensepp]

Hi SAJunky. I have tried to write the 20's but without success.

Writing the full sequence:
SetStuff->ASCI1B5354333830303131412020202020202020202020202020202020202020202020
Stuff key 1b -> 53 54 33 38 30 30 31 31 41 20 20 20 20 20 20 20 20 20 20 20 20 2
0 20 20 20 20 20 20 20 20 20 20 ff ff ff ff ff ff ff ff
T>

Writing only one word:
T>F
SetStuff->ASCI2B2020
AutoRd Err 43 at 00f6ba.00.000c

Read Ver Retrys
AutoRd Err 43 at 00f6ba.00.0008

Read Ver Retrys
T>

I have tried several times without success. Therefore I concluded that the medium must be worn out.

But BlackST thinks that there are other possibilites and I should concentrate on different "stuff".

Possiblly readjusting the "head adaptives" for head 0 by a partial self scan (= factory self-testing cycle?) That this might be possible could be read in the last paragraph of an article from Artem Makarov:
http://www.hardmaster.info/eng/articles/20-01-2009.html
Remember BlackST's comment on your statement on the destructivness of self scan "ARE YOU SURE...".

So how is a "partial" or restricted selfscan possible? This would not only help for read errors on the vendor track but also on other tracks. What do you think?

[SAjunky]

I understand last BlackST comment to not focus on AutoRd Err 43 messages. Selfscan is desctructive. I can't comment on partial selfscan, I don't know. Ask BlackST. I know only one things: before running selfscan, you need to stabilise firmware first. Otherwise selfscan will fail.

So coming back to the main business, your command line contains again 32 characters for name instead of 40 characters (or 40 pairs of hex digits). I urge to make it properly, maybe copy/paste the following will work:

ASCI1B53543338303031314120202020202020202020202020202020202020202020202020202020202020

[SAjunky]

I made further tests on my guinea pig. I enterred deliberately 32 characters in key 1B. My HDD didn't lose ability to work on ATA interface. So I guess fixing name not going to restore ATA interface in your case. It must be something else you did wrong, or simply firmware is more corrupted in your case.
Now I uploaded Vendor track (which has been backed up before) back to the hard drive. Writing is 5 times slower than reading. I see no negative effects on data and STUFF has been restored to "Configured -1".
Now going to investigate uploading Vendor track from the donor and see whether my firmware will stabilise, also watching what happen with data.

So unless you get a response to NOT do it, I suggest to restore your Vendor track (first 0x12 sectors) as I did. Your script (for your BASE) is attached, and mine for comparison as a txt file. When your ATA interface is restored, I suggest to strart copying.

Before starting the script I suggest to verify if your BASE hasn't been changed, as your HDD is able to boot with safe mode BASE!
I get errors as shown below, but it seems doesn't affect writing.

Code:

T>
ÐÛ¯­¯±‗³ COM/HDD=115200 / B0115
÷
T>
þÓ´¯ÙÝ Õý ß¾¶Õ­
210
211
212
213
214
215
216
217
218
219
21A
21B
21C
21D
21E
21F
þÓ´¯ÙÝÞÙÞ ß¾¶Õ­¹ ÝÓ¸ÞÝÓ  ± 210 10 °‗ Þþ ¶ÓÚÙÓ G:\TEMP\STwin\vnd.trc
/2
Command Inactive - No VALID Cert Code Detected
2>
Command Inactive - No VALID Cert Code Detected
2>
sE9C7,0
2>
w,0,10
2>


Attachments

Vendor_WR.ZIP

(718 Bytes) Downloaded 608 times

[atzensepp]

I understand last BlackST comment to not focus on AutoRd Err 43 messages. Selfscan is desctructive. I can't comment on partial selfscan, I don't know. Ask BlackST. I know only one things: before running selfscan, you need to stabilise firmware first. Otherwise selfscan will fail.

So coming back to the main business, your command line contains again 32 characters for name instead of 40 characters (or 40 pairs of hex digits). I urge to make it properly, maybe copy/paste the following will work:

ASCI1B53543338303031314120202020202020202020202020202020202020202020202020202020202020

Hi SAJunky. Many thanks for your faitfhful suppurt! I have tried as you said. This time it worked and the drive accepted the 20's. Either because its a new day or simply because F-commands does not really accept every key.

0018: 3036 2020 2020 5354 3338 3030 3131 4120
0020: 2020 2020 2020 2020 2020 2020 2020 2020
0028: 2020 2020 2020 2020 2020 2020 2020 8010
..
Neverteheless the driveis still in Master-mode only.

[SAjunky]

Neverteheless the driveis still in Master-mode only.

What do you mean by that? Does it show 'Master' or 'Slave' on the last line of boot string? If so, then is fine, but I don't expect so, after my last tests. See my previous post, that would return drive to working on ATA interface.

[atzensepp]

Hello SAJunky: I have done the read back of my copy of the vendor track. Log as follows:

Interface task reset
1024k x 16 buffer detected
ALPINE - 1_Disk M.14 01-16-03 11:51
Head Mask 0000 - Switch to full int.
Spin Ready
3.06 02-17-04 10:59
(P)PATA Reset

CE Log EC=0 Rtype=36 OV=0 STStatus0
AutoRd Err 43 at 00f6ba.00.008b

Read Ver Retrys
AutoRd Err 43 at 00f6ba.00.008b

Read Ver Retrys
Master

Ñêîðîñòü COM/HDD=115200 / B0115
Ö
T>
çàïîëíÿåì áóôåð
210
211
212
213
214
215
216
217
218
219
21A
21B
21C
21D
21E
21F
çàïîëíèëè áóôåðû íà÷èíàÿ ñ 210 10 øò èç ôàéëà C:\Install\ST_MEM_FREE\vnd.trc
/2
2>
2>
sF89A,0
2>
w,0,10
Code - FE Track 0F89A.0.000 Sns 006 Rty F7FF.FF.80FF Rtf 1800 LBA 00000000
2>
Ñêîðîñòü COM/HDD=115200 / B0115
T>
T>
çàïîëíÿåì áóôåð
210
211
çàïîëíèëè áóôåðû íà÷èíàÿ ñ 210 2 øò èç ôàéëà C:\Install\ST_MEM_FREE\vnd.trc
/2
2>
2>
sF89A,0
2>
w,10,2
Code - FE Track 0F89A.0.010 Sns 006 Rty F7FF.FF.80FF Rtf 1800 LBA 00000000
2>
Ñêîðîñòü COM/HDD=9600 / B0096
T>

After Power Cylcing:

Interface task reset
1024k x 16 buffer detected
ALPINE - 1_Disk M.14 01-16-03 11:51
Head Mask 0000 - Switch to full int.
Spin Ready
3.06 02-17-04 10:59
(P)PATA Reset

Stuff Was Unreadable
T>
Remarkably the drive starts with "Stuff was Unreadable" but the Stuff print out (^U) is ok but it says now at the end:
Not configured-0

Did you compare my vendor track with your's? Are there any further differences outside the STUFF regions? Maybe if I had a known "sane" vendor track from an identical drive I could try to load this one and adapt S/N. My other drive has a 8.01 firmware. I would bet that this would not work.