F3 1>N5 reads SMART

(tested on another drive, now to look at this 2TB one)

Slowly remembering this stuff

and that the following will show the commands the drive understands
F3 C>Q

Finally getting somewhere now
^Z
^R to put in ascii online mode, and get lots of errors

ASCII Online mode

(DOS)STE NEED: 0x039A3533 - 0x039A4570
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 039A354B!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 039A3569!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 039A356A!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 039A356B!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 039A356C!
(DOS) Write Error

(DOS) Write Failure Reallocation started.
(DOS) AutoWriteReallocationEnabled and Reallocation Request Issued. !84320091
(DOS) WriteFailureReallocateLBARequest is executed successfully.
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 039A356E!
(DOS) Write Error

(DOS) Write Failure Reallocation started.
(DOS) AutoWriteReallocationEnabled and Reallocation Request Issued. !84320091
(DOS) WriteFailureReallocateLBARequest is executed successfully.
(DOS) Write Error

(DOS) Write Failure Reallocation started.
(DOS) AutoWriteReallocationEnabled and Reallocation Request Issued. !84320091
(DOS) WriteFailureReallocateLBARequest is executed successfully.
(DOS) Write Error

(DOS) Write Failure Reallocation started.
(DOS) AutoWriteReallocationEnabled and Reallocation Request Issued. !84320091
(DOS) WriteFailureReallocateLBARequest is executed successfully.
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 039A3572!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 039A3573!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 039A3574!
(DOS) Write Error

and loads more
disc_lba only slowly creaping up
up to 039A3916 after 10+ minutes

Raw reading of SMART
F3 1>N5
Att
Num Flgs normlzd worst raw
1 000F 6D 63 000000374AFBC4
3 0003 5E 5C 00000000000000
4 0032 64 64 00000000000319
5 0033 5F 3 00000000000F18
7 000F 3C 3C 0000000010E339
9 0032 64 64 0000000000005C
A 0013 64 64 00000000000000
C 0032 64 64 00000000000318
B7 0032 64 64 00000000000000
B8 0032 64 64 00000000000000
BB 0032 48 48 0000000000001C
BC 0032 64 64 00005900600071
BD 003A 64 64 00000000000000
BE 0022 44 2F 00000080800020
BF 0032 64 64 00000000000000
C0 0032 64 64 000000000002E7
C1 0032 64 64 0000000000031B
C2 0022 20 35 00000000000020
C3 001A 1D 17 000000374AFBC4
C5 0012 64 64 00000000000018
C6 0010 64 64 00000000000018
C7 003E C8 C8 00000000000000
F0 0000 64 FD 101C4F0000005C
F1 0000 64 FD 0000004AF4D6D0
F2 0000 64 FD 000000506638AA
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000

not examined this yet, but probably shows lots of reallocated or pending realloc


Anything I can do to force it ready, so as to try to see what is readable ?

Or way to read the user sectors (as best I can) from the terminal

F3 2>l0 doesn't seem to be showing me where user sector 0 is
seems to say its at LBA/PBA 0 (maybe it is)

Hmm, two search hits on STE NEED
neither sounds too promising

F3 T>V
User Slip Defect List

lots

Head 0: entries 660 slips A0E
Head 1: entries 511 slips 1496
Head 2: entries 184 slips 372
Head 3: entries 33A slips 8B1
Head 4: entries 588 slips 8C6
Head 5: entries 3F1 slips 809
Total Entries 19A8 Total Slips 3B96

Is that excessive for a 2TB drive ?

what are slips and why more of them than the entries ?


This also shows the last LBA is approx. 1D29AA32
which means the LBA's must be 4K in size ?
and even that doesn't quite add up to '2TB'
Can anyone confirm ?

Well this is all good practice and interesting

F3 2> ^L shows

Banshee Bogart, RAP17, add 6k SAP csys 4K QNC
Product FamilyId: 4F, MemberId: 02
HDA SN: 5YD55B84, RPM: 5939, Wedges: 1F8, Heads: 6, OrigHeads: 6, Lbas: 00001D326C41, PreampType: A8 05
PCBA SN: 0000K206KNNV, Controller: BANSHEEST_2_0(8000)(4-00-0-0), Channel: Unknown, PowerAsic: MCKINLEY DESKTOP LITE Rev
91, BufferBytes: 2000000
Package Version: BGC15D.CCD4.BH048N.CC43 , Package P/N: 100674525, Package Global ID: 00188399,
Package Build Date: 05/20/2011, Package Build Time: 14:14:33, Package CFW Version: BGC1.CCD4.00359386.00188399,
Package SFW1 Version: D55E, Package SFW2 Version: ----, Package SFW3 Version: ----, Package SFW4 Version: ----
Controller FW Rev: 05201414, CustomerRel: CC43, Changelist: 00359386, ProdType: BGC1.CCD4, Date: 05/20/2011, Time: 14143
3, UserId: 00188399
Servo FW Rev: D55E
RAP FW Implementation Key: 11, Format Rev: 0302, Contents Rev: BB 03 09 00
Features:
- Quadradic Equation AFH enabled
- VBAR with adjustable zone boundaries enabled
- Volume Based Sparing enabled
- IOEDC enabled
- IOECC enabled
- DERP Read Retries enabled
- LTTC-UDR2 compiled off

The 4K QNC at the end of the top line suggest 4K physical
as does Lbas: 00001D326C41 (of 4K)

Theres nothing on the label to say 4K or 512E or advanced format

If/when I can get it ready, we will see what it reports to the sata/ATA interface

For info a 500GB 7200.12 shows
(different name etc)
Lbas: 00003A386050 of 512 bytes = 465GB

I now have a brand new, good, ST3000DM001
doesn't mention 4k but is 4K (native or 512e?)

Terminal shows
GrenadaBP LuxorPlus2 4K
Lbas: 00002BB5420C
so internally 4K

Drive passport through ata/sata interface using older tools shows
5860533168 LBAs (decimal) 2.8GB
implying its doing 512e

Windows Server 2008R2 which knows about 4K drives shows it as
Bytes Per Sector : 512
Bytes Per Physical Sector : 4096
ie 512e


For info F3 T>V shows
Total Entries 5D25 Total Slips 52A92 ! so looks like those sort of numbers are normal

That's showing 3864 (= 0xF18) Reallocated Sectors, 28 Reported Uncorrectable Errors, 24 Pending and Uncorrectable Sectors, and about 100 Command Timeouts.

_________________
A backup a day keeps DR away.

0x1D29AA33 x 4096 = 2 004 049 145 856

http://www.google.com/search?q=0x1D29AA ... in+decimal

_________________
A backup a day keeps DR away.

i have its solution mail me
waqasali766@hotmail.com

Friendly request / reminder

Anyone any ideas how to get the drive to skip reallocation and go ready
so I can try to extract any readable sectors

^Z
^R to put in ascii online mode, and get lots of errors
ASCII Online mode

(DOS)STE NEED: 0x039A3533 - 0x039A4570
..
InitiateMarkPendingReallocateRequest for disc_lba: 039A356B!
(DOS) Read Unrecoverable Error
InitiateMarkPendingReallocateRequest for disc_lba: 039A356C!
(DOS) Write Error
(DOS) Write Failure Reallocation started.
(DOS) AutoWriteReallocationEnabled and Reallocation Request Issued. !84320091
(DOS) WriteFailureReallocateLBARequest is executed successfully.
(DOS) Read Unrecoverable Error
etc etc

i have commands to disable relocation of 7200.11 12 13 14 hdd. kinldy mail me to my eamil address. no private msg me here . because i cannot reply privete msg here . dont know why . but there is no reply button for me in the forum .

BUSY, cant access SMART in MHDD.
Heads ?

terminal:

Boot 0x20M
Spin Up[0x000246DF]
Trans.

Rst 0x20M
MC Internal LPC Process
Spin Up
(P) SATA Reset

MediaPartition:

Host LBA Length Disc LBA Length Start Cyl Head
Media Partition 00000000 00999A80 00000000 00133350 00000000 00000000
MC 00000000 0098A120 00000000 00131424 00000000 00000000
MSP 009917E0 00000BE0 001322FC 0000017C 000003CB 00000001
User Partition 00999A80 00133350 000003C0 00000001

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MC Seg Disc and Cache Nodes: 40134924 40132A34
Seg Write Preamble VBM start: 000011B2 end: 000011D9
Footer - start: 000011DB end: 00001202
Seg Read Preamble VBM - start: 00001204 end: 0000122B
Footer - start: 0000122D end: 00001254
Reconstruction: MCMT Reconstruction Start
Max number of MC segments 22E0
Nonvolatile MCMT sequence number 00366DD7
[RSRS] 07D6 DiscLba 00044908 RW_RTL FFFFFFFF
Reconstruction: Completed 1:
[MCMTWS]
MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = 00000041
MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000002A
MCMainPOR: MCStateFlags = 00000041

MCMainPOR: Feature Enabled...


MSP MainPOR:
MSP Init Metadata
Buf Bytes/VBM 00000210 DBA Base 40000000
Metadata size in bytes 0040
Num Segments 005F
Logical Sector Alignment 00000000
MSP Reconstruction
MSP Read ScratchPad Section 0000 DiscLBA 001322FC BlkSize 00000BE0 Num Segments 0000005F DiscLba 001322FC RW_RTL 000F4240
No valid segments found

MSP MSP Main Store Verify Reconstruction Status 10003000
Reconstruction Status 00003000
MSP Init ScratchPad on DiscDiscLBA 001322FC DiscSize 0000017C PhyBlkLBA 009917E0 BlkSize 00000BE0
Write MSP Segment PhyBlkLBA 009917E0 BlkSize 00000BE0 DiscLba 001322FC RW_RTL FFFFFFFF
MSP MainPOR: Complete
MSP MainPOR: Feature Enabled...
ScratchPad restore NOT required

[SR] 0000
[SR] 0000
[SR] 0000
[SR] 0000
[SR] 0000
(DOS)STE OGHT: 0x051CCBE1 - 0x051CE803 - 0x00013873 - 0x00013887 Count 006A
(DOS) Refresh Start.
(DOS) Read Error -
InitiateMarkPendingReallocateRequest for disc_lba: 051CD7F0!.
(DOS) Read Error -
InitiateMarkPendingReallocateRequest for disc_lba: 051CD7F1!.
(DOS) Read Error -
InitiateMarkPendingReallocateRequest for disc_lba: 051CD7F2!.
(DOS) Read Error -
InitiateMarkPendingReallocateRequest for disc_lba: 051CD7F3!.
(DOS) Read Error -
InitiateMarkPendingReallocateRequest for disc_lba: 051CD7F4!.
(DOS) Read Error -
InitiateMarkPendingReallocateRequest for disc_lba: 051CD7F5!.
(DOS) Read Error -
InitiateMarkPendingReallocateRequest for disc_lba: 051CD7F6!.
(DOS) Read Error -
InitiateMarkPendingReallocateRequest for disc_lba: 051CD7F7!.
(DOS) Read Error -
InitiateMarkPendingReallocateRequest for disc_lba: 051CD7F8!.
(DOS) Read Error -


Report this post

for this problem first u need to short the pcb with reading points. when (sata reset) appear in terminal short the pins. if u dont know the pins then send me the picture of pcb from both sides .
then u need to follow 0 capacity manual .
then disable relocation.
then u able to recover data .
thanks.

Dear Friend kowalski

Your Problem Is Easy If You Know And Skill To Identify Errors.
100% Some One Regen The Traslator On This Drive.
Your Drive Have The Partial Sector Accesibility Issue In UDMA Its Broken traslator Problem.
Dont Crush Your Drive If You Dont Know How To Hangle This F3 Drive.
Contact Any Pro.
I Have Fixed Lots Of Drive With This And Other JC44,JC45,KC44,KC45 And This Whole Series. With 100% Gurented Data Recovery. Dont Mess With F3 If You Dont Know What You R Doing Its Not 7200.11 Tipical Problem.

Sorry For My Bad English.

Yours Friend
Jignesh Pankhania (India/Gujarat/Ahmedabad - 9727421981)

I have one of these drives on the table at the moment, your issue is almost certainly partial sector accessible issue caused by using m0 command when it should not be used. Most people only know that command through the old 7200.11 fix, which did actually work well for BSY issue, but not this. Trying to clear / regen the translator incorrectly aggravates the original problem.

Salvation Data tools have a 'fix' for this that works quite well. Their fix is essentially an automated version of the so called Leonardo method, which I first saw on the SD boards and later elsewhere, using i4,1,22 to clear alt list and then manually re-adding bad sectors into the translator by scanning for and adding them one at a time, rebuilding the translator each time a new sector is added to the list. This works fairly well actually, though it takes a really, really, long time - the PC3000 has a different, more proper method that fixes the translator module directly rather than via serial interface commands.

Both SD Doctor and PC3000 has the ability to fix the initial problem itself (BSY 7200.12) without messing up the translator, though SD's solution only works on a subset of drives, not this one as a matter of fact, because it doesn't properly support anything 2TB+ and has only mixed support for 7200.12+. Data can be retrieved manually as waqas_ali766 suggests.. except once the translator is messed that won't work anymore by itself.

You can try to get your data by putting your drive in ESLIP mode (ctrl+t) and reading to as far as you can go, write down failed sector, ctrl+z before it locks up, check alt list (V4) to make sure that sector is loaded, and then rebuild translator with m0,6,3,,,,,22. Water, rinse, repeat. Except.. there may be 10 affected sectors, there may be 10,000. What's worse is that this particular drive series locks up during this operation if you access the data via UDMA, and you can't be sure it will add the bad sector to the alt list in the first place. So, doing this manually is not the correct way.

Xsoliman do you have any news or more info, I have the same problem
thnks

http://malthus.zapto.org/viewtopic.php? ... 557&p=2096

Obtain a list of the ConGen parameters before you change any of them, just to make sure you will be changing the correct ones.

_________________
A backup a day keeps DR away.

Hi phil_ccc, ... hehehe thanks for "Leonardo method".

Bye, Leonardo.