[mythtv-users] MythTV does not see new Default Storage Group drive

Stephen Worthington stephen_agent at jsw.gen.nz
Sat Nov 23 01:49:36 UTC 2013


On Fri, 22 Nov 2013 18:24:28 -0500, you wrote:

>
>Added 5th drive to Default Storage Group and it is not 
>recognized by MythTV in the FrontEnd System Status - Machine 
>Status.  Also, I cannot make it record to the 5th drive.
>
>Ubuntu 12.04  32 bit desktop
>
>MythTV  fixes/0.25
>
>I have a total of five discs in the Default Storage Group.
>
>BigDisc3 and BigDisc4 are recently added.  MythTV recognizes all 
>but BigDisc4.  They all seem to automatically mount okay, as far 
>as I can tell.  Here are the particulars:
>
>'Default' Storage Group Directories in MythTV Setup:
>/var/lib/mythtv/recordings

That looks like a bad idea - the /var/lib/mythtv/recordings directory
is usually on your system partition.  Which means that your system
partition can fill up with recordings.  And a full system partition
causes has the potential for many different sorts of disasters.

>/media/BigDisc4/VideoRecordings/
>/media/BigDisc3/VideoRecordings/
>/media/BigDisc2/VideoRecordings/
>/media/BigDisc/VideoRecordings/
>
>/etc/fstab:
>UUID=68ef0205-d5e2-46ae-86e9-999999999999	/media/BigDisc	ext4
>UUID=2f87c252-9683-404d-96b1-999999999999	/media/BigDisc2	ext4
>UUID=bd275fd5-8a37-4ac4-9ecb-999999999999	/media/BigDisc3 ext4
>UUID=f43515d8-f21f-4b3c-a57c-999999999999	/media/BigDisc4 ext4
>
>napier at colossus:~$ sudo mount
>/dev/sde1 on / type ext4 (rw,errors=remount-ro)
>proc on /proc type proc (rw,noexec,nosuid,nodev)
>sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
>none on /sys/fs/fuse/connections type fusectl (rw)
>none on /sys/kernel/debug type debugfs (rw)
>none on /sys/kernel/security type securityfs (rw)
>udev on /dev type devtmpfs (rw,mode=0755)
>devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
>tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
>none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
>none on /run/shm type tmpfs (rw,nosuid,nodev)
>/dev/sdb2 on /media/BigDisc type ext4 (rw)
>/dev/sdd1 on /media/BigDisc2 type ext4 (rw)
>/dev/sdc1 on /media/BigDisc3 type ext4 (rw)
>/dev/sda1 on /media/BigDisc4 type ext4 (rw)
>binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
>(rw,noexec,nosuid,nodev)
>gvfs-fuse-daemon on /home/napier/.gvfs type 
>fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=napier)
>
>napier at colossus:~$ sudo ls -l /media
>total 16
>drwxrwxrwx 8 napier napier 4096 Sep 16 16:00 BigDisc
>drwxrwxrwx 6 napier napier 4096 Feb 17  2013 BigDisc2
>drwxrwxrwx 5 napier napier 4096 Nov 21 20:46 BigDisc3
>drwxrwxrwx 4 napier napier 4096 Nov 21 20:59 BigDisc4
>
>napier at colossus:~$ sudo ls -l /media/BigDisc3
>total 20
>drwx------ 2 root   root   16384 Nov 21 17:26 lost+found
>drwxrwxrwx 2 mythtv mythtv  4096 Nov 22 16:19 VideoRecordings
>napier at colossus:~$
>napier at colossus:~$
>napier at colossus:~$ sudo ls -l /media/BigDisc4
>total 20
>drwx------ 2 root   root   16384 Nov 21 17:13 lost+found
>drwxrwxrwx 2 mythtv mythtv  4096 Nov 22 16:19 VideoRecordings
>
>I've looked through several logs without seeing anything about 
>BigDisc4 and I keep staring at the two discs and I can't see why 
>BigDisc3 is and BigDisc4 is not recognized.

Maybe a typo?  It is very easy to miss one even when looking hard. So,
is your list of storage group directories above machine generated, or
did you type it?


More information about the mythtv-users mailing list