ROM Patch = "Unlock Error!" in terminal...

[300ddr]

Drive is busy. Read ROM. Applied Patch (both with and within "Force" option). When unlocking, it says "UNLOCK ERROR!" in terminal. This is the 2nd time in a week I've had this issue (I believe the other was also a Grenada). Any idea why it's happening?

Boot 0x40M
Spin Up
Trans.

Tech Unlock Handshake: 0x0552391E
Reply:
UNLOCK ERROR!

Spin Up
SpinOK
TCC:0017

(P) SATA Reset

[Nick_TS]

Hello Brian,

What version of PC-3000 did you use when patch ROM?
What is a family of the drive? What did the family you select in utility when patch ROM?

[300ddr]

What version of PC-3000 did you use when patch ROM? 6.4.18
What is a family of the drive? Grenada.
What did the family you select in utility when patch ROM? Grenada.

Says "UNLOCK ERROR" but if I wait a few mins, then control+Z works.

[studiogsm]

Like that: Grenada,
Model : ST3000DM001-1CH166
Serial : W1F402C7
Firmware : CC47
Capacity : 3 TB (5 860 533 168)


Boot 0x40M
Spin Up
Trans.

Tech Unlock Handshake: 0x97C7BFE4
Reply:
UNLOCK ERROR!

Spin Up
SpinOK
TCC:0022

(P) SATA Reset

ASCII Diag mode

F3 T>
ASCII Diag mode

F3 T>
ASCII Diag mode

F3 T>

[300ddr]

Happened today on Sentosa. ST1000LM010. But, this time, after "(P) Sata Reset" I never get terminal access. This is after head swap, so not sure if it's a head/platter damage problem, or unlocking issue.

[Trouse]

Was there any resolution for this? I have a drive with the exact same issue.... Thanks!

[300ddr]

You just wait and then it should give you term after a few minutes (except in my case above, which is probably unrelated to the unlock error).

[Nick_TS]

Hello Brian,

Source of the post You just wait and then it should give you term after a few minutes (except in my case above, which is probably unrelated to the unlock error).

I have checked several drives with the same problem, all of them had a head issue, I think it deals with heads...

Source of the post Happened today on Sentosa.

Did you unlock Sentosa drive?

[300ddr]

I believe it didn't ever get term access to that sentoza, but I think it had bad heads. A 3tb DM that had error was 99% recovered (no bad heads).

[carlosmar]

When a drive dont need patch, and you patch it you have this error... just remove patch or write original rom back... and its ok...