I apologize that this is a long read, as I am still at a loss for ideas and thus I am laying out most of my attempts, habits, designs, and thoughts in the hopes that it will allow someone more knowledgeable than I to come to a solution.
The morning of Tuesday, Oct. 20th had me awake to discover the power was out. My computer normally is online at all hours, at least partially, and thus it was on when the power must have dropped. That being said, I have a Kill-a-watt leading into an APC surge protector, leading into a Corsair RM1000 80plus Gold certified PSU. None of these devices suffered ill fates. I returned from school to find the power restored. I turned the computer back on to encounter the first bad omen, Windows was taking an obnoxiously long time to boot -- over a minute when it normally took a couple seconds, literally. I log in to windows to be greeted with a plethora of "this isn't running", "could not update this", "such and such did not start" etc. errors. Figured it was just some extra nonsense from a bad shutdown until I noticed the shortcut to my main drive was dead. Go to computer>drives. Only two partitions are listed when there should've been 4 (note: 2 of those partitions were on one drive, the affected drive, drive A).
An aside. My system runs off of a "large" HDD split into two partitions, one containing media, the other containing games, other programs, and miscellaneous files. This HARD disk drive will hence forth be referred to as drive A including its two partitions for simplicity.
A second drive is a recent SSD purchase to put some random files on as well as big, hefty, fancy games such as GW2 that I want to run at peak speeds. This SSD will hence forth be referred to as drive B.
A third drive is my original SSD and is hardly big enough to hold windows 7, often even needing to be pruned periodically to make space. Not great I know, but was hoping to buy a replacement for it soon. This Windows only SSD will be referred to as drive C (because that makes sense after all).
I reboot and hope that resets everything. no dice. So I get into the machine and unplug drive A from power and data, plug it back in, reboot. No dice. I go into the admin tools and pull up storage information. Drive B and drive C show up, drive A is no-where to be seen. Not even an unformatted partition, corruption errors. again, it's as if the drive wasn't even plugged in despite the contrary. Hoping this might just be an OS error I reboot and go into the BIOS. BIOS doesn't even recognize that the hardware is plugged in. It shows an empty SATA port. I shut down the system and remove the drive for its safety and go to bed.
Drive B already had GW2 on it, the next night I had a TLC rally to run and installed teamspeak on drive B, put up with my computer's gimped functionality and had some fun. By Thursday Oct. 22nd, I started considering my options about data recovery which is way out of my budget and where I might be able to cut corners or what options I might not have tried yet. For now I set into the idea of partially rebuilding what I lost and start installing some other core programs and games on to drive B in the hopes that I could at least be mildly ready for HoT the next day. In the middle of steam installing TF2 and Rocket League to drive B it suddenly returns "disk write" errors as if the disk is full. I was sure it had enough space, but I pull up my computer to check its capacity to find that in the middle of installing things to it and with computer operation otherwise nominal, Drive B has now also completely disappeared without a trace! Just like drive A, no recognition from the OS nor the BIOS. And this time there was no power outage to blame it on. As of the time of posting this I have no real explanation as to what truly caused this. At the time it seemed logical that the problem was now likely in the motherboard, rather than the drives, since two drives failing within 2 days of each other in nearly identical ways is just too coincidental. Yet somehow, the oldest drive, also the OS drive, drive C, still functioned. For safety I shut down the computer and it hasn't been turned on again since, over a week later.
Sickening thoughts about the depth of the damage and work lost began to sink in combined with my new job and I'll be honest, I just didn't want to face these facts for a while and let the time go by a bit. The computer talked about this whole time was a recent build put together just this January with almost all brand new, high-end parts to replace a very aged gaming rig I built nearly a decade ago. That rig still works for the most part and I reassembled it to become a testing/troubleshooting machine. After over a week I finally got the old machine running again and after fighting some POST codes after not being used for so long, it was happily booting to BIOS and the freshly burned copy of Ultimate Boot CD (UBCD) I gave it. I plugged in drive A and set to testing. First just seeing if the BIOS of a different motherboard recognized it. No dice. Using a variety of HDD testing tools on UBCD all of them either ended up hanging indefinitely or spitting out errors about not being able to properly read the drive...or both! so no dice. UBCD has a LARGE list of tools to use though and I have hardly exhausted that list. For now though, with everything throwing errors about failing to read the drive, it seems my original hunch that the PCB that runs it is somehow badly damaged.
The good news is that the drive does not make the tell-tale "clicking noise of doom". It DOES spin up though which is obvious now that I have it sitting in an area where I can easily feel and listen to it. It seems like it's spinning slower than normal too, but I could just be perceiving it wrong. I have not gotten to test drive B yet. I worry that it has suffered the same ill fate. It is a samsung 840 EVO purchased a few months ago that is still likely under warranty. Sadly, not long after installing it I moved some files to it that exist no where else, which makes claiming a warranty where I lose that data unlikely.
The round up, Drive A seems to have a fried PCB, drive B likely does too. Handing them off to a repair/recovery service will cost thousands of US dollars which is significantly out of my budget. I have no idea what caused these events to happen and I feel if I were to leave my main computer online with drive C long enough it would be damaged too. At least that wouldn't hurt much, it's just windows. Losing the other two drives hurts...a lot. For what it is worth, yes, I have a back up, but it's a year old at least. I was getting ready to install a RAID1 array in a month or so to eliminate the need for back ups and got lazy. Too little too late I guess. Along with costly data recovery, until I can pin point the cause of these failures I feel simply replacing the drives could lead to the replacements being destroyed as well. I've so far found no visible damage to the motherboard and aside from drive failures the rig operates fine as if nothing was wrong. I suppose I could test voltages on the PSU to see if maybe it's frying things, but that's about all I can come up with.
Any ideas regarding further troubleshooting of the causes of these failures, or how to restore the damaged hardware, would be greatly appreciated. Any information or field connections anyone has to drive recovery services or employees that might be able to lend me advice or discounted services would also be greatly appreciated.
For now. I've spent over an hour writing this and need to go to bed. Thank you all very much for reading that and thanks in advance for any assistance you can offer.
In hindsight I note that the BIOS chipset had SATA devices set to an IDE standard format as per defaults, and I did not test with the other available settings. While I do not believe this will make a notable difference I will try the other options later and report back.