I'm going to try to explain this the best I can. However, I know nothing about the internals of a HDD, so please bare with me.
The other day when I powered on my PC after it was shut down for the night, my external USB HDD did not load up properly. I could hear that it was trying to start up but I think the external power must have gone bad (just a guess). Anyway, I took the drive out of the external case and plugged it in as a regular SATA drive. I had it sitting outside of my PC case on a box as I tested to see if it would work.
I booted up my PC, and the drive worked. Great! Now a couple minutes later, because I'm stupid and will never forgive myself, I accidentally hit the drive with my foot and it slid off the box it was resting on. It fell a MAX of 4 inches off the back of the box and it landed on the back of the drive (where the power cables are plugged in) on the carpet. It made a weird spinning noise as I went to set it back atop the box. Windows told me that there was an error reading some file, but I didn't think much of it because for the moment it still worked. Then, however, it disappeared from my drive list. Strange, I thought, so I rebooted to see if it just needed to reset itself.
Bad idea apparently. Once I restarted my PC, the drive would make a buzzing noise for about 2 seconds, then make a small 'beep' noise. Then it would do that over again several times as windows was booting up. As the windows screen appears, the PC shows a BSOD for a split second and restarts. I can no longer boot into windows with that drive plugged in.
It is not my main drive, but it has so many files on it that I will probably never be able to get again. I realize that I'm an even bigger idiot for not backing it up in the first place. Please know that I will never make that mistake again, but it could be a lesson learned too late.
As far as trying to get the drive to boot up, I tried a few things after looking around the web. BIOS will not recognize a drive is plugged in. I tried using the Western Digital SATA Diag tools. It did not recognize that I had a WD drive plugged in. Fail there. I tried using SpinRite which is supposed to be some super-software for doing recovery on HDD's. It booted up into the software, but when it tried to scan the disk, it threw an error similar to this one
http://iamyouruser.blogspot.com/2006/02 ... error.html Basically it must mean something like "what the heck did you do to this poor drive?" So that was a no-go. I also tried tapping on the side of the HDD as it started up thinking maybe something was stuck. However, the more I listen to it, the more I think it may be an electrical error of some sort, and not a part error.
I am now fresh out of ideas in the "things I know something about" category. When it comes to the internal workings of a HDD, I know nothing. Which is why I come before you, oh HDD gurus, in the hopes that you can help me shed some light on this error, and maybe lead me to getting it fixed.
Now, I know I could take it to a pro and get it fixed (maybe) and spend $1,000 in the process. However, while the data on that drive goes back some 5 years and I will never be able to get some of those files again, it's not worth spending that much to recover the files. Tough crap you might say. Plus, I'd rather learn a thing or two about HDD's while I'm in despair.
Now all I've done so far is just ramble on out how dumb I am, and how I potentially killed my HDD by making it fall like 4 inches onto carpet none-the-less. Is that even possible? A 4 inch fall caused this much damage? What information do I need to supply you with to help you potentially lead me on the right path to figuring it out? I haven't taken any portion of the HDD apart for fear of ruining it.
The model # is WD5000AAKS-00TMA0
The numbers across the green board (the PCB, I think it's called) are as follows:
2061-701477-800AC XC 4D05 1CNV 9 0001370 7371
Please let me know what else I can do to help and thank you so much for your time!
Once again, I know this could've all been prevented if I would've just made a backup. I'm really stupid... I get that.