Yoshiofthewire

Members
 View Profile  See their activity

  • Posts

    72

  • Joined

  • Last visited

 Content Type 

Posts posted by Yoshiofthewire

    [Support] urlxl - HDHomeRun DVR [20210501beta1]

    in Docker Containers

    Posted

    Got it installed and it seems to be starting it's first recordings - crossing my fingers. I was expecting some kind of configuration to complete (with the docker) but other than setting up the share it seems good to go.

     

    If you have installed the DVR somewhere else, there really is no setup.  If you haven't you do need to configure your HDHomerun Tuner.

    Your configuration will survive the complete deletion of the docker and container.

     

     

    Out of curiosity, I have question regarding doing recordings using this docker.

     

    Would it work with HDHomeRun Prime? I have Verizon FIOS + ceton tuners and recordings are done with Windows Media Center. Except for couple channels content is not copy protected, but still Windows requires PlayReady to be activated in order to make recordings. How would it work with HDHomeRun  and this dvr docker? Recording are done on unRaid and they are available to all the clients on the network without restrictions?

     

    SiliconDust website has a product called HDHomeRun DVR. Are they talking about this software that is part of this docker?

     

    I am using an HDHomeRun Prime on Verizon.  I can record and watch anything that is not DRMed.  I can't watch any channel that has DRM. YMMV

    So, I can watch anything that is not FX, FXX, Fox Sports 1 (See a pattern).  I don't have any premium channels.

     

     

    I tried installing this docker this morning and i'm get error messages, first line of messages below

     

    Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/urlxl/hdhomerundvr.xml, line: 7 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 379 Warning: 

     

    When I make changes, I do so to the live install .. because I have no idea what I am doing.

    I broke the install for about an hour yesterday.  Please delete the docker container and file and reinstall.

    A reinstall is working for me this morning.

    [Support] urlxl - HDHomeRun DVR [20210501beta1]

    in Docker Containers

    Posted

    I think the docker keeps trying to start HDHomerun DVR ... after it has already started.

    So, it should be running OK.  Mine has been up for a week without issue, that I know of.

    That said I think there are only like maybe 4 people running this, so if there was some edge case bug...

    That said, it looks like everything related to this is on the SiliconDust servers, so there isn't a lot to mess up.

    [Support] urlxl - HDHomeRun DVR [20210501beta1]

    in Docker Containers

    Posted · Edited by Yoshiofthewire

    Information

     

    Overview: HDHomeRun DVR

     

    To install, load the Docker Repository 

    https://github.com/Yoshiofthewire/docker-templates/tree/master/urlxl
     

     

    Requirements:

    1) You Need a Silicondust HDHomeRun Tuner

    2) You Need to be a Kickstarter backer or buy early access

     

    Install:

    1) Install the Windows or Mac HDHomeRun DVR to configure your Tuner and run setup to upgraded the firmware.

    2) Configure a new Docker Container from the Repository above.

    3) The container volume must be /hdhomerun

     

    Update:

    1) Install the Windows or Mac HDHomeRun DVR to configure your Tuner and run setup to upgrade the firmware.

    2) Check and apply updates to update the container.

     

    Notes:

    Current Record Engine Build:  20210501beta1

    Current Firmware Build:          20210501beta1

     

    Help building first container

    in Docker Containers

    Posted

    I am getting on of two errors

    root@evie:/usr/bin# /usr/bin/hdhomerun_record_x86 start
bash: /usr/bin/hdhomerun_record_x86: cannot execute binary file: Exec format error

     

    root@evie:/usr/bin# sudo /usr/bin/hdhomerun_record_x86 start
/usr/bin/hdhomerun_record_x86: 1: /usr/bin/hdhomerun_record_x86: Syntax error: "(" unexpected

     

    That said, the log isn't saying anything, because file moves are not working

    Help building first container

    in Docker Containers

    Posted

    So I am trying to build a container for hdhomerun dvr and I am completely stumped.

    I must be doing something wrong.

    I was using the limetech plex as a template.

    The install.sh is not running some basic commands.

    The hdhomerun dvr wont run itself.

     

    The container will create and I can install it, but it does nothing.

    Ideas?

    https://registry.hub.docker.com/u/yoshiofthewire/hdhomerundvr/

    [Solved] unRAID 6.0 RC3-4 Dynamix WebGUI OFTEN hangs (solved in RC5?)

    in Defect Reports [DEPRECATED]

    Posted

    Why are you unable to telnet?

     

    What's your NIC brand?

     

    Were you browsing from LAN or remote?

     

    Fast Ethernet or Gigabit?

     

    From wireless or wired client?

     

    unRaid fails to respond to telnet requests after the web interface goes down.

     

    Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

     

    Gigabit to Gigabit over Gigabit Switch

     

    I have also seen the Docker / KVM Network issue, but given that I could still access SMB shares, this was not that.

    [Solved] unRAID 6.0 RC3-4 Dynamix WebGUI OFTEN hangs (solved in RC5?)

    in Defect Reports [DEPRECATED]

    Posted

    I was trying to repair ad bad spot on my cache drive. 

    BTRFS was reporting an error on my Win7 DVR VM Img.

    I ran Scrub 3 times, one -r, a second time with the VMs running.

    The third time I turned off my Linux LAMP VM, Win7 DVR VM and Plex Docker Container.

    While switching between tabs to check different things the Web interface went down, but the log was still updating.

    The Web interface never came back and I am currently unable to telnet in to the box.

    The Log file still loads new data and I can access all shares.

     

    Jun 5 06:19:48 evie kernel: BTRFS: bdev /dev/sdg1 errs: wr 0, rd 0, flush 0, corrupt 827, gen 0
Jun 5 06:19:48 evie kernel: BTRFS: unable to fixup (regular) error at logical 156947853312 on dev /dev/sdg1
Jun 5 06:19:52 evie kernel: BTRFS: bdev /dev/sdg1 errs: wr 0, rd 0, flush 0, corrupt 828, gen 0
Jun 5 06:19:52 evie kernel: BTRFS: unable to fixup (regular) error at logical 164131721216 on dev /dev/sdg1
Jun 5 06:20:09 evie kernel: BTRFS: checksum error at logical 82398834688 on dev /dev/sdg1, sector 160935224, root 5, inode 3339977, offset 10918264832, length 4096, links 1 (path: VMs/mythbuntu.img)
Jun 5 06:20:09 evie kernel: BTRFS: bdev /dev/sdg1 errs: wr 0, rd 0, flush 0, corrupt 829, gen 0
Jun 5 06:20:09 evie kernel: BTRFS: unable to fixup (regular) error at logical 82398834688 on dev /dev/sdg1
Jun 5 06:20:17 evie kernel: BTRFS: bdev /dev/sdg1 errs: wr 0, rd 0, flush 0, corrupt 830, gen 0
Jun 5 06:20:17 evie kernel: BTRFS: unable to fixup (regular) error at logical 88062849024 on dev /dev/sdg1
Jun 5 06:20:18 evie kernel: BTRFS: checksum error at logical 88976338944 on dev /dev/sdg1, sector 173781912, root 5, inode 3339977, offset 13952806912, length 4096, links 1 (path: VMs/mythbuntu.img)
Jun 5 06:20:18 evie kernel: BTRFS: bdev /dev/sdg1 errs: wr 0, rd 0, flush 0, corrupt 831, gen 0
Jun 5 06:20:18 evie kernel: BTRFS: unable to fixup (regular) error at logical 88976338944 on dev /dev/sdg1
Jun 5 06:20:18 evie kernel: BTRFS: checksum error at logical 88976343040 on dev /dev/sdg1, sector 173781920, root 5, inode 3339977, offset 13952811008, length 4096, links 1 (path: VMs/mythbuntu.img)
Jun 5 06:20:18 evie kernel: BTRFS: bdev /dev/sdg1 errs: wr 0, rd 0, flush 0, corrupt 832, gen 0
Jun 5 06:20:18 evie kernel: BTRFS: unable to fixup (regular) error at logical 88976343040 on dev /dev/sdg1
Jun 5 06:20:18 evie kernel: BTRFS: checksum error at logical 89009487872 on dev /dev/sdg1, sector 173846656, root 5, inode 3339977, offset 26764943360, length 4096, links 1 (path: VMs/mythbuntu.img)
Jun 5 06:20:18 evie kernel: BTRFS: bdev /dev/sdg1 errs: wr 0, rd 0, flush 0, corrupt 833, gen 0
Jun 5 06:20:18 evie kernel: BTRFS: unable to fixup (regular) error at logical 89009487872 on dev /dev/sdg1

    After Down

    Jun 5 06:32:27 evie kernel: mdcmd (82): spindown 0

    More Complete Log: http://pastebin.com/ix8JMQy2

     

    Beta 14 Network stops working after 24 hours

    in Defect Reports [DEPRECATED]

    Posted

    So, good news, I stayed up for more than 24 hrs.

    Still testing....

    That said, I have issues, but those may not be unRaid related.

     

    My Build:

    Mobo: Gigabyte Technology Co., Ltd. - H61N-USB3

    CPU: Intel® Core™ i5-2500K CPU @ 3400

    Cache: 64 kB, 6144 kB

    Memory: 8192 MB (max. installable capacity 32 GB)

    Network:  eth0: 1000Mb/s - Full Duplex

                    eth1: 1000Mb/s - Full Duplex [Added after last reboot]

    Kernel: Linux 3.19.4-unRAID x86_64 96.0-beta15]

    Current Plugins: Only Built-In

     

    HDDs: 10TB, currently using 7.23TB across 4 Drives + Parity and SSD Cache Drive

    VMs:

    Docker: gfjardim/btsync:latest and needo/plex:latest

    VMs:

    4 vCPU 2GB Ram Win7 VM w/ Media Center and Addons

    1 vCPU 512MB Ram Turnkey Linux LAMP VM

     

    Network: Fios Quantum Gateway (POS)

    This thing stopped doing port forwarding and yesterday crashed.

    Only we can screw up the last 10', Verizon

    On Reboot the LAMP VM keeps loosing it's network config.

    The Win7 VM often feels like it is being pushed to it's MAX CPU wise.

     

    So it is possible that my Fears about Beta 15 were unfounded.

     

    As always, I am a bad test case.

     

    Beta 14 Network stops working after 24 hours

    in Defect Reports [DEPRECATED]

    Posted

    Yeah, I think I am going to let Beta 15 cook for a while and see what happens.

    That said it is acting just like 14 did, only now without any plugins, because everything is built in.

    It would be perfect if br0 didn't go down every day.

     

    Oh yes, I upgraded my Docker Containers and rebuilt the KVM VMs before br0 went down.

    And I know the system was up, I was able to gracefull shutdown from the power button.

    TVHeadEnd PVR Docker for use with Kodi

    in Docker Containers

    Posted

    I tried to create TVHdeadend with the following code

    docker run -d -–name=tvheadend -v /mnt/cache/docker:/config -v /mnt/user/RecordedTV:/recordings -v /etc/localtime:/etc/localtime:ro -p 9981:9981 -p 9982:9982 -p 5004:5004 tobbenb/tvheadend-unstable

    I can see the container running, but I am unable to connect to the web interface.

    The page never loads.  What did I do wrong?