General (and not general)Seagate questions - for everyone :)

[N.C.]

Janos ,
I Have a Stupid Question what Imaging Software/Hardware You Are trying

Amarbir,

I am using own solution.
I always image under Linux, with my patched kernel (retry removed), and one own wrote script, wich uses dd_rescue in the core.

It can do all the needed steps, like jumping sectors, read forward, backward, continue, force the bb area, the only one thing, wich it does not supports, the ECC ignore reading.

But generally, it is not needed.
Anyway, i have other solution in these cases, if it is needed.

(the case, in the first post is already recovered, but for interesting testing, i still have the drive, so the original question is still actual. )

Thanks,
Janos

[BlackST]

I have already pointed out what seems to be ignored : commercial available tools , on which the majority of repair shops and DR rely on, are only tools to access the SA or firmware zone, driven by human beings. We have to use our logic skill / capabilities, unless it is a simple, "clickable" solution.
What's worst, the more I go further researching and experimenting, the more I can do without those expensive tools. The DR is moving to phisycal, hands-on-drive level, and if you really want to do magic, if you know sufficiently how things work, you can write down your own tools even in Turbo Pascal (maybe forgetting GUI but who cares ?). Enough said.

[N.C.]

Agree.

[N.C.]

I have read back the first 20 posts now.

Doomer, Amarbir

This is a technical forum, so please see the posts like this way, and if somebody have any problem with each other, please discuse the problems in PM, please!

Doomer, thank you for the answer, i will try it if i have a little time for learning.

Can you say for me, exactly wich step in error handling is wrong?
If i trying to disable the steps, wich is what i need to disable?

Btw, the error correcting attempts, is important in DR, so skip this step causes lower imaging quality....

Thanks,
Janos

[shahij]

custom made tools best to perform. but commercial tools give us more ease, time consuming solution to perform.

[Doomer]

Can you say for me, exactly wich step in error handling is wrong?
If i trying to disable the steps, wich is what i need to disable?

I doubt it is possible with dd
the idea was in sending software reset as soon as possible when drive found a bad block (stays in busy too long)
But as far as I know dd cannot send software reset

[N.C.]

Can you say for me, exactly wich step in error handling is wrong?
If i trying to disable the steps, wich is what i need to disable?

I doubt it is possible with dd
the idea was in sending software reset as soon as possible when drive found a bad block (stays in busy too long)
But as far as I know dd cannot send software reset

Yes, i know, what you talking about.
No, dd don't send any sw reset, the kernel does it, when the drive don't respond in the timeout period.

Maybe i can set up the drive for using individual error handling solutions, like ECC retries, seek off-and back count, trying to read off-track, and similar.
This is why i am asking, wich attempt causes the fw bug, if you know the answer....

The interesting part, on exactly the same block, in the beginning, the drive can read the content during the error-handling code runs, and i can mount up the partition.
But after it crashed once, the drive almost immediately hung again, if i trying to mount again.
(of course, i am working on readahead = 0, and readonly the whole drive...)

Thanks,
Janos

[mukesh_raval]

USE HARD DISK REGENERATOR IT WILL REMOVE BAD SECTOR OF UR HDD

[BlackST]

USE HARD DISK REGENERATOR IT WILL REMOVE BAD SECTOR OF UR HDD

Are you REALLY sure ?

[shahij]

USE HARD DISK REGENERATOR IT WILL REMOVE BAD SECTOR OF UR HDD

Do you know the definition of BAD Sector?

[N.C.]

USE HARD DISK REGENERATOR IT WILL REMOVE BAD SECTOR OF UR HDD

Do you know the definition of BAD Sector?

[Amarbir[CDR-Labs]]

Mates ,
Always Boasting Of Custom Made solution is Not good .More of these solutions Apply to the Physical Data Recovery Aspect and Very Little To Software ,Since the last time i visited here its more of a i have a NDA ,I Have a customs tool Of this and That Well Use Your Brain Get More Practice and Other Nonesense .What Are We Fellows Upto .If You People Have custom Tools Just Use Them Do Not Boast Of them And If You Say You Have Sown It and Prove It .Otherwise Please Learn and Learn and Learn Like I Do

[Amarbir[CDR-Labs]]

Hello Gurus,

Let me start the questions:

I have one ST3300931A, with a lot of bad sectors (not exactly in fixed place), and when i trying to image, i have got this message on the terminal:

.....
ATA St d0 Er 40 Op 25 e, 699cc4f,0800 0800 0000
Niwot: 00013d00 ae 00013d00.0.036 0000 110e 0000 5901
AT Er 00 Nwt Er 43 RdWr 0435a.00.02f9
ATA St d0 Er 00 Op 25 e, 6ec0087,0800 0700 0000
Niwot: 06ec0087 3a 06ec0087.0.0c0 8000 19b3 07fe 0000

CE Log EC=43 Rtype=6 OV=0 STStatus0
AutoRd Err 43 at ffffffff.00.0081

Read Ver Retrys
AutoRd Err 43 at ffffffff.00.0081

Read Ver Retrys
AutoRd Err 43 at ffffffff.00.0081

Read Ver Retrys
AutoRd Err 43 at ffffffff.00.0081

Read Ver Retrys
AutoRd Err 43 at ffffffff.00.0081

Read Ver Failure!
Failed sys sect. write
Not handled software path:

This point the drive is knocks one big, and stay BSY forever.

Now, the drive can init again, but very soon drops this issue again, so, in this way, i can't countinue the imaging without hw controll....

Somebody have any suggestion?

Thanks,
Janos

Nc ,
I Had Asked You something In My first Post To You ,Can You answer That Please]

[N.C.]

Mates ,
Always Boasting Of Custom Made solution is Not good .More of these solutions Apply to the Physical Data Recovery Aspect and Very Little To Software ,Since the last time i visited here its more of a i have a NDA ,I Have a customs tool Of this and That Well Use Your Brain Get More Practice and Other Nonesense .What Are We Fellows Upto .If You People Have custom Tools Just Use Them Do Not Boast Of them And If You Say You Have Sown It and Prove It .Otherwise Please Learn and Learn and Learn Like I Do

Excuse be, but you was, who asked the solution about imaging.
In this way comes out the custom made solutions.....

Janos

[N.C.]

Nc ,
I Had Asked You something In My first Post To You ,Can You answer That Please]

I Think i have already done this, on the 20th post.
Or not?

Janos

[BlackST]

Amarbir, you know me outside this forum and 'you know'. Me and other people who have developed custom solutions are not going to post any 'proof' maybe because we don't want to self-jeopardise our market - that, if not far west, it is close to. Commercial solutions are commercial, custom are more like capital assets. And NO, info won't leak - just to make someone disappointed. I am somewhat different from other people, and I know it, but common sense is common.

[guru]

so is the problem sorted?

[Amarbir[CDR-Labs]]

so is the problem sorted?

Well ,
We all started a fight Before That

[N.C.]

Hello gurus,

Now I am trying to selfscan one 7200.7 (PUMA) drive.
The selfscan started good, but after some hours, I can see the drive gets in endless loop in test 40.

....
Quick Error Rate cyl 164D8
Rbit Hard Firm Soft OTF Raw Rhdr Wbit Whrd Wrty Whdr
Limit 10.2 10.2 9.5 8.0 0.0 3.9 7.4 9.2 9.2 6.5 7.4
Hd 0 8.6 8.6 8.6 8.6 8.6 6.1 8.6 8.3 8.3 8.3 8.3
Hd 1 8.6 8.6 8.6 8.6 8.6 6.8 8.6 8.3 8.3 8.3 8.3

OTC characterization
Track 0130D
______ISO_____ ______PE______ ______OTC_____
Head Sctr Min Wid Sctr Min Wid Sctr Min Wid
0 2260 000C 0031 2260 0019 001D 2260 0022 0025
1 2260 0018 0023 2260 0058 0002 2260 0048 000D

OTC characterization
Track 164D8
______ISO_____ ______PE______ ______OTC_____
Head Sctr Min Wid Sctr Min Wid Sctr Min Wid
0 203a 0029 0023 203a 0038 000F 203a 002B 001D
1 203a 0001 0045 203a 0004 002F 203a 0004 0035

Power Cycling
ASCII logging off
OkEnd Test 58
Begin Test 40
ASCII logging on
Head Mask FFFF - Switch to full int.
Spin Ready
Head Mask FFFF - Switch to full int.
Spin Ready
Head Mask FFFF - Switch to full int.
Spin Ready
Head Mask FFFF - Switch to full int.
Spin Ready
Head Mask FFFF - Switch to full int.
Spin Ready
Head Mask FFFF - Switch to full int.
Spin Ready
....

At this point, I have switched off the power and on again.
The drive shows this:

4096k x 16 buffer detected
PUMA - 1_Disk M-22d 11-11-04 10:47

Buzz - Head Mask FFFF - Switch to full int.
Spin Ready
3.43 01-26-05 16:23
(P)(H)SATA Reset
Not Interface Age!
VALID Cert Disk Code Detected - Revision # .083
Cert Table loaded
No script first instruction.
No valid SeaDex script on disc.
Begin Test 40
ASCII logging on
Head Mask FFFF - Switch to full int.
Spin Ready
Head Mask FFFF - Switch to full int.
Spin Ready
...

I have changed the AGE from 40 to 41.
The test continues, but i am not sure on the right way.
Now the drive is on this state after more than 24 hour:

.....
Begin Test 49
ASCII logging on
ASCII logging off Not Power Cycling
ASCII logging on
EP=1, TA=1, HiGain=1, OTRd=1, Early Rd=0, Splash=1, Reload=1, NPML=1, MRBias=1
Bst/Zap=1, SrvoThrsh=1, RunOut=1, MaxECC=0, ECC 2=0, ECC 1=1, ECC 0=1
Data=40, Write=80, ID=FF
ASCII logging off
All Hds 0-1, All Cyls 00018-164F8, Rnd data
EP=1, TA=1, HiGain=1, OTRd=1, Early Rd=0, Splash=1, Reload=1, NPML=1, MRBias=1
Bst/Zap=1, SrvoThrsh=1, RunOut=1, MaxECC=0, ECC 2=0, ECC 1=1, ECC 0=1
Data=40, Write=80, ID=FF
ASCII logging on
Score= : #
Measured spin speed: 407 ticks per rev (48 ticks per millisecond)
EndLBA,Pred,Act,%Deg,Score

(only repeate noise, no more messages)

Somebody can help me how to step back to the normal way of ss?

Thanks!

Janos

[ccc]

Hi
Try to press "." several times to see if it's doing something or not....As far as I know this is a long test but 24 hour(for 2 heads) is too long...something is wrong there...
And are you sure that after test 40 comes test 41?...look in log 4e to see the test sequence...

Rgds