I figured it out. It was part hidden problem, part boneheadedness. My real problem was that when I rebooted my myth server, I forgot that I had my recordings directories NFS mounted to my front ends, and I forgot to reboot one of them, so it was locking up over a broken NFS mount. At the same time, I had some recordings that had been accidentally erased, but were still in the database. The weren't causing the problem, and had been broken for a while, but I hadn't noticed. I rebooted all of my front ends, and everything works now, though I still have the broken recordings that I need to delete.<div>
<br></div><div>Now I have the question of how to finish my upgrade. I put in the kernel with the PAE extensions, so I can see all 8 GB of memory. I can still upgrade to the 64 bit kernel, but that would require reinstalling everything. I'll probably seave it with the PAE kernel, install the mythbuntu repos, and upgrade to 0.24.</div>
<div><br></div><div>Thanks to the community for the help.</div><div><br>Matt</div><div><br><div class="gmail_quote">On Sat, Nov 5, 2011 at 11:46 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 11/05/2011 01:25 AM, Matthew Asplund wrote:<br>
> So, I came up with a plan that I thought would work. I built my new<br>
> machine, ran a bunch of tests to make sure that there were not<br>
> hardware problems. Then I transferred my drives from the old machine<br>
> to the new machine. I figured to get it working with the old<br>
> installation on the new hardware. Then I would do the upgrades from<br>
> there.<br>
><br>
> So, I transferred the disks to the new machine, changed the dhcp entry<br>
> on my router to give it the same IP address as my old server, and<br>
> booted it up. It came up fine, and everything worked, and was in the<br>
> right place. But when I tried to connect to the backend from one of<br>
> my front ends, it connected just fine, but it couldn't find the files.<br>
> It had the recordings in the database, but when I tried to play any<br>
> of them, it said that the files for the shows could not be found. I<br>
> checked, and the recordings directories were mounted in the right<br>
> places, and the files were there. When I checked out the mythbackend<br>
> log file, it said that it was looking for files that weren't there,<br>
> and sure enough, the files weren't there.<br>
<br>
</div>Were other recording files there?<br>
<div class="im"><br>
><br>
> So, is there something funny about moving the database like this.<br>
> Does the filename somehow depend on some id field from the machine?<br>
> WIll this be fixed by doing a backup and restore of the database?<br>
<br>
</div>No. The only thing that you have to be careful to line up is the host<br>
name--the recordings must exist on the recording host. If you change<br>
host names, you'll need to update the host name in the database using<br>
the restore script (<br>
<a href="http://www.mythtv.org/wiki/Database_Backup_and_Restore#Change_the_hostname_of_a_MythTV_frontend_or_backend" target="_blank">http://www.mythtv.org/wiki/Database_Backup_and_Restore#Change_the_hostname_of_a_MythTV_frontend_or_backend</a><br>
, but no restore is required).<br>
<br>
Most likely your Storage Groups configuration needs fixing to contain<br>
the directory locations at which you've mounted the recording<br>
directories. I'm guessing that this changed.<br>
<br>
Mike<br>
<div><div></div><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br></div>