PC-3000 Forum

Dear Gurus
This hard disk ( attached snap) gives - SMART Bad +High Reallocated sector count in DOS smart test.
In udma express it gets detection and shows following Terminal. I could Image disk but suddenly it starts giving bad sector & only after restarting I could continue work again.
Since last sector is accessible I cant recover translator.
Can someone pls. suggest what I should do ? Thank you

Send Status: COMRESET seen
Set Transfer Mode selected
Ultra DMA selected
Set Transfer Mode selected
Starting LBA of RW Request=0E243FE5 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0E244028 Sense Code=43110081
Starting LBA of RW Request=0E243FE5 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0E244098 Sense Code=43110081
Starting LBA of RW Request=0E243FE5 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0E24409A Sense Code=43110081
Send Status: COMRESET seen
(S) SATA Reset

Send Status: COMRESET seen
(S) SATA Reset

Send Status: COMRESET seen
(S) SATA Reset

Send Status: COMRESET seen
(S) SATA Reset

First off, try doing slow responding fix which will disable the auto re-allocation function, then clear SMART and see if that helps. Then you might want to check the health of the SA modules. Possibly there's a module that's damaged and is accessed when the drive hits a bad sector causing it to crash out.

DataMedics wrote:Source of the post First off, try doing slow responding fix which will disable the auto re-allocation function, then clear SMART and see if that helps. Then you might want to check the health of the SA modules. Possibly there's a module that's damaged and is accessed when the drive hits a bad sector causing it to crash out.

Haaaaa ,
What are you talking about ,This is a seagate not a western digital hdd that he is talking about .Slow fix is not applicable to this drive .Athena Please Disable Most of The Seagate Auto Relocation Correction Features As Described In This Document - > http://blog.acelab.eu.com/pc-3000-h ... issue.html . If you can read first and last sector of the drive then its not at all a translator issue ,Do not jump into translator functions for no reason .I see that you are using selective head imaging and selective file imaging .I this case disable all heads but one and do file imaging once that head is done enable next head and do same,Once you find problem head you can skip some files .Let me know if you need help i am online most of the time from 10:30 to 5:30 daily and would like to provide support to any PC 3000 User in India Who wants me to butt in .My Skype id is lynx-india .I do not claim to be a expert but i am better then 75% of them here

Thank You all for the kind help.

Amarbir[CDR-Labs] wrote:Source of the post

DataMedics wrote:Source of the post First off, try doing slow responding fix which will disable the auto re-allocation function, then clear SMART and see if that helps. Then you might want to check the health of the SA modules. Possibly there's a module that's damaged and is accessed when the drive hits a bad sector causing it to crash out.

Haaaaa ,
What are you talking about ,This is a seagate not a western digital hdd that he is talking about .Slow fix is not applicable to this drive .Athena Please Disable Most of The Seagate Auto Relocation Correction Features As Described In This Document - > http://blog.acelab.eu.com/pc-3000-h ... issue.html . If you can read first and last sector of the drive then its not at all a translator issue ,Do not jump into translator functions for no reason .I see that you are using selective head imaging and selective file imaging .I this case disable all heads but one and do file imaging once that head is done enable next head and do same,Once you find problem head you can skip some files .Let me know if you need help i am online most of the time from 10:30 to 5:30 daily and would like to provide support to any PC 3000 User in India Who wants me to butt in .My Skype id is lynx-india .I do not claim to be a expert but i am better then 75% of them here

HAHA, that's why I shouldn't be browsing forums while I'm working on other projects....got WD on my brain and forgot what drive you were working on . Yeah, tweaking system file 93 is where to start.

DataMedics wrote:Source of the post

Amarbir[CDR-Labs] wrote:Source of the post

DataMedics wrote:Source of the post First off, try doing slow responding fix which will disable the auto re-allocation function, then clear SMART and see if that helps. Then you might want to check the health of the SA modules. Possibly there's a module that's damaged and is accessed when the drive hits a bad sector causing it to crash out.

Haaaaa ,
What are you talking about ,This is a seagate not a western digital hdd that he is talking about .Slow fix is not applicable to this drive .Athena Please Disable Most of The Seagate Auto Relocation Correction Features As Described In This Document - > http://blog.acelab.eu.com/pc-3000-h ... issue.html . If you can read first and last sector of the drive then its not at all a translator issue ,Do not jump into translator functions for no reason .I see that you are using selective head imaging and selective file imaging .I this case disable all heads but one and do file imaging once that head is done enable next head and do same,Once you find problem head you can skip some files .Let me know if you need help i am online most of the time from 10:30 to 5:30 daily and would like to provide support to any PC 3000 User in India Who wants me to butt in .My Skype id is lynx-india .I do not claim to be a expert but i am better then 75% of them here

HAHA, that's why I shouldn't be browsing forums while I'm working on other projects....got WD on my brain and forgot what drive you were working on . Yeah, tweaking system file 93 is where to start.

Jared ,
Did you notice something i never laughed i just said Haaa Cos i was sure you got more WDC rolling in your office then seagates this Day As a DR Guy Of Your Caliber Cannot Make Such a Silly Mistake ,Cheers Bro

Hi
As Jared suggested I tried to read system file 93 but getting error while opening & system files are not readable as well. . Also getting buffer related error.What should be by further course of action.

Terminal shows --

Send Status: COMRESET seen
Set Transfer Mode selected
Ultra DMA selected
Set Transfer Mode selected
Starting LBA of RW Request=0BDC3E78 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0BDC4096 Sense Code=43110081
Unrecoverable Error Reported
(S) SATA Reset

Wyatt family drives have 8F sys file with SMP flags (not 93).

Athena wrote:Source of the post Hi
As Jared suggested I tried to read system file 93 but getting error while opening & system files are not readable as well. . Also getting buffer related error.What should be by further course of action.

Terminal shows --

Send Status: COMRESET seen
Set Transfer Mode selected
Ultra DMA selected
Set Transfer Mode selected
Starting LBA of RW Request=0BDC3E78 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0BDC4096 Sense Code=43110081
Unrecoverable Error Reported
(S) SATA Reset

Hi Athena,
When You start a Drive In Seagate F3 Utility You Can See a List scrolling very fast "You should check it sometimes " ,This Many times Give a Clue if there is Difference Like System File 93 Not Doing This in Family As TS Tech Fillip Said .

Filipp_TS wrote:Source of the post Wyatt family drives have 8F sys file with SMP flags (not 93).

Filipp ,
Thanks for This Info "Something to Remember "

Thanks Filipp & Amarbir
Guys I can access System 8F ,but disk is reading slow with lots of defects. I must fix this issue as I think origin of bad sectors is in system files /SA

Athena wrote:Source of the post Thanks Filipp & Amarbir
Guys I can access System 8F ,but disk is reading slow with lots of defects. I must fix this issue as I think origin of bad sectors is in system files /SA

Well,
How do You Plan To Fix This Tell Us Your Method Might Be i Can share My thoughts Then

HI Good Morning.
This seems to be "7200.12 Sector Access Interruption " issue. So far I have reset smart and erased non resident G-list.
Since this is system file related issue , some technique must be used to identify why system files cant be read. I will have to read manuals so as to find solution for this issue,

I can read system file 35 , I think this issue revolves around this file. I tried to copy it from other disk of same family but after that symptoms become worse & I was forced to restore earlier backup.
What to do now ?

Hello Athena,

Athena wrote:Source of the post I can read system file 35 , I think this issue revolves around this file. I tried to copy it from other disk of same family but after that symptoms become worse & I was forced to restore earlier backup.
What to do now ?

Non-resident G-list is located in 26 system file on Wyatt family. But I'm not sure that problem is related to defect in NRGL.
Does drive still work slowly after cleaning SMART and unchecking background processes?