ST9500325AS LBA 0 problem

[ivrzivr]

Dear all,

2 days ago, when i was using my notebook, i got a warning from google chrome that it had crushed and need to be restarted. I pressed ok button but computer reset itself and that is it. OS didn't start again.

When i look to bios, i saw that HDD is recognised 0GB and after i make test with Seagate Seatools, i saw the hdd again as 0 GB and LBA 0.

After that i searched the net and found some solutions by using serial to TTL interface and prepared that interface. Than i applied (F3 T>m0,2,2,0,0,0,0,22).

When i reboot the system, i saw that hdd now seems as 500GB. So i thought things are going well.

I started to check the device with Seagate Seatools again and it recognised the device as 500 GB. When i started to make short test, hdd failed. than i applied long test. Test started normally but when it comes to 4% it opens a windows showing "A1EECC52" error code. Than it starts "short dst" and after 10% it opens another windows named "errors detected during long test" and asks me to skip or repair. When i press repair, it showes for all the errors as repaired. But this isn't changing anything. I cannot reach any data. When i start seatools again, the same thing happens.

MHDD is not recognising my hdd because it is connected to notebook as slave (i don't know why but it is factory default).

What can i do now?
Any DIY suggestions?
Would "board replacement" work for me?

Waiting for your helps...

[labtech]

There is nothing wrong with your board, so don't mess with it.
You have either firmware, bad sectors or both issues. Need pro equipment and know how to tell for sure.

Would have asked you to run a test using MHDD, but your set up makes things more complicated.

[dick]

Set the laptop bios setting for the hard drive to 'ide' or 'compatibility' mode. Then Mhdd should see the drive.

[northwind]

...or remove hdd and connect it to a desktop machine.

Agreed that there is nothing wrong with the pcb.
When disk detected with correct capacity, did you try to access data? If so, i would copy them to another hdd and RMA this one.
But i guess, since you started seatools again, that you couldn't access user data.

Then, pro equipment is needed.

[ivrzivr]

i connected it to desktop and run mhdd.

it detected hdd. than i started scan.

on 46553158 (%4,8) mhdd started to mark X (UNC) ... and it is going on to mark X...

any suggestion?

[mr_spokk]

Translator issue, not a DIY...you will need a pro on this one.
Where you from? Maby there is a member here thats near you!

Regards/ Bosse

[ivrzivr]

istanbul

[einstein9]

istanbul

Contact: Omer
http://www.omeramasya.com/

he is the best choice

[ivrzivr]

btw
what is translator problem???

[mr_spokk]

btw
what is translator problem???

It's when the drive speak Spanish, and you don't understand word. ...Figure of speach.

Bosse

[mr_spokk]

Pci 3000 UDMA can handle the translator problem, or you can do it your self if you know how.
But as I understand you don't know, so to solve your problem you need to go to a pro who knows how to deal with it, for example Omer.

Regards/ Bosse

[ivrzivr]

i will try to do by myself if it is something that i can do.
As i wrote above, i already set up a tool to reach hdd by serial to ttl interface.
Let me see if i can find a walkthrough...

[pcimage]

As Bosse ans northwind already said, you need PC3000 UDMA to solve this problem.

Please feel free to ignore the advice you asked for, then tamper wih the drive possibly rendering it non-recoverable.

Your data = your choice