We are currently facing an outage on Matrix server due to a failed HDD. However, the data are fully protected with our Raid-1 redundancy system. We are curently replacing the failed drive from RAID array and cloning a new disk from the primary HDD. We expect to complete this task soon. After that, the server will run stable. We apologize for the inconvenience caused.<\/p>\n
** UPDATE #1**<\/strong> ** UPDATE #2**<\/strong> ** UPDATE #3**<\/strong> ** UPDATE #4**<\/strong> ** UPDATE #5**<\/strong> ** UPDATE #6**<\/strong> ** UPDATE #7**<\/strong> We are currently facing an outage on Matrix server due to a failed HDD. However, the data are fully protected with our Raid-1 redundancy system. We are curently replacing the failed drive from RAID array and cloning a new disk from the primary HDD. We expect to complete this task soon. After that, the server<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[5],"tags":[],"yoast_head":"\n
\nThe drive clone process errored out. We are currently attempting to manually copy over
\nthe data from old drive to the new drive. Most likely, this means the
\nhard drive has some severely damaged section of the disk. Quite often we are
\nable to manually copy over the data to a new drive (thats what we’re trying
\nnow). We are also double checking the RAID backup drive to check the status of
\ndata.<\/p>\n
\nAll of the HDD partitions copied successfully except for \/home, which is still in
\nprogress. It has currently restored 50% and still in progress. So it will take quite a bit of
\ntime yet (couple more hours most likely). \/home partition contains all the real data (including files, databases, emails etc).<\/p>\n
\nThere is about 5GB remaining data to copy. So far, the data recovery has been going perfectly fine, with no loss of data. The recovery process took so long due to the huge amount of data we had to copy over (few hungreds GB). We are going to finish the restore process very soon and get the server back online as soon as possible. Again, we truly apologize for the inconvenience caused and appreciate your patience.<\/p>\n
\nAll data files have been successfully restored. We are now restoring the MySQL databases. It’s taking more time than expected because the faulty drive keeps shutting off intermittently…and we have to reboot the server everytime to resume the restore process (from the point where it rebooted). We will post an update here as soon as we are done.<\/p>\n
\nThe server is now online. All data files & SQL DBs have now been successfully restored. We are now fixing the permissions of web files, so that the webserver can parse the pages corrrectly. Until we finish fixing the file permissions, you may see “404 error” while browsing your site. This is a temporary issue and we are already working to fix it. We’ll post an update here soon.<\/p>\n
\nThe server is now running in stable condition. We are now restoring individual sites from our daily backup copies (dated Aug-07-2009 1AM PST). 50% sites are already fully online and the site-restore operation is still in progress. We’ll update here when all the sites are fully restored from backup.<\/p>\n
\nThere are few sites still remaining in the restore queue & currently in progress. These sites are taking time to restore to to bigger sizes (more than 10GB of data). Of your site still shows “404 error”, please open a support ticket and our techs will restore your site on priority basis (instead of queing).<\/p>\n","protected":false},"excerpt":{"rendered":"