knoppmyth.net

[cesman]

If you experience system crash it is probably a good idea to check the MySQL table to ensure your tables have not become corrupted. To do this:

[jesse]

You can do the same thing from a separate computer by using MySQL Control Center (http://www.mysql.com/downloads/mysqlcc.html). You just right click on the table(s) then go to Tools. You can choose from Analyze, Check, Optimize, Repair.

This can be done from a Windows or Linux box.

[notivo]

you can try this command:

cd /var/lib/mysql/mythconverg
myisamchk -f -r *.MYI

it force repairs all broken tables

[Human]

[tjc]

There are some really good reasons that force repair is not the default option... Mostly that it's not always safe. This would be kind of like your car always starting up in gear...

[tvmyth]

I was looking for this post, and several other posts stated ...search for the post containing database and repair
Unfortunatly my searches failed because the word database was no where in this post, so here it is.

[lynchaj]

I had my hda1 partition fill up for some mysterious reason and then the mythtvbackend froze up and the database got corrupted. So what I did was:

/etc/init.d/mythtv-backend stop
mysqlcheck -c -umythtv -pmythtv mythconverg

heres where I detected something was wrong with the database. Lots of error messages about tables

so then I did:

mysqlcheck -r -umythtv -pmythtv mythconverg

which attempted to repair the database. Some errors went away but about half stayed. "Error 28" which you can figure out what that means by using

perror 28

prints out that it means "disk full" or something like that

so I was starting to sweat and locate the KnoppMyth R4V5 reinstall disk and told my wife that all her Christmas shows were probably lost. So, that motivated me to keep looking.

Did some research and found this command to repair the MySQL tables


cd /var/lib/mysql/mythconverg
myisamchk -r *.MYI

which fixed all the table errors, reran

mysqlcheck -c -umythtv -pmythtv mythconverg

all errors gone, so looking good. Rebooted, and crossed my fingers.

Sweat. More sweat,

finally it booted and everything was normal. All the wifes Christmas shows were saved and I slept indoors that night. Happy endings are always nice when its snowing outside.

Andrew Lynch
_________________
Dayton Ohio MythTV Users Group http://www.dma.org/mailman/listinfo/day-mug

Automatic Installer for MythTV on Debian. Ideal for new users and/or older low resource PCs! http://amicus.sourceforge.net

[mccoyn]

After repairing my tables everything worked fine for a few days. Then, suddenly, it stopped recording. It still lists scheduled recordings, but nothing gets recorded.

Some investigation showed that the hda4 (where my recordings are at) was full. I tried manually deleting the oldest recording that was supposed to auto-expire. Everything worked like it was supposed to, except that when it was done, the recording was still listed. Next, I tried to delete the file manually (getting the filename from mythweb.) This resulted in a file not found message. Apparently it is listed in the database, but there is no file to delete. This leads to an error, which seems to block the auto-expire.

Here is how I fixed it:

edit: A patch has been added to CVS which prevents this problem from stopping the auto-expirer. One partial fix, then, is to install from CVS.

1. From a console create an empty file using a text editor.

[spud]

I was experiencing:
1) painfully slow skipping
2) commercial skip stopped working
3) recording editor would not start

I performed the steps described by cesman, which correctly identified recordedmarkup.MYI' as corrupt and repaired it.

One more step was required after repairing specifically the "recordedmarkup.MYI" database to fix the skipping problems.

mythcommflag --rebuild --all

This command rebuilds the seek table.

[mal1ch1]

On running the above command, I'm receiving a message "Parser not found for Codec Id: 94210 ! and also "You probably should modify the Master Server settings in the setup program and set the proper IP address".
And when I do the myisamchk -f -r *.MYI, it seems to be fixing things, but if I repeat it, it goes through the same sequence.

[dspille]

[BluesBrian]

I was having the same problem.. and SQL Error in MythWeb. (I'm using R5C7) using myisamchk -r *.MYI pretty much did the trick.

[bigbro]

[silentmic]

I had this problem. The /usr/sbin/mysqld and the /usr/share/mysql were completely gone. I started copying files from an old installation I had but gave up. I fixed it by reinstalling mysql using apt-get mysql-server. The check indicated no corruption of the database.

[bruce_s01]

Just to say thanks for the fix.

Bruce S.
_________________
Updated 2010/06/26: Athlon64 3700+ Asus A8N4-SLI Deluxe
1Gb PC 3200, 200Gb+250Gb SATA HDD,
DVD-RW LG , Gigabyte GV-NX66128DP
Hauppauage Nova-T 500 + Hauppauge Nova-(D)T 500,+ Nova HD S2 LinHes R6 RC2