HelioHost Posted February 20, 2014 Posted February 20, 2014 It appears as if the crash on Stevie has caused some Mysql issues for some people. If your database uses the InnoDB engine, then it is probably in read-only mode for the time being. This means that you can probably run most select queries, but if you try to insert, update, delete, etc to change the database it will return an error such as ERROR 1030 (HY000): Got error -1 from storage engine This read-only access will allow you to make backups of your data if you need to through cPanel. Keep in mind that we always strongly recommend users to take frequent backups of all of their data. We also recommend using a database engine that is more reliable.If your website uses InnoDB databases we strongly encourage you to convert to the default engine MyISAM as this database engine performs much better in the case that Johnny crashes again. We will do everything in our power to prevent another crash like this from happening again, but unless you require any of the features specific to InnoDB it might be wisest to convert.While we are in the very time consuming process of fixing all of the errors in all of the databases on Stevie that the crash created you may also see intermittent connectivity issues even on non-innodb databases. These should resolve themselves quickly, and we will do out best to minimize database downtime. If you have any issues with MySQL on Stevie please post them in this customer service thread http://www.helionet.org/index/topic/18427-stevie-mysql-issues/ Creating multiple identical or similar threads will just be merged. Thank you for your patience during this crash recovery period. 1
Recommended Posts