Page 1 of 1

ABORT! SenseCode from a drive that was reading well but now not all

Posted: 14.03.17, 19:54
by osity
I was originally able to read most sectors but eventually hit a large rough (timeout) patch with H2 and H3.
It seemed to stop reading completely shortly after clearing SMART and/or G list (T>i4,1,22). I did both.

Now, none of the heads read anything and I get this in terminal when I start the utility.

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5


Any ideas what this error indicates?
Could the clear G list command be the cause of the heads no longer reading user area?


Currenty the drive comes ready with Full ID.
Tested heads with X and output is fine.
I am able to read system files fine.
All critical modules are good.

is there anything I can try?

Re: ABORT! SenseCode from a drive that was reading well but now not all

Posted: 16.03.17, 19:55
by osity
Head 00 Resistance 01F5
Head 01 Resistance 01A6
Head 02 Resistance 01D5
Head 03 Resistance 01D2

Re: ABORT! SenseCode from a drive that was reading well but now not all

Posted: 22.03.17, 04:12
by Amarbir[CDR-Labs]
Well,
The First Thing You All Do is Attach Smart Module And Clear It and Also Growing Defect Lists ,Mostly They Are Never a Issue

Re: ABORT! SenseCode from a drive that was reading well but now not all

Posted: 23.03.17, 15:03
by osity
Amarbir,
What do you mean "attach smart module"? Are you suggesting I clear smart and G-list again?

Re: ABORT! SenseCode from a drive that was reading well but now not all

Posted: 02.04.17, 10:41
by Amarbir[CDR-Labs]
osity wrote:Source of the post The First Thing You All Do is Attach Smart Module And Clear It and Also Growing Defect Lists ,Mostly They Are Never a Issue


Sorry ,
There was a Typo Error ,I Wanted To Say "The First Thing You All Do is Attack/Clear Smart Module And Clear It and Also Growing Defect Lists ,Mostly They Are Never a Issue "