<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Sep 27, 2014 at 3:56 PM, Brian S <span dir="ltr"><<a href="mailto:inanimatecrbnrod@hotmail.com" target="_blank">inanimatecrbnrod@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br></blockquote>
Next, I was able to get the mysql daemon to start by adding the "innodb_force_recovery = 2" flag to /etc/mysql/my.cnf. First tried =1 and got the same error as previously noted.<br>
<br>
With mysql up and running I checked all databases/tables with:<br>
mysqlcheck -c -u root -p --all-databases<br>
Output indicated all tables in both the mysql database and the mythconverg database were "OK." (again can attach output if useful).<br>
This may have been a bad idea, but with mysql running with the force recovery option, I was able to start the BE process successfully and begin watching a program on the FE. The DB check on mythweb also indicated all the mythconverg tables were ok.<br>
<br>
So based on what I have been able to find, the next step seems to be to dump all the tables and then restore a copy of them, however based on what I have so far, a corrupt table doesn't seem to be the problem(?), so I'm not sure dumping/restoring is the best way to go. Would this be the logical next step, or should I try something else?<br>
<br>
Thanks again for all your help.<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>The reason myisamcheck didn't work is because it's for fixing ISAM tables, not InnoDB. It looks like you've got it working, I would make a backup, just so you have one, but it's probably not necessary. I'd also remote the force recovery flag, otherwise it's likely going to do it every time you start mysql.</div><div><br></div><div>Good work!</div><div><br></div><div>Tom </div></div></div></div>