Okay about maybe a month ago my hdd became unrecognized by the os, and bios after a surface scan got interrupted.

At startup the computer takes a long time in bios when the drive is connected.
After post moment the hdd is unrecognized by the OS.

I have tried to swap the PCB with a new one,
and recently have connected to the hdd using the RS232 attempting to fix what seemed to be the seagate
bsy error.

(This is the specific serial cnnector i baught in the link)

http://www.ebay.com/itm/280748167812?ss ... 1497.l2649

But as soon as i plug in the power i get different error messages from the terminal i do not understand such as....

( 43110081 InitiateMarkPendingReallocateRequest for.... and repeats for some time)
and now
(FAIL Servo Op=0100 Resp=0003 ResponseFrame....)

There is information on this disk that is not TOO important, not enough to pay alot of money to fix, but enough for me to try DIY methods.

Please, any help or insight would be great, i think ive posted just enough detail, but any other specifics needed simply ask and i will post asap.
Thank you in advance for any and all help.

Thanks for the reply Spildit.

By the 7200.11 solution i think u mean this
VVVVVV

http://www.msfn.org/board/topic/128807- ... 0011-hdds/

then yes that's what i did after i got the "43110081 InitiateMarkPendingReallocateRequest for" errors.

once i did those steps and after restart the disk was still not recognized.
so i used the terminal once again and got the different error

"FAIL Servo Op=0100 Resp=0003 ResponseFrame.."

i'm sorry i'm not sure i understand your reply too well. It may be a tad bit too technical for me. lol. I have my fare share of computer experience, and have taken servicing classes, but i have almost no knowledge of HDDs so please bare with me a little. I'm not sure if I erased G-List, or regen translator as you said, i just follwed the steps blindly in that link.

It seems like you know exactly what is going on. Just tell me what you would do step by step, and i will follow and let you know exactly what happens and what i see. Hopefully you can at least give me an idea of what the problem is and what can be done as far as recovering the data.

I would gladly pay around $150 -$200 for a clone of the data, or a fix, or anything, but the quotes i got from the professional companies was in the $800- $2000 range. and that is just insanity to be honest, i think they are crooks, no matter how sensitive the processes may be, they charge way too much because professional businesses are there typical costumers, i'm guessing, and they are willing to pay that much to recover sensitive data. but everyday household consumers are not.

Again thanks for your help and reply, it is extremely appreciated.

First off thanks again for your help, it truly is appreciated.

But the underlying tone of both your replies seem like i offended you in some way, witch was not my intention at all, and i am sorry if i somehow did.

That being said i am not completely ignorant either, Please get your facts straight before you judge someone. I did some research first with the symptoms and stumbled upon a website called hdd-parts.com. it was here that i got in contact with a "technician" who recommend i try a PCB swap. He also explained the information on the PCB needed to be transferred in order for the board to work with the drive, so they provided a BIOS swap service for me. If you still think the PCB is an issue i still have the original PCB, its not like i tossed it in the garbage. After installing the new PCB and having no luck i again contacted the "technician" of hdd-parts and he recommended i buy the usb connector and follow instructions for the terminal on the site. I was a bit skeptical about this process at first, so i did research before purchasing the product and it seemed like that was the solution to my problem. I also posted on another HDD repair site but it was no help, the only responses told me to pay a company for the DR. With research and with what the tech said, i went with my gut and did what i thought seemed best, but as soon as i got connected to the terminal, and powered on, i got the first error. i didnt want to shut it down so i waited to let the HDD finish and sure enough it did.

I was able to enter commands, but i did not enter the steps you provided in your response. I did not do a g-list erase or F3 T>m0,2,2,0,0,0,0,22 (enter). If you look lower in to the link i provided there are other steps for the BSY error.


I did this and only this after spin down, which was in the link...

F3 2>U (enter)
You should get something like this:
Spin Up Complete
Elapsed Time 7.093 secs
F3 2>

Then go to Level 1 (by typing /1):
F3 2>/1 (enter)
Now lets do a S.M.A.R.T. erase (create S.M.A.R.T. sector):
F3 1>N1 (enter)


. After that i shut down rebooted in sata and the problem persisted so i again connected to the terminal and i got the new error.

From this point, i did more research and i stumbled upon this site. And looking through i realized this is exactly what i needed. It is true, if i knew this forum existed earlier i would've definitely came here first, but with what i had at the time, i made the best decisions possible believing the people who said they knew what the problem was and that led me to where i am at now. I never did anything without asking or without research. I am very thankful to have you helping me i really am. But you kinda just criticized me and schooled me in two posts. I have more information now But again all you showed me was a link to another solution that might be my problem so i can blindly follow the steps yet again. You told me i should not do anything without asking, so here i am asking. Will you help me diagnose my problem properly and see what my options are? i am 100 percent willing to listen and do everything you say.

Once again thank you very much for the time and help you are providing. I cant stress enough how a good forum such as this one can be. From experience being helped by knowledgeable people such as yourself, for free, is truly a godsend.

MiamiYayi, I have been thru the same issue. It is not the disk, it is seagate discwizard. It does not handle the extended partition very well and goes off the deep end if you have the temerity to have 2 3T's on your system (XP pro on a dell xps).

I lost some files, but not awful; have been struggling for a couple of months.

My disk was not being recognized and, in fact, screwed up the whole system so that it would not boot when the disk was on board. My troubles began because I prefer 64K clusters. While segate would "clone" the disk I was trying to back up, it would slow down to a crawl when trying to do a straight file copy from the master disk. This concluded with the situation you describe and I experienced.

Really accidentally, I have the disc back. It will not work with the other 3T on board in normal winXP. However, safe mode will recognize the basic partition and do a straight copy to it from another disk, including the other 3T on the system. Of course, in safe mode, the extended disks are not recognized and cannot be dealt with. I can run normal winXP only with 1 3T on board. My system disk is a seagate 2T with 4k; works fine mostly. System partition is smallish, a "temporary file" partition, then the rest 64K cluster data.

I read what you read (best I can tell), got a RS232 to ttl converter (actually many as I wanted to get exactly the right one!) and set up the terminal session on a win98 PC. Got the error codes you mention and interrupted it. But, it communicated!

Decided to let the disk spin unconnected for several hours, then went to the terminal session again. This time cntrl z got a response. Not wanting to change anything, I merely did several of the "display" commands. Everything worked cleanly.

The disk had not been updated to the newer firmware.

Remounted the disk (had to be internal as XP 32 does not have a USB that will handle it) and went to setup. Setup showed all the disks (both 3T) correctly. This was a thrill!

But, sadly, in windows XP, the disk did not show. I decided to see what would happen on a win 7 USB connection; got recognized, unusable, with the 16T storage report. That heartened me as it meant the disk was reconized.

Decided to mount it without the other 3T and to try to update the firmware. Using the ISO on DVD method, it worked.

Started winxp and the disk was fully recognized. Immediately backed up what little I had failed earlier (far less than I though!) to a USB external 2T.

Shutdown and remounted the good 3T. Recognized in setup, winXP saw the "mass storage devices" but they were unusable. Pulled the good 3T and everything was back to working order.

I tried to do a mass copy of missing files to the extended partition; same behavior as before; slower and slower until virtually nothing. I don't know if it is a 4K issue or the extended disk issue, but it does not happen with my 2T disks.

Thanks for your post, it encouraged me and ultimately helped, despite your failure to solve the problem. As I said, I am sure it is seagate software.

MiamiYayi, In addition to what I said, below, in the thread, since getting the disk working again, I have tried to copy files from a non-extended disk to the 3t extended partition; it reall just won't work. Got a blue screen that mentioned essentially stack overflow problems. I think the diskwizard is faling to clear its stack after each write. I am confident it is a seagate issue.

The 2T parttion seems fine as long as the disk is not mounted with the other 3T at the same time in normal windows. Safe mode works fine, but, of course, the extended partitions cannot be reached.

Thanks very much for your post.

Doubtfull... Besides, NRG is cleared now already

He guys, thanks for all the replies,

I havent had time to try what spildit suggested, ive been very buisy around the holidays. As soon as i get a chance i will post.

Thanks again