First of all, thank you all for your replies. I appreciate your time spent in reading as well as getting a thought back to me. I didn't get back to you earlier because it took about 4 hours to to get my post online, and after a lot of refreshing it did cross my mind that it wouldn't go online at all, but nevertheless, its up along with the info.
hdguy wrote:
You need to correctly identify the problems...
Problem Solving one on one, know what is you want to fix before you fix it.
apollon13 wrote:
...there i go again on, off, on, off, SPARK OMG!! dead. So as if it wasn't enough, i killed the board as well...
Well i know that much, i definetely need to replace the pcb. If this allone will be enough, i doubdt it, but lets say its a starting point.
hdguy wrote:
...Parts sourced need to be totally compatible...
apollon13 wrote:
...I killed the board, lets look for the board, and so i did, and found it, havent seen the chip code yet, so i haven't ordrered it in yet...
Through my reading especially on the donor drive subject, they did mention that if you do undergo that path, you should definetely look for a drive that is the exact same p/n, as well as something close to 2 weeks -+ of the production date.
So based on the above i found the following that match my pcb:
sticker code: OA75655
# on board: OA90269
chip #: 88i9105-TLA2
In case that i do undergo that path, it seems to me that I'm gettin somewhere closer, even if in the end i do endup giving this to an expert company, at least they wont have to deal with the pcb board as well. So i did put my order in today, and fingers crossed I'll let you know how that one works in two weeks time.
hdguy wrote:
...following any repairs you would need to attempt recovery / image of your data in an environment that will help keep stability - Windows alone is not enough...
As an MCP (pretty useless in this field but what the heck) I know that windows is a bit messy in regards to accessing and reading from the drive, that alone is enough to mess the process since the iradical movement of the head would be more than enough to hold me back.
apollon13 wrote:
...So, i didn't breath, one hand the hd, the other on windows explorer, slowly...
At the time it did woke up out of nowere, and i tried to get back what i needed, and to be honest although that i was trying to access the data as a "noguru", i didn't really believe it would come back alive, so yes, unless you feel on giving me a specific path towards a steady environment (mount/linux for example), i recon I'm gonna do a bit more research on that one.
hdguy wrote:
I expect there will be many surface errors also which again would require a specific environment for the recovery (i.e PC3000 / Deepspar etc)
Well here comes the difficult part, the pricings on those are slightly of the grid, so i guess i should keep my fingers crossed and hope for the best, eg maybe the data in question not to have been affected by the surface errors.
hdguy wrote:
you also need a clean environment like a laminar flow bench.
That much i understood from the beginning, I've got some contacts in the pharmaceutical industry that they might let me use their laminar flow workbench (a friend of mine did build their production line, so i might get away with it by scratching their back at a later time)
Spildit wrote:
...Don't think about platter swapping when the problem is most likely somewhere else...
The only reason that i mention it is because its single platter disk, meaning having less risk in "encrypting" the data to a point of "no decryption". Another reason (negating the "only reason" that i mention before but hey

) would be that then i would be closer to solving the problem, by not having to identify if it is the motor, the head, or whatever else that from my point of view i will be unable to correctly and accurately identify, and maybe if i do it right, i'll get a glimpse of my data.
Eleg wrote:
...you will most likely be able to recover with R-Studio or similar tool...
Well i did try that with some other solutions, and couldn't seem to find unformatted text (.txt files) which is actually the reason that i go the whole data recovery process (txt files containg user pass credentials spread across different servers of my customers databases, which are many other ways to reset, but it will be a huge @#$%). But i'm gonna look into r-studio and let you know how that one works.
Reha Andrew wrote:
dropping can cause severe damage to your drive and can make you to lose your data permanently
Northwind duly noted, as well as the general don't DIY, which i more or less expected. Still if you have any more thoughts on "No Guaranty DIY" I will be more than happy to hear. I will be holding my breath untill i get my ordered pcb, and will be looking for a donor of the the same part # and close production date, and if you have any suggestions on that, shoot. Maybe by that time i'll roll the dice and DIY, or just ship them altogether to Northwind or similar, so I'll keep on refreshing this topic in the meantime
