[mythtv-users] ts File Migration to New Backend

Mon Nov 18 15:11:12 UTC 2024

Hi Stephen!

Summary: No change yet.

> >> /No plugins directory /usr/lib/mythtv/plugins/
> >> /==> This for options like Weather, Streaming, etc?/
> Yes.  You will need to install the appropriate MythTV plugin packages.
> I have mythmusic and mytharchive installed:

Looking at the webpage interesting options but doesn’t appear to be 
required, so not causing the problems here.

> This lists all packages that are installed and have "myth" in the
> name:
>
> root at mypvr  <http://lists.mythtv.org/mailman/listinfo/mythtv-users>:~#*apt list --installed | grep myth*

My list is only about a dozen or so:

libmyth-python/noble,noble,now 
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed,automatic]

libmyth/noble,now 2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 
amd64 [installed,automatic]

libmythes-1.2-0/noble,now 2:1.2.5-1build1 amd64 [installed,automatic]

libmythtv-perl/noble,noble,now 
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed,automatic]

mythes-en-au/noble,noble,now 2.1-6 all [installed]

mythes-en-us/noble,noble,now 1:24.2.1-1 all [installed]

mythtv-backend/noble,now 
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64 
[installed,automatic]

mythtv-common/noble,now 
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64 
[installed,automatic]

mythtv-database/noble,noble,now 
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed,automatic]

mythtv-frontend/noble,now 
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64 
[installed,automatic]

mythtv-transcode-utils/noble,now 
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 amd64 
[installed,automatic]

mythtv/noble,noble,now 
2:34.0+fixes.202411041418.c376437559~ubuntu24.04.1 all [installed]

> Mythfrontend can now tell you where a recording is stored, as long as
> it can find it (not marked with an X).  On a recording in the list,
> hit I on the keyboard twice and scroll if necessary to find the
> storage location (look for "Recorded Pathname").

Mine all have X’s on BE5, looked but didn’t see an option for Recorded 
Pathname.

> If there are no valid storage directories to record to, I suspect that
> mythbackend has a default directory it will use.  It is likely
> somewhere under /var, so this should find it, if it exists:
>
> *sudo find /var -iname "*.ts"*

Things get stranger!
barry at BE5:~$ sudo find /var -iname "*.ts"
barry at BE5:~$ 	<no response>

barry at BE5:~$ sudo find / -iname "*.ts"
/usr/share/mythtv/themes/default/dummy768x576p50.00.ts    (plus several more)
/mount/WD_4TB/Default/10004_20241105170000.ts
/mount/WD_4TB/Default/14705_20230825053500.ts  (continues with the whole list)

> So, can you see that drive mounted on /mount/WD_4TB?
>
> First, does the mountpoint exist?
sudo ls -al /mount

barry at BE5:~$ sudo ls -al /mount
total 12
drwxrwxrwx  3 barry  barry  4096 Nov  4 12:24 .
drwxr-xr-x 24 root   root   4096 Nov  4 12:24 ..
drwxrwxrwx 16 mythtv mythtv 4096 Nov 14 15:20 WD_4TB

> Does the system think the drive is mounted?
sudo mount | grep WD_4TB

barry at BE5:~$ sudo mount | grep WD_4TB
/dev/sdb2 on /mount/WD_4TB type ext4 (rw,nosuid,nodev,relatime,x-gvfs-show,x-gvfs-name=WD_4TB)

> Then does the mountpoint have any directories or files under it?
> sudo ls -al /mount/WD_4TB/

barry at BE5:~$ sudo ls -al /mount/WD_4TB/
total 108
drwxrwxrwx 16 mythtv mythtv  4096 Nov 14 15:20 .
drwxrwxrwx  3 barry  barry   4096 Nov  4 12:24 ..
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 Banners
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 CoverArt
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 DB_Backups
drwxrwxrwx  2 mythtv mythtv 36864 Nov 17 08:16 Default
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 FanArt
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 LiveTV
drwxrwxrwx  2 mythtv mythtv 16384 Apr 26  2019 lost+found
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 Music
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 MusicArt
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 Photographs
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 Screenshots
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 Trailers
drwxrwxrwx  4 mythtv mythtv  4096 Nov 14 15:20 .Trash-1000
drwxrwxrwx  2 mythtv mythtv  4096 Nov 16 10:04 Videos

> My best guess for the problem would be that you forgot to create the
> mountpoint directory.  I do that all the time!.  To fix that:
>
> sudo su
> mkdir -p /mount/WD_4TB

barry at BE5:~$ sudo mkdir /mount/WD_4TB
mkdir: cannot create directory ‘/mount/WD_4TB’: File exists
barry at BE5:~$
barry at BE5:~$ sudo mkdir -p /mount/WD_4TB
barry at BE5:~$
==> Pretty sure the mountpoint is there so just testing use sudo; previous experience is try to recreate get the error.  OTOH the parent option surprised me – no error so did something.

chown mythtv:mythtv /mount/WD_4TB
chmod a-rwx /mount/WD_4TB	==>  DON’T!!  SeebelowRethink next morning:
Drive would not be mounted at this point so umount and continue.
mount /mount/WD_4TB
exit

The "chmod" line is optional - what it does is remove all permissions
on the mountpoint directory itself, before anything is mounted on the
mountpoint.  So if nothing is mounted on the mountpoint, software that
expects something to be mounted and goes ahead and writes to the
mountpoint directory or to directories below the mountpoint directory
will get an error, instead of working and creating files below the
mountpoint directory that will then be masked when something gets
mounted on the mountpoint.Do NOT do the "chmod" command if there is
a drive mounted on the mountpoint - it would be changing the
permissions on the mounted drive rather than the mountpoint itself.

> >/Quick thought: have a look at your storage groups, see where they 
> have been set to./
>
> Yes, that sounds like the problem.  MythTV will only see recording
> files that are in a storage group directory.  On BE5, the restored
> database will have the storage groups set to the same directories as
> they were on BE4.  So the directories in your storage group settings
> have to exist in the same places on BE5 as they were on BE4.
>
> To see all the storage groups:
>
> sudo mysql		==>   sudo mysql mythconverg
> select * from storagegroup order by groupname,dirname;

*+----+-------------+----------+---------------------------+*
*| id | groupname | hostname | dirname |*
*+----+-------------+----------+---------------------------+*
*| 30 | Banners | BE5 | /media/MythTV/banners |*
*| 38 | Coverart | BE5 | /media/MythTV/coverart/ |*
*| 35 | DB Backups | BE5 | /media/MythTV/db_backups/ |*
*| 18 | Default | BE5 | /media/MythTV/recordings |*
*| 34 | Fanart | BE5 | /media/MythTV/fanart |*
*| 19 | LiveTV | BE5 | /media/MythTV/livetv |*
*| 32 | Music | BE5 | /media/MythTV/music |*
*| 33 | MusicArt | BE5 | /media/MythTV/music_art |*
*| 31 | Photographs | BE5 | /media/MythTV/photographs |*
*| 29 | Screenshots | BE5 | /media/MythTV/screenshots |*
*| 37 | Trailers | BE5 | /media/MythTV/trailers/ |*
*| 36 | Videos | BE5 | /media/MythTV/videos/ |*
*+----+-------------+----------+---------------------------+*
*12 rows in set (0.00 sec)*

So that might be the problem: the old BE4 is set for recordings 
(lower-cased) and the new BE5 for Default. I’m guessing either a rename 
project <slight whimper> or perhaps a bunch of soft links (thinking 
easier as mostly copy and paste but what happens with the eventual BE6?)

I did reboot the Backend in case...  nope.

Thank You!!

Barry

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20241118/1ea4ebc5/attachment.htm>