Hello,

I'm having problems with this seagate drive. It takes a really long time to get ready in terminal and in online mode i'm getting this type of errors:
...
InitiateMarkPendingReallocateRequest for disc_lba: 000012AF5B!
(DOS) Read Error - 000012AF5B.
(DOS) Marginal Read: 000012AF5C
(DOS) Read Error - 43110081
....
The V4 list has a lot of entries mostly about head 1:
F3 T>V4
Reassigned Sectors List Enabled
Entries: 28EF, Alts: 002A, Removed: 0000,
Pending: FFFF Host Pending: 4318
...
The V40 it's empty:
F3 T>V40
Nonresident GList 0 entries returned
Total entries available: 0
PBA Len Flags Phy Cyl Hd PhySctr SFI
...
And V80 has 80 entries:
F3 T>V80
Resident GList 50 entries returned
Total entries available: 50
...

I tried disabling read and write sparing, correction, Background Media Scan, offline sparing and set DAR_ENABLED = 0,
but the drives bocks anyway after reading a few mb (12 -32).

Thanks to this thread Seagate Terminal Tutorial – Reading Disk Sectors Via Termina ( thank you xsoliman) i managed to read with a script the ntfs mft except for 2 4k sectors (both in the V4 list).
But when i try to read some of the files i run into problems when the sectors are in the V4 list.
When the sector is pending to be relocated it gives me:
F3 A>Re656aa5,1

DiagError 00005003 R/W Status 2 R/W Error 40000087
Next User LBA 00000E656AA5 LLL CHS 020BB5.1.012D PLP CHS 020BB5.1.012D
Remaining Transfer Length 00000001
Info about lba:
F3 A>FE656AA5

Track Info:
Partition PhyCyl LogCyl NomCyl RadiusMils LogHd Zn LogicalTrack FirstLba FirstPba LogSecs PhySecs WdgSkw SecPerFrm WdgPerFrm
User 00020BB5 00020BB5 00023CA0 +1.354562E+3 01 0B FFFFFFFFFFFF 00000E656978 00000E678D66 0188 0188 008B 0001 0001

Sector Info:
LBA PBA LogSec PhySec Wdg SFI
00000E656AA5 00000E678E93 012D 012D 0030 00024A28 PENDING
V4 entry:
26E7 00000E656AA5 00000E678E93 020BB5.1.012D 000 020BB5.1.012D 024A28 00AC6 1173B0 0000000000100001 00000000

When the sector has been relocated it gives me this (it also makes a really ugly noise):
F3 A>RE96F277,1

FAIL Servo Op=0055 Resp=0007
0055 0572 0702 7FFF 7FFF 7FFF 0000 0003 0000 0905 03E8 0004 FFFF 9580 0205 0600 0064 000C 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
ResponseFrame 6752 0001 FFFF FF82 0008 0000 0000 0000 0C79 0000 0000 0000 0000 0000 1000 0000 0000 0000 FFFF 2000 DEB6 0000 0003 6371 0005 7996 0000 2443 0000 0020 0018 0000 C7E5
DiagError 00005003 R/W Status 2 R/W Error C4150183
Next User LBA 00000E96F277 LLL CHS 053B0A.0.B408 PLP CHS 053E6A.0.005B
Remaining Transfer Length 00000001
Info:
F3 A>FE96F277

Track Info:
Partition PhyCyl LogCyl NomCyl RadiusMils LogHd Zn LogicalTrack FirstLba FirstPba LogSecs PhySecs WdgSkw SecPerFrm WdgPerFrm
User 00053E6A 00053B0A 00057996 +7.328125E+2 00 1D FFFFFFFFFFFF 00001D273E6F 00001D2B2CC3 003D 00E0 00B9 0004 0007

Sector Info:
LBA PBA LogSec PhySec Wdg SFI Split Burst
00000E96F277 00001D2B2D1E B408 005B 0158 000998D4 0516:06D5 0159 REALLOCATED TO PBA 00001D2B2D1E
V4 entry:
26E9 00000E96F277 00001D2B2D1E 000000.0.0000 000 053E6A.0.005B 0998D4 00ABF 083AEA 0010010000010000 11111111

Is there a safe way to empty the V4 list and regenerate it? Or that's not the way to go?

Thank you for your help.

Hi Dear Friend pacman730

if u r in data recovery field and have basic setup then contact me on my skypee id : smart.computech i will teach u how to resolved this issue step by step.
i have solution for this problem and then u u just pay me just ONE REPLY Messege here that ur problem is resolved sucessfully no need any money or anything other things.

but if u r not in this data recovery field sorry in advanced.

Yours Friend
Jignesh Pankhania.

@OP
If your goal is to repair the drive and not data recovery, then just RMA the drive. Too much headache.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

@jignesh
Anything that can be done with just terminal? What exactly would i need?

@Spildit
Do you mean like in malthus .zapto. org/ viewtopic.php? f=83&t=557&p=2096?
Because i tried that but cant read past a few mb without the drive blocking itself. The sata interface doesn't respond anymore. Have to power cycle.
I didn't try the reverse method though.
What is the problem with the drive?

Can someone please explain the reading errors?
I understand the ones that are marked pending: the drives tries to read at that lba but since it hasn't been relocated yet doesn't know where to look. Right?

What about when they have been relocated? Why are they still in the V4 list? Shouldn't be moved to the resident g-list (V80)?
It makes a really ugly noise when i try to read from them. And a nasty error. Why?
Thank you.

sorry for not quoting and bad link, everything i try to post seems like it needs approval

Hello

Glad we were able to read some/most sectors of interest from Terminal
But no easy way to read large amounts of information that way

"When the sector has been relocated it gives me this (it also makes a really ugly noise):
F3 A>RE96F277,1

FAIL Servo Op=0055 Resp=0007 ...."

That's doesn't sound good

Maybe the 'spare' area at high LBA numbers is bad


Since your V40 NRGList is empty
and since you don't need the data
you could experiment with some m0,... commands to try to partially 'refurbish it'
But its never going to be reliable enough to trust with any real data

I'm doing some similar 7200.12 experiments with some scrap drives
7200.12 (and .11 ?) do seem prone to busy issues with InitiateMarkPendingReallocateRequest

Apparently I've been banned for trying to post my last post to many times. I didn't mean to cause any spam, i was just trying to ad a link.
I couldn't even quote for some reason. I did wait 5-6 hours after my first attempt before i tried to post again, so i thought it was just automatic protection and nobody was going to approve the post.
I apologize to whomever had to deal with that, admin and/or mod.

@xsoliman
Unfortunately i do need the data. I only need to recover a few gb. It's a personal drive with some photos that i need.
That is why i didn't try anything that might jeopardize recovery. Only played with the congen flags, but that didn't help me.

You might be right about the spare area being bad.
I just did some testing and if i try to read above PhyCyl 4FFFF on head 0 that FAIL Servo error happens and it makes the noise.
Other heads are ok. So everything at PhyCyl 50000 and higher i can't access.
At that location it's the spare pool:

F3 2>x
User Partition

LBAs 000000000000-00001D273EAB
PBAs 000000000000-00001D4619A0
HdSkew 006E, CylSkew 0019
ZonesPerHd 1E
...
System Partition

LBAs 000000000000-000000315A0F
PBAs 000000000000-0000003BE7FF
HdSkew 006E, CylSkew 0018
ZonesPerHd 02
...
Spare pool
Start Logical Cyl: 053B0A Logical Hd: 0
PBAs: 00001D2B2D92-00001D4619A0

Anybody has any idea what might be wrong with the drive? Or the steps to diagnose it correctly?
Even with specialized tools like pc3k. It might be helpful to steer me in the right direction.