Tony

I would suggest instead of using the forwarding option setup gmail to check your email account via pop3. This way any spam you receive is not creating a bad reputation for your domain and the server you're on which is what happens when you do regular forwarding.

All services are online once again.

The server is now back online and services booting back up.

The server is currently booting back up.

The FSCK is 90% complete at this time.

The FSCK is 72% complete at this time.

The machine is back online. We will be contacting R1Soft regarding what caused the machine to crash in the way it did to hopefully make sure that we do not produce the bug that caused this again.

The file system check is 75% completed

The file system check is 50% completed

The file system check is 30% completed

The cougar server has crashed we believe due to a file system issue caused by the R1Soft system as we noted oddities in the system before it proceeded to crash. Upon rebooting the system the server is reporting possible file system issues on the home partition requiring us to run a file system check. We estimate the check will take approximately 2 hours to complete. Date: 05/02/2012 Start time (CDT): 12:21am End time (CDT): 4:20am Duration: 4 hours Estimated Down Time: 120 minutes

The file system check is complete and the server is now back online.

The check is 75% completed

The check is 50% completed

The check is 25% completed

Unfortunately it looks as though we were right about something being wrong with the machine. It looks as though there are some underlying file system issues which we need to address before the machine will be back online. Unfortunately our estimate is the machine will be down for approximately 2 hours while the file system check is performed. We estimate the machine will be up around 11pm PDT.

We're going to be rebooting the sea005 server immediately to investigate a possible kernel or hardware issue. The current time is 8:50pm PDT and the server will hopefully not be down for more than 10 minutes. If this turns out to be a hardware failure of some kind the machine may be off line for a more extended period of time. Date: 04/30/2012 Start time (PDT): 8:50pm End time (PDT): Unknown Duration: Unknown Estimated Down Time: Unknown

This has been completed the server was down for approximately 15 minutes to replace the memory. The server is once again reporting the correct amount of memory.

The sjc003 has had a stick of memory fail on it which will need to be replaced. We have scheduled this to be replaced today between 5pm PDT and 8pm PDT. This is necessary maintenance as the server is currently not running with an optimal amount of memory. We estimate that the server will be down for about 45 minutes while all the server memory is replaced. We are very sorry about this falling on the same day as a file system check but unfortunately leaving the system without an optimal amount of memory will lead to an increased chance of server degradation. Date: 04/30/2012 Start time (PDT): 5:00pm End time (PDT): 9:00pm Duration: 4 hours Estimated Down Time: 45 minutes

The machine is back online and all services are now running.

The file system check is done and the machine is currently booting back up.

The file system check is now 75% completed

The file system check is now 50% completed

The file system check is now 25% completed

The file system check is 10% completed