Page 1 of 1
unreadable sectors on seagate st2000dl001
Posted: 05.08.13, 12:00
by farjad
I have a seagate st2000dl001 , and Firmware CC98, When i view sectors after 2000000 i got the unreadable sectors,
Anyone can help in this,
best reg.
gh. farjad
Re: unreadable sectors on seagate st2000dl001
Posted: 05.08.13, 13:05
by AJ2008
Did you rebuild translator before trying to get access?
Re: unreadable sectors on seagate st2000dl001
Posted: 05.08.13, 13:52
by farjad
no i dont rebuild translator
Re: unreadable sectors on seagate st2000dl001
Posted: 05.08.13, 13:54
by AJ2008
Probably someone has rebuilt translator and NRG is not right, or it has some level of pending bug. Do you see any information in Terminal field?
Re: unreadable sectors on seagate st2000dl001
Posted: 06.08.13, 11:11
by farjad
No, it`s empty
Re: unreadable sectors on seagate st2000dl001
Posted: 06.08.13, 11:41
by AJ2008
You are sure there is no terminal output at all?

Re: unreadable sectors on seagate st2000dl001
Posted: 06.08.13, 11:49
by farjad
Yes of course.
Re: unreadable sectors on seagate st2000dl001
Posted: 06.08.13, 12:03
by AJ2008
But you get "T>" after pressing CTRL+Z?
Re: unreadable sectors on seagate st2000dl001
Posted: 06.08.13, 12:18
by farjad
thanks, that`s write
the massege is
ASCII Diag mode
F3 T>
Spinning Down
Spin Down Complete
Elapsed Time 14.516 secs
Delaying 5000 msec
Jumping to Power On Resetÿ
Rst 0x20M
(P) SATA Reset
RAW OFF
PASS
Re: unreadable sectors on seagate st2000dl001
Posted: 06.08.13, 12:45
by AJ2008
With terminal connected, at your task in DE select 'Work with active utility' then select 'No' at the next prompt. Now try to read sectors .
Re: unreadable sectors on seagate st2000dl001
Posted: 06.08.13, 13:23
by farjad
Please Tell us more about it ( at your task in DE select 'Work with active utility' ) or how do it?
Re: unreadable sectors on seagate st2000dl001
Posted: 06.08.13, 14:04
by AJ2008
Select 'Task Parameters' -> 'Command to Read' -> 'Read from Active PC3000 utiltiy'.
Re: unreadable sectors on seagate st2000dl001
Posted: 23.08.13, 16:58
by Nick_TS
Hi,
Try to increase Terminal timeout.