MythTV Rebuild

I wanted to grab the large HDD out of my MythTV box so I can take that with me to Vancouver.  So I swapped it for a 160GB I had sitting around.  It all went surprisingly well.  Here's what I did:
1. Installed Mythbuntu on the new disk
2. Once that's booted stop mysql (sudo /etc/init.d/mysql stop)
3. Copy the database files from the old partition, they can be found in /var/lib/mysql/mythconverg.  It pays to make a backup but make sure you don't leave it in /var/lib/mysql or mysql will try to use it as a database.
4. Copy the old recordings to the new recordings folder on the new drive.

Now I was at a point were I could watch recordings (Yay!).  Live TV and recordings still wouldn't work.  I noticed in system settings that the tuners were both unavailable.  to fix this run MythTV setup and delete all the capture cards and recreate them.

I also had a quirk where mythweb gave an error that the table weatherscreens didn't exist.  I rebuild the tables using this process
1. Connect to mysql using the syntax mysql -u mythtv -p
2. Enter the password from /home/mythtv/.mythtv/mysql.txt
3. Type use mythconverg;
4. Enter these commands to build the tables:
DROP TABLE IF EXISTS `weathersourcesettings`; 
CREATE TABLE `weathersourcesettings` ( 
`sourceid` int(10) unsigned NOT NULL auto_increment, 
`source_name` varchar(64) NOT NULL, 
`update_timeout` int(10) unsigned NOT NULL default '600', 
`retrieve_timeout` int(10) unsigned NOT NULL default '60', 
`hostname` varchar(255) default NULL, 
`path` varchar(255) default NULL, 
`author` varchar(128) default NULL, 
`version` varchar(32) default NULL, 
`email` varchar(255) default NULL, 
`types` mediumtext, 
PRIMARY KEY (`sourceid`) 
) ENGINE=InnoDB DEFAULT CHARSET=latin1; 

DROP TABLE IF EXISTS `weatherscreens`; 
CREATE TABLE `weatherscreens` ( 
`screen_id` int(10) unsigned NOT NULL auto_increment, 
`draworder` int(10) unsigned NOT NULL, 
`container` varchar(64) NOT NULL, 
`hostname` varchar(255) default NULL, 
`units` tinyint(3) unsigned NOT NULL, 
PRIMARY KEY (`screen_id`) 
) ENGINE=InnoDB DEFAULT CHARSET=latin1; 

DROP TABLE IF EXISTS `weatherdatalayout`; 
CREATE TABLE `weatherdatalayout` ( 
`location` varchar(64) NOT NULL, 
`dataitem` varchar(64) NOT NULL, 
`weatherscreens_screen_id` int(10) unsigned NOT NULL, 
`weathersourcesettings_sourceid` int(10) unsigned NOT NULL, 
PRIMARY KEY (`location`,`dataitem`,`weatherscreens_screen_id`,`weathersourcesettings_sourceid`), 
KEY `weatherdatalayout_FKIndex1` (`weatherscreens_screen_id`), 
KEY `weatherdatalayout_FKIndex2` (`weathersourcesettings_sourceid`), 
CONSTRAINT `weatherdatalayout_ibfk_1` FOREIGN KEY 
(`weatherscreens_screen_id`) REFERENCES `weatherscreens` (`screen_id`) 
ON DELETE CASCADE ON UPDATE CASCADE, 
CONSTRAINT `weatherdatalayout_ibfk_2` FOREIGN KEY 
(`weathersourcesettings_sourceid`) REFERENCES `weathersourcesettings` 
(`sourceid`) ON UPDATE CASCADE 
) ENGINE=InnoDB DEFAULT CHARSET=latin1; 

Done, now mythweb works too.

Comments

Unknown said…
Cool, solved my problem on a update from 0.22 to the 0.23rc2
6 April 2010 at 04:08
Post a Comment

Popular posts from this blog

Using Homebridge and Broadlink RM Mini to automate

Image
In this post, I'll be documenting how I configured a Broadlink RM Mini to work with HomeKit using the Homebridge server I built in my last post . The Broadlink RM Mini is a small IR Blaster that sits on the coffee table and sends IR signals when requested. They're cheap, and they work: In hindsight, for a little more you can also get the RM Pro which (I found out later) includes a thermometer. I added a DS18D20 thermometer to my Raspberry Pi to get around this mess up. To start with, you'll need to unpack your RM Mini and get it setup on your network. To do this, you'll need to download their "e-Control" app and follow through the setup. There's a good summary of these steps here: https://spectrum.co.ae/blogs/technology/how-to-configure-broadlink-devices, you can just stop before step 5 if you don't plan to use the e-Control application. Now we need to add homebridge-broadlink-rm to our Raspberry Pi. Connect to the pi console, SSH or local...
Read more

Using HomeBridge on a Raspberry Pi to control devices from HomeKit

Image
If you’ve got a selection of devices that you’d like to control using iOS HomeKit, setting up homebridge might be a good solution. In short, it’s a platform which acts as a “bridge” between your devices and “HomeKit”. There are MANY plugins available for it: https://www.npmjs.com/search?q=homebridge. Here’s how I use it: I have a Broadlink RM Mini that controls my AC, TV, Radio and a digital photo frame using homebridge-broadlink-rm: https://www.npmjs.com/package/homebridge-broadlink-rm  I have it enable/disable an indoor camera using MotionEye using homebridge-script2: https://www.npmjs.com/package/homebridge-script2  With all those plugins, the options are almost endless if the device is connected to the network. To do this I use a Raspberry Pi 2. To get started, you’ll need to have raspbian installed and running. To do this, there are various guides available, including this official one: https://projects.raspberrypi.org/en/projects/raspberry-pi-getting-started. ...
Read more

LetsEncrypt and AWS ELB Load Balancers

Image
This is something that I've struggled to find good information on. You've setup your IIS Web Servers in AWS, get them working nicely behind an ELB Load Balancer, now you want to apply a free LetsEncrypt SSL Certificate. This guide will take you through that process. Here's he basic run down: Design your Infrastructure to allow for a Central Validation Server Setup and IAM identity with access to manage your certificates Setup an initial certificate Apply the new certificate to a new ELB Re-generate the LetsEncrypt Certificate with a script to automatically update the ELB Certificate Design your Infrastructure to allow for a Central Validation Server One concept discussed in LetsEncrypt's Integration Guide  is a Central Validation Server. To abbreviate this considerably, this is setting up one of the servers to manage the certificates. Fortunately ELB2 presents the certificate to clients and it doesn't matter which certificate is presented by the server....
Read more