MongoDB problems recovering a member of the replica set
You currently have a member running in secondary, because it cannot form a majority.  This is why you should always have an odd number of nodes in a replica set (one can be an arbiter) and I would recommend adding a third node as soon as possible once you get things back to normal.

In terms of how to get the second node up and running, do the following:


Shut down the remaining Secondary server (not strictly necessary, since it is read only as a Secondary, but safer)
Now, copy the whole data directory (everything in dbpath) over to the other host
Restart both nodes


One of the advantages to replica sets (over classic master/slave) is that they are intended to be functionally identical to each other, so you can simply use the data from one "good" node to seed any other "bad" node.