[mythtv-users] unexpected behaviour

Sun Nov 4 13:17:46 UTC 2018

On Sun, 4 Nov 2018 06:39:56 -0500, you wrote:

>On Sat, Nov 3, 2018 at 9:23 PM glen <glenb at glenb.us> wrote:
>
>> On Sat, 2018-11-03 at 13:21 -0400, Daryl McDonald wrote:
>>
>>
>>
>> On Sat, Nov 3, 2018, 9:00 AM Daryl McDonald <darylangela at gmail.com wrote:
>>
>>
>>
>> On Fri, Nov 2, 2018, 9:05 PM George Bingham <georgeb1962 at gmail.com> wrote:
>>
>>
>> -- George
>>
>>
>> On Fri, Nov 2, 2018 at 4:07 PM Daryl McDonald <darylangela at gmail.com>
>> wrote:
>>
>>
>>
>> On Fri, Nov 2, 2018, 9:36 AM glen <glenb at glenb.us wrote:
>>
>> On Fri, 2018-11-02 at 09:11 -0400, Daryl McDonald wrote:
>>
>>
>>
>> On Thu, Nov 1, 2018, 10:26 PM Stephen Worthington <
>> stephen_agent at jsw.gen.nz> wrote:
>>
>> On Thu, 1 Nov 2018 11:11:23 -0400, you wrote:
>>
>> >Greetings mythizens, I got 0-byte recordings for three shows airing
>> between
>> >10 &11 pm last night.
>> >This was co-incident with me switching over to Kodi, and starting my VPN,
>> >and streaming a show I had missed, I can wrap my head around losing the
>> >hdhr (network tuner) recording but the other two were on internal tuner
>> >cards. Is this normal behaviour?
>> >
>> >Does any one else using Myth and Kodi on the same box have suggestions?
>> >
>> >TIA  Daryl
>>
>> MythTV uses tuners in order, and does not ever try another tuner when
>> one fails.  So if the first tuner is a network one and you have
>> somehow screwed up the network access to the tuner, then that could
>> explain what happened.  When you say the other two recordings were on
>> internal tuner cards, how are you working out what card was used for
>> the recordings?  Were the recordings from a different source that
>> needed to use the internal cards?  When you get a failed recording,
>> you can find the tuner it attempted to use in the logs, or you can go
>> to the recording and use the I command twice (and then scroll down if
>> necessary) to see the tuner.
>>
>> How do you use a VPN?  If it is run from the MythTV box then it is
>> likely that setting up the VPN connection will have changed the
>> routing on the MythTV box in a way that prevented access to the HDHR
>> tuner.  The standard way the VPNs work is to divert all traffic
>> outside the box to the VPN connection.  Often you can set them up so
>> that local traffic on your network will not go via the VPN, but you
>> will have to do extra configuration to do that.
>>
>> Another consideration is if you have storage group locations that are
>> stored over network connections to other boxes on your network. MythTV
>> has problems with network locations not being accessible.  If
>> activating your VPN caused network storage groups to be inaccessible,
>> but mythbackend kept trying to access them, that causes mythbackend to
>> run extremely slowly due to it continually locking up in a bit of code
>> that is trying the network connection and then failing. Each time the
>> connection fails, it can move on and do a little more work, but as
>> soon as it tries the connection again, it locks up again.  Only part
>> of mythbackend is affected, but that includes the threads that do
>> recordings, so all recordings fail.  As mythbackend tries to access
>> all storage groups in that code, it does not matter if the networked
>> storage group is only used for videos or pictures - it will still
>> cause access to the recording storage groups to fail.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>>
>>
>> My only network component is the HDHR, everything else in in the combined
>> FE/BE, internal cards have UDEV rules and are used first, before the HDHR.
>> Storage is three 1TB drives, internal, one of which I just replaced
>> (impending failure) and curiously when I used Kodi it unmounted storage2 of
>> it's own volition at the time of the failure. I doubt that all three failed
>> recordings were going to the one drive, as they were simotanious, just
>> something else to scratch the head with. VPN is on the myth/kodi box only
>> and engaged when needed through the unity bar.
>>
>>
>> _______________________________________________
>>
>> mythtv-users mailing list
>>
>> mythtv-users at mythtv.org
>>
>>
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>>
>>
>> http://wiki.mythtv.org/Mailing_List_etiquette
>>
>>
>> MythTV Forums:
>>
>> https://forum.mythtv.org
>>
>>
>> why don't you test each tuner independent of myth. stop the backend and
>> test the tuners to see they are receiving signal. with hdhomerun you can
>> use the hdhomerun_config_gui util. and there are methods for the ones
>> directly attached. if those work properly, take a look at your mythtv-setup
>> and make sure the tuner setup is what you think and the storage directories
>> are correct. then start the backend and test. on the storage verify the
>> permissions are good for your storage directories. run mythtv-setup under
>> user that is running backend
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>>
>>
>>
>> I have a similar issue from time to time. I have one card that has two
>> tuners on it, but can do up to 3 recordings if two of them share a
>> multiplex. This often  happens starting at 7:00 where there will be three
>> shows all starting at the same time. Often one of them would not tune
>> within the tuning time out period and I am guessing that since it starts
>> each recording nearly at the same time that there must be additional time
>> allowed or something. Anyway, I now have one of the recordings set to start
>> a minute early and since I made that change, it hasn't missed out on any
>> recordings.
>>
>> Not sure if that's happening to you or not, but since it took place when
>> you have multiple recordings starting at the same time, maybe stagger them
>> a bit by starting one of them a minute early.
>>
>> HTH,
>>
>> George
>>
>>
>>
>>
>>
>> this was a one time episode, all is working as expected now, I think I
>> will check the permissions though.
>>
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>>
>> Interesting to know George, but for years now I have recorded by SD time,
>> 3 or even 4 episodes at the same time without incident
>>
>> I may have spoke to soon, it looks like my problems may be related to the
>> storage drive replacement. The last two news recordings have been
>> unwatchable, intermitten freeze-ups until inability to play at all, while,
>> a football recording made the same night a couple hours later plays great.
>> I'm going to use disks to check it out and am open to suggestions for
>> confirming if the new drive is a lemon or not.   TIA  Daryl
>>
>>
>> Maybe its just a coincidence, because the file system on the new drive
>> checks OK and smartmontools doesn't find any fault.?
>>
>>
>>
>> _______________________________________________
>>
>> mythtv-users mailing list
>>
>> mythtv-users at mythtv.org
>>
>>
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>>
>>
>> http://wiki.mythtv.org/Mailing_List_etiquette
>>
>>
>> MythTV Forums:
>>
>> https://forum.mythtv.org
>>
>>
>> are you using xfs ? if not change to xfs and test.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
>
>I'm using ext4 and have been for years without problems, its just since I
>replaced a drive that was about to fail. I'm finding that the system
>unmounts and remounts the drive from time to time. While using Kodi I see
>on-screen notifications saying "removable media storage 2 successfully
>removed", /etc/fstab has it mounted at boot, I used clonezilla to put the
>files,bootloader, UUID, and label on the replacement drive. Is there
>something else I need to do to keep the drive mounted? Storage 1 and 3
>remain rock solid

If the drive is on an internal SATA port, there is no way it should be
unmounting itself.  What do the logs say about why it is happening?