F3 RW sub file error 2044

admin

hi all
in this topic F3 RW subfile error 2044

Rst 0x10M
RW sub file error 2044
RW sub file error 2044
SIM Error 2044
No HOST FIS-Ready Status Flags 2002A1A5

HDD ID:


Model Number : ST3500418AS; Desktop- 7200.12
Family : YETIST_3_0(649B)(3-12-3-3)
Firmware version: CC37
Head Number: 2
Capacity: 976773168 (500G)
S/N  : 5VM3EZWL


F3 T>
ASCII Diag mode
F3 T>/1


F3 1>N1,,22


Init SMART Fail
LED:000000CC FAddr:0024E4A3
LED:000000CC FAddr:0024E4A3
LED:000000CC FAddr:0024E4A3
LED:000000CC FAddr:0024E4A3


LED:000000CC FAddr:0024E4A3
LED:000000CC FAddr:0024E4A3


F3 T>m0,6,3,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 16, Max Certify Rewrite Retries = 2DF8


DiagError 0000500D
User Partition Format Failed – Elapsed Time 0 mins 00 secs
R/W Sense 00000002, R/W Error 843200A6, File Error 00000000
Blk Addr 71030001, Blk Addr Type D0, Cyl 00000000, Hd 1B


F3 T>
ASCII Diag mode


F3 T>m0,2,1,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 16, Max Certify Rewrite Retries = 2DF8


User Partition Format   3% complete, Zone 00, Pass 00, LBA 00009A64, ErrCode 00000080, Elapsed Time 0 mins 30 secs
User Partition Format Successful – Elapsed Time 0 mins 30 secs
Zone re-format was skipped

!guest!!post_hide_reply_hidden!

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000


DiagError 0000500D
User Partition Format Failed – Elapsed Time 0 mins 00 secs
R/W Sense 00000002, R/W Error 843200A6, File Error 00000000
Blk Addr 71030001, Blk Addr Type D0, Cyl 00000000, Hd 02


F3 T>
ASCII Diag mode


F3 T>/1


F3 1>N1,,22


Clear SMART is completed.


F3 1>
ASCII Diag mode


F3 T>m0,2,1,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 16, Max Certify Rewrite Retries = 0A74


User Partition Format   3% complete, Zone 00, Pass 00, LBA 00009A64, ErrCode 00000080, Elapsed Time 0 mins 30 secs
User Partition Format Successful – Elapsed Time 0 mins 30 secs
Zone re-format was skipped.
F3 T>


Power off and power on, the error was gone and the drive was scanned