Problem with st32000644ns Hard Drive from raid array

[computerpd]

Heres a little backround I bough lots of these drives they were removed from hp and dell arrays. 2TB sizes.

Ok the problem, I hook them up to a PC since i dont have a server handy and my BIOS sees them as 4.14 GB ST_M13FQBL and if they happen to show up in windows which only a few do, it shows the same thing

Someone suggested they have seen this before when you try to put raid drives on pc units he called it raid lock where the drive only functions in raid arrays.

Any Suggestions, I ran MHDD Screen shot below.
[PRE]
51 ERR INDX CORR DREQ DRSC WRFT DRDY BUSY HPA AMNF T0NF ABRT IDNF UNCR BBK 04
[ST_M13FQBL ] [ 8,089,950] [ 8,089,949] [ EST: 00:01 ]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Û <150ms:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Û <500ms:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Û >500ms:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ? TIME :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! x UNC :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ABRT : 31726
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! S IDNF :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! A AMNF :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 0 T0NF :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! * BBK :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [ 97.9% ] [ 97.9% ]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: 8088600
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: 8088855
Error: 8089110
Error: 8089365
Time spent: 00:00:33 Error: 8089620


þ Smart -> ATT
Getting SMART attributes... Error: device error


| Take a screenshot : <F10> | 13:31:42
[/PRE]

[fzabkar]

What sounds do the drives make?

[BlackST]

If the drive is ata locked it appears with the right name and capacity but you cannot read or write anything, in mhdd you get only '!'
This case sounds like you have a faulty drive recognised as his 'factory alias'.

[computerpd]

it spins up clicks but not like the COD its like the read heads are just moving back and forth around 10 or 11 times then spins down, I found another post here about it being a fault in firmware, I may have to try getting in there and seeing what I can figure out.

[BlackST]

Seems BAD HEADS, instead.

[jignesh]

Heres a little backround I bough lots of these drives they were removed from hp and dell arrays. 2TB sizes.

Ok the problem, I hook them up to a PC since i dont have a server handy and my BIOS sees them as 4.14 GB ST_M13FQBL and if they happen to show up in windows which only a few do, it shows the same thing

Someone suggested they have seen this before when you try to put raid drives on pc units he called it raid lock where the drive only functions in raid arrays.

Any Suggestions, I ran MHDD Screen shot below.
[PRE]
51 ERR INDX CORR DREQ DRSC WRFT DRDY BUSY HPA AMNF T0NF ABRT IDNF UNCR BBK 04
[ST_M13FQBL ] [ 8,089,950] [ 8,089,949] [ EST: 00:01 ]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Û <150ms:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Û <500ms:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Û >500ms:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ? TIME :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! x UNC :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ABRT : 31726
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! S IDNF :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! A AMNF :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 0 T0NF :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! * BBK :
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [ 97.9% ] [ 97.9% ]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: 8088600
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: 8088855
Error: 8089110
Error: 8089365
Time spent: 00:00:33 Error: 8089620


þ Smart -> ATT
Getting SMART attributes... Error: device error


| Take a screenshot : <F10> | 13:31:42
[/PRE]

Dear Friend computerpd

Ur Drive Is Spindown In 5 yo 7 second when powerup its not complet init process check it definatly ur drive status is what i said i am sure 100%.
if ths drive status what is said then its head and u cant do anything with this case bcoz i judged you by ur question.
and for drive status its show u the PCB info only its common things in seagate.
when anyone getting the ST_M13FQBL or anything like this that mean the drive stop spining and u r in only safe mode @ some says it pcb mode like me and some say it kernel mode its not make big defrance. if u try to conform put any drive with only pcb and get info u just getting this what u seen rightnow with this hard disk.

your friend
jignesh pankhania

[DR-Kiev]

It is not clear, all the drives you bought, perform the same state?
Often, when big companies sell their old server drives , they do degaussing before sell them, to avoid any leak of information.

[computerpd]

If they were degaussed is there any hope of repairing them?

[computerpd]

To be honest I have 13,000 of these drives and wondering if there is anything that can be done, or is this just a million dollar pile of junk?

[BlackST]

If servo is gone, no way except at factory or you have a STW and know what to do (very unlikely), all the rest except physical damage is fixable (not by you, though). P.s. usually these drives are sold as is because they are pulled from servers for a reason !

[BlackST]

Maybe they are not degaussed, just intentionally damaged in order to make data inaccessible. A simple test with a DDA can determine if there is servo or not and a sample check can determine if headstacks are likely working or not. Find someone at reach who have this kind of equipment and check some samples.
Excluding me because of the distance I am quite sure someone near can refurb the drives.