[mythtv-users] Salvaging myth database after crash (latin1?)

Dale Pontius DEPontius at edgehp.net
Sat Aug 28 18:48:02 UTC 2010


Same system as other post.  It's crashed, but I managed to get most of
my information back, and it looks as if all that I'm missing is the very
last mythdb backup, apparently because the crash happened then.

I have my entire media directory, and appear to have the /var/lib/mysql
directory where MySQL keeps the binary form of the database.

I'm reinstalling Gentoo now, and noticed that as mysql flew by that I
was building it without the "latin1" flag.  I know that on a completely
new install it won't matter, and I'm trying to recover what was a
happily functional mythtv-0.22 installation.  But this database began
it's life as a latin1 mythtv-0.18 or 0.19 install.  Has the upgrade to
0.22 wiped all fear of latin1 out of there, or are there still some
problems waiting in the wings.  Should I be rebuilding mysql with the
latin1 feature, or should I be expressly avoiding it?

Though I have the backups, I think I'm going to try first dropping
/var/lib/mysql in place of the fresh installed one,  (moving it aside,
in case this doesn't work) and see what happens if I then start mysql
and check / repair the database.  I guess I can always scrap it all and
start from the backup, if I have to.  Does mythrestore need me to
initialize the database first, as on a new install, or does the backup
take care of all of that for me?

Thanks,
Dale


More information about the mythtv-users mailing list