Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

v{00000028}qv{00000028}

November 19th, 2013, 16:29

I'm reading and writing sectors on a 7200.12 drive using terminal commands
(and also via the sata interface)

There is a particular area I cant read

Other similar areas if I write them with terminal they become readable again (both in terminal and sata)

But some give me this this strange v{00000028}qv{00000028}... error

Anyone know what it means
or why I can't clear down or refresh this area ?


F3 A>R7d52e,1

DiagError 00005003 R/W Status 2 R/W Error 43110081
Next User LBA 00000007D52E LLL CHS 000185.4.0093 PLP CHS 000185.4.0093
Remaining Transfer Length 00000001

F3 A>W7d52e,1
v{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}q
DiagError 00005004 R/W Status 2 R/W Error C4090081
Next User LBA 00000007D52E LLL CHS 000185.4.0093 PLP CHS 000185.4.0093
Remaining Transfer Length 00000001


Later areas read and write ok
or are fixable by writing
Other later areas have the same v{00000028}qv{00000028}... error

Re: v{00000028}qv{00000028}

November 19th, 2013, 16:40

Probably means a real bad area
especially as I suspect issues with head 4

I'll double check what head the areas I was able to fix were

Re: v{00000028}qv{00000028}

November 19th, 2013, 16:42

But the sector before it 7d52d, also on head 4, reads and writes ok
(after I fixed it with a write)

So not a completely dead head 4

Re: v{00000028}qv{00000028}

November 19th, 2013, 16:52

Sometime I get several lines of v{00000028}q
which then turn into qV{00000028}qV
and the write completes ok !

Re: v{00000028}qv{00000028}

November 20th, 2013, 1:14

What is the purpose?

Re: v{00000028}qv{00000028}

November 20th, 2013, 6:55

Education

Plus resurrecting the drive for reuse if possible

Re: v{00000028}qv{00000028}

November 20th, 2013, 7:17

You cannot refurb it completely and isolate errors completely without other resources, the only thing you can do is add some defect or zero fill, the rest doesn't work or work partially, with errors that come back later during use.
P.S. the various m0 miracles about 'adding defects' and 'certify' are BULLSHIT. You can simply zerofill it ! (Complete refurb require a lot of additional work).

Re: v{00000028}qv{00000028}

November 20th, 2013, 14:03

For info some of the 'bad sectors' that I rewrote inside terminal and get to work again are being put on the g-list
ie they are really bad and are getting remapped (as expected)

eg a typical new V4 entry
0021 00000007D52D 00001D32A85C ------.-.---- 0437FA.0.0013 01AD9E ----- ------ 00010000 11111111

F3 A>F 7d52d

Sector Info:
LBA PBA LogSec PhySec Wdg SFI Split Burst
0007D52D 1D32A85C 0013 0013 0056 0001AD9E 0372:1(04B4):03F1 0057 REALLOCATED TO PBA 00001D32A85C

The recent remapped sectors are probably due to a bad area on that part of the Hd4 platter

Strange that it cant remap 7d52e
when I write it and gives
v{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}qv{00000028}q
DiagError 00005004 R/W Status 2 R/W Error C4090081


Reassigned Sectors List cant be full ?
Can still remap other bad sectors ok

Correction the ones I can still fix just refresh and stay in the same place
Cant seem to add any more to the remap list
Post a reply