• 2008-09-21T21:00 (approx) kernel oops
• 2008-10-04T09:30 machine non-responsive. Console frozen with no messages. Power cycled by bills.
• 2008-11-15T15:57 no response nothing on console power cycled by bills
• 2008-11-15T22:20 no response nothing on console power cycled by bills
• 2008-11-20T00 (approx) no response on console, power cycled by pap
• 2008-11-26T11:06 no response on console, power cycled by pap; was under heavy load
• 2008-11-27T08:30 no response on console, power cycled by bills; was under heavy load
• 2009-01-23T14:15 no response on console; was under heavy load
• 2009-02-19T08:35:05 IDE Channel 20 Device Failed
• 2009-03-23T10:22:50 IDE Channel 20 Device Failed
• 2009-06-01T06:23:53 Degraded unit: unit=0, port=1 - disk#2 failed
• 2011-05-30T14:00 Kernel panic, power cycled by eam, see console message
• 2012-01-24T03:59:06 system unresponsive, nothing on console, power cycling not working. MHPCC manually power cycled - no response. Having Rita who is onsite verify BIOS settings. IPP027 booted up with no issues. Cindy to verify with Rita what was done to get IPP027 back online. (2012-01-24:09:33:21)
• 2013-01-16 system became unresponsive about 1 week ago. Attempts to power cycle didn't help -- no response on monitor. With troubleshooting efforts today we found the system would start up with one of the CPUs removed. We discovered it wasn't a failed CPU, but failed CPU socket. The CPU itself had very little heat sink cream, which leads us to believe it overheated and damaged the CPU socket. All 1TB RAID disks were swapped with new 2TB disks and the restarted with 1 CPU. (Rita and Haydn)