The failed drive on Aries has been replaced and is building in to the RAID array at this time. This process usually takes around 24 hours on an active system with the legacy drives on Aries, but service speeds should remain stable throughout this time with only minor intermittent speed issues.

The Aries server is now back online. We apologize for this unscheduled downtime and would like to thank everyone for their patience and understanding. We will be needing to replace a drive on the Aries server ASAP, which may slow the server down for a while. We will announce when this is taking place.

The Aries server has encountered a RAID error which has caused a system crash. We are recovering the system at this time, all looks well so we are just waiting for a FSCK to complete at this point. We anticipate this process to take around one hour. We are closely monitoring the process and will post updates here if any further information becomes available.

We have restored service to Node5 after a complication with R1Soft CDP Backups and the operating RAID array was encountered. The system is building a new drive in to the RAID array now, which will cause intermittent speed issues, depending on where you files are physically located on the actual hard drives (in fact it is one of the least utilized drives, so speed issues should be minimal). As with all Virtuozzo system crashes, Quotas must be re-calculated. This occurs over the course of the next several hours as each VPS is taken down, recalculated, and then brought back online, which will cause roughly 15-30 minutes of additional downtime for most VPS configurations. This will occur over the next 12-16 hours, and unfortunately we can't say when it will happen for your VPS, but it will happen.

We would like to sincerely apologize for the downtime today on Node5. We do our best to avoid service problems related to new technologies (in this case: R1Soft CDP 3.0), but we have not succeeded in this regard with the new backup software. We are interfacing directly with R1Soft concerning how to reduce the system strain encountered when actually taking backups. Until we can do that, however, backups will be suspended for the operating Virtuozzo nodes in Chicago.

We have been investigating the issue causing Node5 to crash. We will update this post when we have more information and a definitive timeline to service restoration. Thank you for your continued patience and understanding.