[mythtv-users] Myth cannot find tuner after reboot
Michael T. Dean
mtdean at thirdcontact.com
Tue Apr 29 23:02:50 UTC 2008
On 04/29/2008 05:52 PM, Mike Perkins wrote:
> Michael T. Dean wrote:
>> On 04/29/2008 03:38 PM, Ian Hodgson wrote:
>>> I have been using MythTV 0.20.20070821 on Ubuntu v7.04 for the last 6
>>> months without any problems. Last weekend, I shut my machine down in
>>> preparation for a weekend decorating session.
>>> Decorating done, I switched the machine back on this evening only to
>>> find that Myth cannot find the TV card. I have tried the various tests
>>> that I used when setting up the machine and have verified that the card
>>> is working. I started the MythTV back end set-up program and noticed
>>> that there were no Capture Cards listed.
>>> I reinstalled my card, but
>>> without success; MythTV no longer stores the card data that I add. A
>>> little Googleification points to a corrupted database and a reinstall as
>>> the solution.
>>> This may be a good time to update to 0.21, but I have some questions
>>> about maintaining the data in my current configuration. Whilst the
>>> recording schedules are not so important, I would like to keep the
>>> recorded programs after the update so finally to the question; what do I
>>> need to do to fix my database and install the updated release whilst
>>> still being able to access my existing MythTV recorded files.
>>> I should add that I am not experienced with mySQL so I would appreciate
>>> a pretty detailed rely.
>> backup with: http://mythtv.org/docs/mythtv-HOWTO-23.html#ss23.5
>> upgrade MythTV, run mc.sql (
>> http://mythtv.org/docs/mythtv-HOWTO-6.html#ss6.2 ), then run
>> mythtv-setup, then restore your programs, etc. with
> That's fine, Mike, but he did point out that he likely had a corrupted database.
> At what point in your backup/upgrade/restore cycle should he fix his database,
> as he might not be able to back it up in the first place?
Assuming the corruption isn't in one of the 23.7 tables, he'll "fix" his
corrupted database when he does the "DROP DATABASE mythconverg;" (which
would occur sometime before running mc.sql, or when he starts with a new
OS install or whatever).
That being said, I'm not convinced it's database corruption. If so, he
can fix database file corruption with optimize_mythdb.pl. Data
corruption is much harder to fix and often, 23.7 is the quickest,
easiest, and most effective way to do so.
More information about the mythtv-users