Synopsis
At 6:25am a black lasting only a few seconds has been recorded by building logs.
7:00am 2 ITS staff from arrive upon being contacted due to an error with a server not restarting and begin diagnostics.
7:10am File server isolated as a problem.
7:20am Diagnostics complete with only the file server remaining as an issue, it is suspected the black out has caused physical damage to the system and further investigation on the server is required to pin point the problem.
7.40am Suspected problems have been narrowed down to either hard drive failure leading to the corruption of data or to write errors on the hard drive both are directly connected to the blackout.
8.00am Problem has been identified as a corrupt file system due to write errors which initiated during the time of the power outage. The physical hard drive has passed reliability tests and is deemed acceptable for data recovery/repairing.
8.05am Repair failures result in the use of backups.
10.30am Full system backups used to recover systems, normality restored.

Overview:
When dealing with a server that refuses to start there are many causes that could in turn lead to a long diagnostic process which may or may not be resolved with a specific incident.
In this case we know of a power outage and a lack of functionality which corresponds to the same time as the black out, this will significantly aid in the diagnostic process as symptoms will generally range from hardware damage by the power outage or software corruption.