ST4000DM000 - Not accepting F3 commands

[parmindo]

Hello guys, good day.
I'm struggling with a particular drive here. This ST4000DM000 is reading on every 8 heads, but only some parts of the sectors.
Every head can read aprox 20% of the sectors with a consistent 30mb/s.. but at the mojority of points it doesn't read at all.
SO, I was looking to find anything using serial (with MRT), but this drive is behaving weird as fuck.
I could backup the majority of the sys files, but when I try some of the diagnosis command, it gives me this:

F3 T>/7

F3 7>X

F3 7>

F3 7>V1

Invalid Diag Cmd

F3 7>V4

Invalid Diag Cmd

F3 7>V40

Invalid Diag Cmd

I don't know if this could be head problems (it doesn't sound weird at all), or a firmware problem.
Thank you for any light.

[pepe]

terminal locked, lombard family. easy to unlock.

[parmindo]

pepe, thank you for your answer. I've already unlocked it, but still gives the same results

[parmindo]

pepe, Deeply sorry. I"ve found now that Lombard needs am ATA unlocking.
Found it on MRT and now I can work. Thank you so much

[northwind]

F3 7>V1

Invalid Diag Cmd

F3 7>V4

Invalid Diag Cmd

F3 7>V40

Invalid Diag Cmd

Additionally, V* works on level T, not 7.

[pepe]

LOL, i missed that

[parmindo]

Oh god... this was made on a really tired moment.
I appreciate all your answers.
I'm still struggling with bad sectors. This is really different of everything I saw.
Heads are working, but doesn't read spatial points.
I'm convinced that this is not a head issue, but how could I be certain of that?

Thank you

[michael chiklis]

Probably you will be able to increase heads reading ability with AFH parameters, you might kill heads and surface if you change AFH too high or too low.
Don't play to much with those parameters, do first some research about AFH before changing them.
Start from this:
https://youtu.be/5lKvzmVMBM4?si=7ylbMlXVXVdnFpA3

[michael chiklis]

Sediv can do that either
https://www.youtube.com/watch?v=7bdax6udlY0

[digisupport]

99,9% head or media problem. Probably with a high risk of killing data without visual head inspection or a quick head check in a donor drive.

[parmindo]

I've found a pattern. Drive reads nearly 500.000 sectors at +50mb/s, then find nearly 75.000 problematic sectors on every single head (there are . I'm imaging those good sectors first, but still this is a strange pattern for media damage.

[michael chiklis]

it's zone issue, as i said try by modifing AFH with mrt