Page 1 of 1
hard seagate st500dm002
Posted: 25.05.16, 09:16
by atwartec
Rst 0x10M
MC Internal LPC Process
Spin Up
SIM Error 2009
RW Error 00000080
ASCII Diag mode
F3 T> PASS
ASCII Diag mode
F3 T>
Starting LBA of RW Request=001320AE Length=00000144
ProcessRWError -Read- at LBA 001320AE Sense Code=43110081
LED:000000BD FAddr:00008A23
any one help me? this is message in terminal
Re: hard seagate st500dm002
Posted: 25.05.16, 11:39
by Filipp_TS
SIM Error 2009
RW Error 00000080
This error mean that drive have one (or more) damaged sys files.
Take a look this article
http://blog.acelab.eu.com/how-to-ch ... mmand.html and check sys files, then fix a damaged of them.
Re: hard seagate st500dm002
Posted: 25.05.16, 15:42
by atwartec
- sys.txt
- (11.16 KiB) Downloaded 953 times
When I press on Crl-z and Crl-x show this message (LED:000000BD FAddr:00008A23
) and terminal not access
Re: hard seagate st500dm002
Posted: 26.05.16, 17:49
by Garry_TS
So you need to
short read channel firstly to get a stable terminal access
Re: hard seagate st500dm002
Posted: 09.06.16, 11:53
by AJ2008
Short read channels during calibration to retain terminal access and prevent LED error. Then, at T>, you will have access to SMP where relocation and media cache can be disabled. you can also get info about error locations with CTRL+X and this could be useful in identifying any damaged system files.
Check 0x93 first, this may be ok.
Re: hard seagate st500dm002
Posted: 14.06.16, 10:27
by Amarbir[CDR-Labs]
AJ2008 wrote:Source of the post Short read channels during calibration to retain terminal access and prevent LED error. Then, at T>, you will have access to SMP where relocation and media cache can be disabled. you can also get info about error locations with CTRL+X and this could be useful in identifying any damaged system files.
Check 0x93 first, this may be ok.
AJ Sir ,
I Too Think its a SMP Issue ,But in Your Experience is There a Sys File Associated with Sim 2009 Error ?
Re: hard seagate st500dm002
Posted: 17.06.16, 09:22
by AJ2008
I do not know specifically this error code, but with T> access there are some steps that can help to identify it. There are a lot of various error codes relating to different issues with translator and processes such as reallocation and media cache, I would guess the error relates to one of these problems.