Segate st980825as 80GB

[senordingdong]

I have a st980825as that is doing something a bit strange.

I can plug it in and read sectors (using hdparm) for around 30 seconds to a minute. after that time any sector read results in an IO error. I can then remove power, replug, and read sectors again until that time passes.

Ive been able to recover about 500MB of the 80GB (using DDrescue), but this method is not really viable (unless its the only option)

the drive does get hot, but even cooling it with a fan make no difference to this process.

My initial thought was failing head, but the consistency of this has me questioning that.

I have not yet hooked into the UART to see what what it is saying.

Possible that this is a SMART or drive cache issue?

[sathyan]

I had something similar, a long time ago(v long time)..
when without a hardware imager, or wanting to change the heads, MTP and manual switch inline to the drive did the trick.
But i wouldn't go that way now..


if data is important,take pro help, should not cost much.

else
a) rule out PCB issue
b) check terminal output

"

Possible that this is a SMART or drive cache issue?

"
not usually

[senordingdong]

Sounds good. I was thinking of going that route if need be. Put a switch inline to be able to toggle power on and off and just go about this the long way. At least its only 80GB ha

What is MTP, not familiar with that?

I am going to check terminal output today, i have to imagine whatever is happening will be shown (if only cryptically) in the terminal output.

[senordingdong]

OK, so terminal spits this out

(P)SATA Reset
Q X
Switch to full int.
Spin Ready
Head Mask FFFF - Switch to full int.
Spin Ready
Q AT Er 00 Nwt Er 43 RdWr 00066.03.0043
ATA St 50 Er 00 Op 60 4, 0060183,5800 0000 0101
Niwot: 00060183 3a 00060183.f.fe6 8000 23f2 07fe 0000

CE Log ErrCode=43 LBA=60183 Type=6Not handled software path:


Also getting INVALID Cert Disk code - ROM resident Revision required : 3.04

and

Inactive no valid cert code detected

[sathyan]

What is MTP, not familiar with that?

Media tools professional

check with another PCB(rule out PCB issue)
Does the drive clicks or makes unusual sound after the "30 seconds to a minute of proper reading" ?
if so, (and if data is important) chances are that you will make the problem worse trying to clone it

in my case, it was a head issue, as i found out later(after recovering the data , i tried swapping heads to know the cause)

[senordingdong]

no noises or anything unusual.

I suppose i will have to obtain a donor drive to try pcb swap.

[senordingdong]

CE Log ErrCode=47 LBA=7983ae Type=25 Add To Pending 7983ae
SCAN Error


CE Log ErrCode=43 LBA=19bf3 Type=25 Add To Pending 19bf3
SCAN Error
AT Er 00 Nwt Er 43 RdWr 0092c.03.017b
ATA St 50 Er 00 Op b0 0,c24f/0/00,00 00 da
Niwot: 00b00001 ff 00b00001.0.297 0000 0000 0040 0070


when the data transfer ultimately fails (usually around 40MB) i get CE Log ErrCode=43 LBA=7983b4 Type=26Not handled software path:


My research shows that i may be suffering from something called the "Pending Bug" that was common on drives of this era.

Can anyone with experience with this bug confirm that this is the case?

If this is not the case, my other thought is that the CERT is not being read correctly, as i do on occasion get this message
INVALID Cert Disk code - ROM resident Revision required : 3.04

[pepe]

Hello,

yes, it is a bug in the fw and can be easily recovered with proper tools. I recommend contacting somebody near you, there are several guys on this forum from the US. Where are you?

pepe

[senordingdong]

I am in PA, United States.

I have seen some terminal methods of resolving this bug, as well as using a loader file. I do not have proper equipment for the loader method.

Opening up to quotes from forum members.

Thank You

[fzabkar]

Could we see a SMART report?

https://crystalmark.info/software/CrystalDiskInfo/index-e.html

Do your Niwot errors show different numbers in the C.H.S position?

Q AT Er 00 Nwt Er 43 RdWr 00066.03.0043

I expect that these three numbers would be the CHS address of the read/write error, in which case it would appear that there is a problem with head #3. Conversely, if the errors show up on all heads, then this could point to a PCB fault.

BTW, you might like to try HDDSuperClone:

http://www.sdcomputingservice.com/hddsuperclone

IIUC, the following error would suggest that there is a problem reading the System Area on the platters, which would in turn point to a problem with head #0.

INVALID Cert Disk code - ROM resident Revision required : 3.04

Here is something you could try ...

Fixing the "Pending Bug" prior to the F3 Arch :
http://www.hddoracle.com/viewtopic.php?f=83&t=175

Last edited by fzabkar on August 25th, 2017, 16:42, edited 1 time in total.

[senordingdong]

Maybe a stupid question, but since this is a firmware bug, can i flash unaffected/fixed firmware to the SPI chip? I do have such a programmer, and can easily do so if firmware is available.

[fzabkar]

Maybe a stupid question, but since this is a firmware bug, can i flash unaffected/fixed firmware to the SPI chip? I do have such a programmer, and can easily do so if firmware is available.

No, the majority of the firmware exists in the System Area on the platters ("discware"). Only a small portion resides in flash memory.

[senordingdong]

Could we see a SMART report?

https://crystalmark.info/software/CrystalDiskInfo/index-e.html

Do your Niwot errors show different numbers in the C.H.S position?

Q AT Er 00 Nwt Er 43 RdWr 00066.03.0043

I expect that these three numbers would be the CHS address of the read/write error, in which case it would appear that there is a problem with head #3. Conversely, if the errors show up on all heads, then this could point to a PCB fault.

BTW, you might like to try HDDSuperClone:

http://www.sdcomputingservice.com/hddsuperclone

IIUC, the following error would suggest that there is a problem reading the System Area on the platters, which would in turn point to a problem with head #0.

INVALID Cert Disk code - ROM resident Revision required : 3.04

Here is something you could try ...

Fixing the "Pending Bug" prior to the F3 Arch :
http://www.hddoracle.com/viewtopic.php?f=83&t=175

----------------------------------------------------------------------------
Model : ST980825AS
Firmware : 3.04
Serial Number : 3MH0LJ08
Disk Size : 80.0 GB (8.4/80.0/80.0/80.0)
Buffer Size : 8192 KB
Queue Depth : 32
# of Sectors : 156301488
Rotation Rate : Unknown
Interface : UASP (Serial ATA)
Major Version : ATA/ATAPI-7
Minor Version : ----
Transfer Mode : ---- | SATA/150
Power On Hours : 7852 hours
Power On Count : 3416 count
Temperature : 27 C (80 F)
Health Status : Caution
Features : S.M.A.R.T., APM, 48bit LBA, NCQ
APM Level : 8080h [ON]
AAM Level : ----
Drive Letter :

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 _44 _31 __6 000002B0A64E Read Error Rate
03 _94 _93 __0 000000000000 Spin-Up Time
04 _97 _97 _20 000000000D44 Start/Stop Count
05 _79 _79 _36 000000000354 Reallocated Sectors Count
07 _67 _60 _30 00150616D2F3 Seek Error Rate
09 _92 _92 __0 000000001EAC Power-On Hours
0A 100 _99 _34 000000000000 Spin Retry Count
0C _97 _97 _20 000000000D58 Power Cycle Count
BB __1 __1 __0 00000000AAEA Reported Uncorrectable Errors
BD 100 100 __0 000000000000 High Fly Writes
BE _73 _46 _45 00731B1B001B Airflow Temperature
C0 _99 _99 __0 000000000A56 Power-off Retract Count
C1 __1 __1 __0 000000050BD5 Load/Unload Cycle Count
C2 _27 _54 __0 00040000001B Temperature
C3 _50 _43 __0 00000A2C1888 Hardware ECC recovered
C5 _17 _17 __0 0000000006A3 Current Pending Sector Count
C6 _17 _17 __0 0000000006A3 Uncorrectable Sector Count
C7 200 200 __0 000000000000 UltraDMA CRC Error Count
C8 100 253 __0 000000000000 Write Error Rate
CA _92 245 __0 000000000008 Data Address Mark Error

-- IDENTIFY_DEVICE ---------------------------------------------------------
0 1 2 3 4 5 6 7 8 9
000: 0C5A 3FFF C837 0010 0000 0000 003F 0000 0000 0000
010: 2020 2020 2020 2020 2020 2020 334D 4830 4C4A 3038
020: 0000 4000 0004 332E 3034 2020 2020 5354 3938 3038
030: 3235 4153 2020 2020 2020 2020 2020 2020 2020 2020
040: 2020 2020 2020 2020 2020 2020 2020 8010 0000 2F00
050: 4000 0200 0200 0007 3FFF 0010 003F FC10 00FB 0010
060: F8B0 0950 0000 0407 0003 0078 0078 00F0 0078 0000
070: 0000 0000 0000 0000 0000 001F 0502 0000 0048 0040
080: 00FE 0000 346B 7D09 6003 3469 3C09 6003 007F 0000
090: 0000 8080 FFFE 0000 FE00 0000 0000 0000 0000 0000
100: F8B0 0950 0000 0000 0000 0000 4000 0000 0000 0000
110: 0000 0000 0000 0000 0000 0000 0000 0100 0000 0000
120: 0000 0000 0000 0000 0000 0000 0000 0000 0001 F8B0
130: 0950 F8B0 0950 2020 0002 82B6 0002 0000 3C06 3C06
140: FFFF 07C6 0100 0000 100F 1800 0002 0080 0000 0000
150: 60A0 0000 0000 0000 0000 0000 0000 0000 0700 000B
160: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
170: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
180: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
190: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
200: 0000 0000 0000 0000 0000 0000 0001 0000 0000 0000
210: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
220: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
230: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
240: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
250: 0000 0000 0000 0000 0000 4AA5

-- SMART_READ_DATA ---------------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 0A 00 01 0F 00 2C 1F 4E A6 B0 02 00 00 00 03 03
010: 00 5E 5D 00 00 00 00 00 00 00 04 32 00 61 61 44
020: 0D 00 00 00 00 00 05 33 00 4F 4F 54 03 00 00 00
030: 00 00 07 0F 00 43 3C F3 D2 16 06 15 00 00 09 32
040: 00 5C 5C AC 1E 00 00 00 00 00 0A 13 00 64 63 00
050: 00 00 00 00 00 00 0C 32 00 61 61 58 0D 00 00 00
060: 00 00 BB 32 00 01 01 EA AA 00 00 00 00 00 BD 3A
070: 00 64 64 00 00 00 00 00 00 00 BE 22 00 49 2E 1B
080: 00 1B 1B 73 00 00 C0 32 00 63 63 56 0A 00 00 00
090: 00 00 C1 32 00 01 01 D5 0B 05 00 00 00 00 C2 22
0A0: 00 1B 36 1B 00 00 00 04 00 00 C3 1A 00 32 2B 88
0B0: 18 2C 0A 00 00 00 C5 12 00 11 11 A3 06 00 00 00
0C0: 00 00 C6 10 00 11 11 A3 06 00 00 00 00 00 C7 3E
0D0: 00 C8 C8 00 00 00 00 00 00 00 C8 00 00 64 FD 00
0E0: 00 00 00 00 00 00 CA 32 00 5C F5 08 00 00 00 00
0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 82 79 AA 01 00 5B
170: 03 00 01 02 01 54 00 00 00 00 00 00 00 00 00 00
180: 00 00 AD DB 61 00 00 07 06 06 06 06 06 07 07 00
190: 00 00 00 00 00 00 00 01 AF 83 79 00 02 00 00 00
1A0: 01 00 BD 61 2B B7 1C 05 00 00 A3 06 00 00 00 00
1B0: 00 00 00 00 AF 83 79 00 00 00 00 00 00 00 00 00
1C0: 02 00 01 00 B5 06 00 00 00 00 E8 33 FD A5 00 00
1D0: 00 00 1B 00 00 00 00 00 00 00 AC 1E 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 28

-- SMART_READ_THRESHOLD ----------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 0A 00 01 06 00 00 00 00 00 00 00 00 00 00 03 00
010: 00 00 00 00 00 00 00 00 00 00 04 14 00 00 00 00
020: 00 00 00 00 00 00 05 24 00 00 00 00 00 00 00 00
030: 00 00 07 1E 00 00 00 00 00 00 00 00 00 00 09 00
040: 00 00 00 00 00 00 00 00 00 00 0A 22 00 00 00 00
050: 00 00 00 00 00 00 0C 14 00 00 00 00 00 00 00 00
060: 00 00 BB 00 00 00 00 00 00 00 00 00 00 00 BD 00
070: 00 00 00 00 00 00 00 00 00 00 BE 2D 00 00 00 00
080: 00 00 00 00 00 00 C0 00 00 00 00 00 00 00 00 00
090: 00 00 C1 00 00 00 00 00 00 00 00 00 00 00 C2 00
0A0: 00 00 00 00 00 00 00 00 00 00 C3 00 00 00 00 00
0B0: 00 00 00 00 00 00 C5 00 00 00 00 00 00 00 00 00
0C0: 00 00 C6 00 00 00 00 00 00 00 00 00 00 00 C7 00
0D0: 00 00 00 00 00 00 00 00 00 00 C8 00 00 00 00 00
0E0: 00 00 00 00 00 00 CA 00 00 00 00 00 00 00 00 00
0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 E4

[senordingdong]

Do your Niwot errors show different numbers in the C.H.S position?

Q AT Er 00 Nwt Er 43 RdWr 00066.03.0043

I expect that these three numbers would be the CHS address of the read/write error, in which case it would appear that there is a problem with head #3. Conversely, if the errors show up on all heads, then this could point to a PCB fault.

If we are talking physical heads, is it even likely that a 2.5" 80GB drive would even have 3 heads?

[fzabkar]

If we are talking physical heads, is it even likely that a 2.5" 80GB drive would even have 3 heads?

Momentus 7200.1 SATA Product Manual - ST910021AS, ST980825AS, ST96023AS, and ST94015AS:
http://www.seagate.com/support/disc/manuals/sata/100320528a.pdf

Code:

                                     ST910021AS ST980825AS ST96023AS ST94015AS 
Formatted Gbytes (512 bytes/sector)  100        80         60        40
Physical read/write heads            4          4          3         2 
Discs                                2          2          2         1

[fzabkar]

(...)

Here is something you could try ...

Fixing the "Pending Bug" prior to the F3 Arch :
http://www.hddoracle.com/viewtopic.php?f=83&t=175

This will NOT work .....

Because of this :

(...)

Also getting INVALID Cert Disk code - ROM resident Revision required : 3.04

and

Inactive no valid cert code detected

One would need a valid CERT to run SS tests. The method on my forum requires the use of a valid CERT.

OP needs proper tools to either run the drive by loader / external firmware tracks or to load a valid CERT compatible with ROM to the drive and then use the procedure on my forum ....

But the OP's drive comes ready and is able to read the user area, so ISTM that the "invalid cert code" error must be intermittent ???

[senordingdong]

But the OP's drive comes ready and is able to read the user area, so ISTM that the "invalid cert code" error must be intermittent ???

The CERT error happens when i press Ctrl R

Otherwise this error does not occur.

Due to this error (which is consistent thus far) no commands can be run. I can only passively monitor terminal messages.

I can absolutely read data from this drive. And i can read data from different sections of the drive. The ~1GB i have recovered in laborious ~40MB chunks does appear to contain files i attempting to recover. I say this because i thought it may be just writing 0s or something useless, but not the case.

Thats what has me super confused. How can it be becoming ready and readable if that part of the firmware is damaged/unreadable.

[fzabkar]

But the OP's drive comes ready and is able to read the user area, so ISTM that the "invalid cert code" error must be intermittent ???

The CERT error happens when i press Ctrl R

Otherwise this error does not occur.

Due to this error (which is consistent thus far) no commands can be run. I can only passively monitor terminal messages.

^R tries to restart the diagnostic monitor and load the appropriate overlay (CERT) from the disc. IIUC, Spildit is saying that this CERT module contains the code which is required to support the terminal commands.

[pepe]

yes, CERT is not required for the drive to work in normal mode.
Moreover, it probably was able to read CERT, but it was not compatible with rom version (perhaps fw was upgraded?) or some other error prevented loading it correctly (i have seen that too as far as i remember, but it was years ago...).

It is not impossible you will get your data off the drive, but if there is some surface damage (which is probable), torturing the drive can make it worse.
So if you are considering contacting somebody with tools and knowledge, it is time for that i think.
it's about saving 2-300 bucks or loosing 2-3 times more (risking an overall chance for recovering the data at all).

pepe

[fzabkar]

I have been trying to find a firmware update for the OP's SATA model, but all I found was the 3.07 update for the PATA version. In any case this update appears to incorporate a CERT component.

http://driverdl.lenovo.com.cn/think/download/driver/dr1240114069108/fwhd56.iso

Code:

;   Seagate :  Momentus 7200.1
;
; ST980825A 80.0GB
"ST980825A","3.06","3.07","m72307.bin","HFus429.exe","","-m m72 -b -v"
;
; ST910021A 100.0GB
"ST910021A","3.06","3.07","m72307.bin","HFus429.exe","","-m m72 -b -v"

My idea was to apply a SATA firmware update to the OP's drive, thereby ensuring that the overlays and ROM code were compatible. The OP could then have attempted Spildit's fix. This might still be possible if we can find suitable firmware resources.