ST3320613AS SD11 — LBA0 (0 bytes), N1,1,22,,,,,22 gives Rst

[p.h.]

Hello,

I have a Seagate ST3320613AS with firmware SD11 showing 0 bytes (LBA0 issue). The drive was previously written with random data across its full capacity, after which it began presenting as 0 bytes and disappearing from Windows Disk Management after a failed initialization attempt.

Serial connection is confirmed working at 38400 8N1 via CP2102 USB-TTL adapter (3.3V). The drive responds correctly at all prompt levels.

Here is what I have tried:

--- Attempt 1: Standard BSY/LBA0 fix ---

F3 T>/2
F3 2>Z
Spin Down Complete, Elapsed Time 0.149 msecs
[paper removed]
F3 2>U
Spin Up Complete, Elapsed Time 4.190 secs
F3 2>/1
F3 1>N1,1,22,,,,,22
<NUL>
Rst 0x10M [repeating ~27 times]

Result: Drive still shows 0 bytes after power cycle.

--- Attempt 2: LBA translator rewrite ---

F3 1>m0,2,2,0,0,0,0,22
Invalid Diagnostic Command

--- Command enumeration ---

F3 T>? and F3 1>? and F3 3>?
All levels return identical SA buffer map (block addresses, DBA, zone labels including Drive Geometry SDBP DSB, Diag Mode Cmd, Ext Test Service). No command list returned — ? appears to output the SA directory in this firmware version.

Levels confirmed accessible: T, 1, 2, 3.

Summary of situation:
- Drive: ST3320613AS, FW: SD11
- Symptom: 0 bytes / LBA0
- N1,1,22,,,,,22 → Rst 0x10M reset loop (not the expected format progress)
- m0,2,2,0,0,0,0,22 → Invalid Diagnostic Command
- SA appears readable and structurally intact
- Drive firmware is running and responsive

It appears SD11 uses a different command set from the more commonly documented firmware versions. Could anyone advise the correct command sequence for the LBA0 fix specific to SD11? I want to avoid further blind attempts against the SA.

Thank you.

[pepe]

i guess this procedure is pretty broadly described, wondering where you got the commands you ran... N1,1,22,,,,,22 is bs for sure, m is for level T. Pay closer attention to what you are doing.

[SWM]

F3 2>/1
F3 1>N1
Wait for response...
F3 1>/T
F3 T>m0,6,3,,,,,22
Wait for response... (complette) The case of characters is important!

[pepe]

that sequence can lead to partial access very easily...

[p.h.]

Thanks for your replies.

The drive starts to send "Rst 0x10M" when only I turn on its power. Its speed varies and it clicks each 2 seconds.
So far I have tried:
"m0,6,2,0,0,0,0,22",
"m0,1,1,0,0,0,0,22",
"m0,2,2,0,0,0,0,22".
These commands were given to me by Seagate's support person.

Earlier today I was able to enter "F3 T>" with Ctrl-Z, but now I am struggling even with this.
"Rst 0x10M<NUL>[Warning: RX FRAMING ERROR]"

[SWM]

that sequence can lead to partial access very easily...

Yes, exactly. I was thinking about fixing the HDD. These commands aren't suitable for data recovery. Actually, just like the terminal.
Judging by the fact that it's gotten worse, it's not writing properly in SA either. Or maybe a lot of incorrect commands were sent...