[mythtv-users] Corrupt cardinput and jobqueue tables

[Michael T. Dean]

On 07/06/2012 12:20 AM, John Taggart wrote:
> I recently noticed that my myth install hasn't been recording shows in 
> recent history.  A little more investigation shows that I have some 
> corrupt tables in my database.  After searching the archives I can see 
> that the answer is "restore from your most recent backup"  
> Unfortunately I haven't backed up for some time.  Is there a way to 
> restore specific tables from previous backups?  It looks like it's 
> only the cardinput and jobqueque tables are corrupt.
>
> John
>
> mythtv~$ mysqlcheck -ao --auto-repair -u mythtv -p mythconverg
> mythconverg.archiveitems                           Table is already up 
> to date
> mythconverg.callsignnetworkmap                     Table is already up 
> to date
> mythconverg.capturecard                            Table is already up 
> to date
> mythconverg.cardinput
> Error    : Incorrect file format 'cardinput'
> error    : Corrupt

FWIW, this is the error you get when you follow the advice some will 
give to "just copy the binary MySQL data files over to the new system" 
and don't do all the other MySQL administration required for doing so.  
It can always be avoided with no worries/required DBA experience by 
simply doing a proper database backup (which you should be doing, even 
if you know how to properly migrate and upgrade MySQL binary data files) 
and restore...  Just a piece of advice for future upgrades.

http://www.mythtv.org/wiki/Database_Backup_and_Restore


> mythconverg.inputgroup                             Table is already up 
> to date
> mythconverg.inuseprograms
> Error    : Can't find file: './mythconverg/inuseprograms.frm' (errno: 5)
> status   : Operation failed
> mythconverg.jobqueue
> Error    : Incorrect file format 'jobqueue'
> error    : Corrupt

If you really want to, you can spend some time learning mysqlcheck and 
may be able to fix these issues.  That said, if you choose not to (and, 
really, I don't know that I'd trust my database schema or data with this 
amount of corruption), the approved-by-MythTV solution is to back up 
your existing database (which, in your case, may require dropping some 
of the corrupt tables--so is likely to be destructive), then doing a 
partial restore of the database ( 
http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_of_a_backup 
), and then reconfiguring all of MythTV from scratch.  This approach 
will maintain non-recreatable information about existing recordings and 
recording history, but all other information will have to be re-generated.

Mike