Grumpy DBA (3/25/2014)
As someone else has already stated if this data is valuable I would seriously consider bringing in a seasoned SQL Server pro to handle this. No offense intended but you do not have a clue, leave it to someone who can recover your database(s) for you. Also, have your contractor savior review the current backup and recovery plan and change it as needed.
Also hardware redundancy. We monitor things like disks, and use raid / SAN to minimize disruptions like you are experiencing.
It is hindsight, but had you (or someone else) dug in deeper at your first sign of trouble, you may have been able to avoid most of this.
Most servers have some kind of health monitoring for things like this.