Tony

We have been notified by the raid card on the Jedi server that one of the drives has failed. As a result we will be replacing the drive tomorrow (September 22nd) morning between 1:00AM and 2:30AM EDT. This will be a non service impacting maintenance as the server has hot swap capability. Once the drive is replaced the server will have slightly higher i/o wait while the new drive is rebuilding. Date: 09/22/2009 Start time (EDT): 1:00am End time (EDT): 2:30am Duration: 1.5 Hours Estimated Down Time: None

We do not disable the ability for you to backup your sites via cPanel's backup tool.

It should now be back online.

We're still working on this.

Unfortunately it looks like it's not coming back online as of yet. There appears from first inspection hardware failure of some kind. The system crashed with CPU errors and now one of the network cards is not functioning. We already have a technician on the job to as we assume at this point replace faulty hardware.

The machine was able to boot back up again. All services should be coming back online again within the next 5 minutes.

We are rebooting the system now as we're unable to issue any commands via SSH and the console is littered with error messages. It should hopefully be back online in 10 minutes.

We have been alerted by our monitoring systems that the Saturn server has gone off line. We are currently investigating the issue and will up this thread as soon as we have more information.

I'm very hesitant to say this is a good idea. This plugin I believe is how you'd accomplish it: http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/ . Although reading about it from some posts on the internet some users are suggesting it'll still be littered with the sub domain references within the blog itself. It sounds like this might be more complicated than having different wordpress installs for each site. With wordpress now supporting one click updates it's not a huge chore to keep all the blogs updated.

No we do not allow that.

We're working on it should be back up soon.

The drive has been rebuilt everything is once again optimal.

It appears one of the drives has failed while we were running the verify on the array. We're placing it now there should be no service impact at all with this.

Every VPS is now back online total down time was about 13 minutes.

It is online now we're just working on getting all the VPS's back up.

The machine is now off line to replace the raid card and cables. It should hopefully be back up in 20 minutes.

We're going to be performing emergency maintenance on the Jedi server as maintenance yesterday has not solved the issues we're having with the server. This time around we're doing this immediately as another drive is reporting as failed in one portion but active in another. This is two separate drives now so we do not wish to take any chances with this and possible data loss as if another drive was dropped it would be highly likely all data would be lost. We will be replacing the raid card on the system as well as all the cables. We hope this ends the frequent drive failures this machine is reporting. This will take we estimate 20 minutes to do it all. Date: 09/17/2009 Start time (EDT): 5:35pm End time (EDT): 6:35pm Duration: 1 hour Estimated Down Time: 20 minutes

The server is running a verify on the array in the background just in case one of the drives may be bad or have bad data. Other than that everything is resolved so this is window is being marked as completed.

All virtual machines should be up and running now. Everything went as planned the firmware is up to date now and we're no longer having misinformation on the raid cards reporting system. The kernel upgrade has fixed some lingering bugs on the system itself as well. The total down time for all of this was 20 minutes. Then about another 10 to have every single virtual machine back up and running.

It has been back up for 5 minutes now we're just working on having all the virtual machines starting back up.

The server has just gone off line for this maintenance to be completed.

The Jedi server is once again acting up which we believe to be caused by the raid cards firmware. We have been suggested by datacenter technicians to upgrade the firmware to hopefully solve this issue. As it stands the raid card reports all drives healthy while reporting a degraded array. It also reports in logs that one of the drives has in fact failed. These are the reasons why tonight between 11:00 PM EDT and 1:00 AM EDT we will updating the servers raid card firmware even though this is short notice. Upgrading firmware requires the server off line so unfortunately it will be down for 15-30 minutes. Once the server is back up we will start up all virtual machine instances once again. Along with this maintenance window we're going to take the time to upgrade the nodes kernel to the latest version. We have encountered several bugs that are not service affecting but we'd like to see them fixed. We're very sorry about any inconvenience this may cause but this is necessary so that there is no chance of data loss. Date: 09/16/2009 Start time (EDT): 11:00pm End time (EDT): 1:00am Duration: 2 Hours Estimated Down Time: 15-30 minutes

Missed this topic completely. I'm sure any of our shared hosting packages are fine for what you're doing. I'm very sorry for us not responding to this topic.

Well without any information about an actual account we cannot we really help. We have no way of reproducing the issue so we cannot come up with a solution. If there was a ticket we'd know the account and be able to do some testing.

This has been completed.