Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Slow responding ST1000DM003

July 12th, 2018, 7:42

Hey,

can some one help me out? I have a Seagate ST1000DM003 drive. The drive initialises normally, but stays busy for a while.

The first thing I did was, I patched sysfile 93. After the patch, the drive gets ready right after initialisation, but when I try to read the drive id, again I get the busy signal. Can some one tell me, what I can try?

Re: Slow responding ST1000DM003

July 12th, 2018, 7:55

If you can publish the terminal report it will help diagnose the problem,

Maybe a problem with the DOS table?

Re: Slow responding ST1000DM003

July 12th, 2018, 8:01

colanco wrote:If you can publish the terminal report it will help diagnose the problem,

Sure and thank you for your help:
Code:
Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
(P) SATA Reset

RAW OFF
PASS
MCMainPOR: Start:
User Data Base  00441140
Check MCMT Version: Current
MCMainPOR: MCTStateFlags 0000002A  MCStateFlags 000000C1
MC061: MainPOR: MC off and MCMT empty
MC057: MainPOR: EXCEPTION: POR Failed General  Tms 00000040
MC062: MainPOR: Feature Disabled...
MSP MainPOR: Feature Disabled by AMPS
6Gb Max Speed lowered to 3Gb for Intel bug
Send Status: COMRESET seen


FYI, I set the additional messages flag in the sysfile 93. And that's it.

Re: Slow responding ST1000DM003

July 12th, 2018, 13:26

What tools do you have?

Re: Slow responding ST1000DM003

July 12th, 2018, 13:27

colanco wrote:What tools do you have?


PC3k

Re: Slow responding ST1000DM003

July 12th, 2018, 14:31

Do you have access to a terminal?

Have you checked that glist is not full?

Re: Slow responding ST1000DM003

July 13th, 2018, 5:14

Yes, I have access to the Terminal.
I checked the G-List and it was full, so I cleared it with i4,1,22

After this, I was able to access the User Area. Currently I have the problem that the drive is still relocating the sectors, right after I powered the drive on and while imaging. Even though I have turned auto relocation off in edit HDD ID.

Code:
(DOS) Read Error - 43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0007A97A53!
(DOS) Read Error - 0007A97A53
WTR: Outer Timer Expired
(DOS)ABT
(DOS) NEED: 0x0007A97A54-0007A980DB - 0x00023D93-00023D96 Count 2098
(DOS) Refresh Start.
(DOS) Marginal Read: 0007A97A54
(DOS) Read Error - 43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0007A97A54!
(DOS) Read Error - 0007A97A54
WTR: Outer Timer Expired
(DOS)ABT
(DOS) NEED: 0x0007A97A55-0007A980DB - 0x00023D93-00023D96 Count 2098
(DOS) Refresh Start.
(DOS) Marginal Read: 0007A97A55
(DOS) Read Error - 43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0007A97A55!
(DOS) Read Error - 0007A97A55
WTR: Outer Timer Expired
(DOS)ABT
(DOS) NEED: 0x0007A97A56-0007A980DB - 0x00023D93-00023D96 Count 2098
(DOS) Refresh Start.
(DOS) Marginal Read: 0007A97A56
(DOS) Read Error - 43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0007A97A56!
(DOS) Read Error - 0007A97A56
WTR: Outer Timer Expired
(DOS)ABT
(DOS) NEED: 0x0007A97A57-0007A980DB - 0x00023D93-00023D96 Count 2098
(DOS) Refresh Start.
(DOS) Marginal Read: 0007A97A57
(DOS) Read Error - 43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0007A97A57!
(DOS) Read Error - 0007A97A57
WTR: Outer Timer Expired
(DOS)ABT
(DOS) NEED: 0x0007A97A58-0007A980DB - 0x00023D93-00023D96 Count 2098
(DOS) Refresh Start.


And after a while the G-List is full again.

Re: Slow responding ST1000DM003

July 13th, 2018, 14:58

Can I see 2a(93)?

Re: Slow responding ST1000DM003

July 13th, 2018, 21:26

D_R wrote:And after a while the G-List is full again.
Unfortunately, this is what it is (it is a SEAGATE drive....)
drHDD wrote:Even though I have turned auto relocation off in edit HDD ID.

This helps, but disabling the relocation will not make the damaged sectors disappear.

Change the head block, you can check them out, I don't think it's going to get much better either.....
D_R wrote:I powered the drive on and while imaging
Unless you want to recover 1TB of data (or nearby) you would also not try to make a full-image of this drive, you may die in the attempt.

It would be better to clone at the same time as the important data is being retrieved, the first pass with very short waiting times and the next passes increasing the waiting time ( and refreshing all sectors except those read successfully).

Every now and then when the G-list is full, then re-clean and continue with the recovery.....

Good luck, you'll need it.

Re: Slow responding ST1000DM003

July 15th, 2018, 8:15

drHDD wrote:Can I see 2a(93)?


Sure....

colanco wrote:Good luck, you'll need it.


Thank you for the support!
Attachments
93.bin.zip
(1.71 KiB) Downloaded 338 times

Re: Slow responding ST1000DM003

July 15th, 2018, 21:35

try this one
Attachments
93.7z
(946 Bytes) Downloaded 364 times
Post a reply