Jump to content

hgeorges

Members
  • Posts

    110
  • Joined

  • Last visited

Posts posted by hgeorges

  1. Hi,

    I have tvheadend installed on Unraid 6.3.5 -

    M/B: Supermicro - X10SLL-F
    CPU: Intel® Xeon® CPU E3-1265L v3 @ 2.50GHz
    HVM: Enabled
    IOMMU: Enabled
    Cache: 256 kB, 1024 kB, 8192 kB
    Memory: 16 GB (max. installable capacity 32 GB)
    Network: eth0: 1000 Mb/s, full duplex, mtu 1500 
    Kernel: Linux 4.9.30-unRAID x86_64
     
    Tvheadend is attached to two hdhomerun  network devices (first generation which produce mpeg-2 output) connected to an antenna for OTA content.

    I'm not using this much - but tried a few things and some work some don't (at least for me). I'd like to know find out if this is something having to do with my setup (perhaps some error), or more general, due to, perhaps, running as a docker app etc.

     

    So:

    I can only watch/stream to my browser through webtv-vorbis codec. The other codecs do not produce any output. Sometimes I only get audio, and no video. For HD content would be great to be able to recode on the fly the mpeg stream - which otherwise doesn't run too well over wifi. I have 

     

    I can only record program through default profile(pass mpeg) - which generates huge files. I can convert them afterwards, but if conversion on the fly/during recording, is possible, I would try to use it.

    Any advice is appreciated! Thank you

    hg

     

  2. Hi,

    any update on this particular problem. I'm sort-of in "limbo" - not sure how to best resolve the issue.

    I started this procedure hoping I can undelete some files (pictures).

    But it turns out that there are bigger problems lurking in the background.

    fsck is not working reliably

    fsck is reporting strange filesystem problems, which a cursory monthly scan of parity doesn't reveal

    fsck is also modifying the image to the point that it is no longer mountable. (it was before running fsck). Probably crashing in the middle of the procedure did that.

     

    Here is the output of a new run:

    root@Tower:~# reiserfsck --rebuild-tree --scan-whole-partition /mnt/disk9/hd5.dd

    reiserfsck 3.6.25

    *************************************************************
    ** Do not  run  the  program  with  --rebuild-tree  unless **
    ** something is broken and MAKE A BACKUP  before using it. **
    ** If you have bad sectors on a drive  it is usually a bad **
    ** idea to continue using it. Then you probably should get **
    ** a working hard drive, copy the file system from the bad **
    ** drive  to the good one -- dd_rescue is  a good tool for **
    ** that -- and only then run this program.                 **
    *************************************************************

    Will rebuild the filesystem (/mnt/disk9/hd5.dd) tree
    Will put log info to 'stdout'

    Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
    Replaying journal: Done.
    Reiserfs journal '/mnt/disk9/hd5.dd' in blocks [18..8211]: 0 transactions replayed
    ###########
    reiserfsck --rebuild-tree started at Sun Mar 26 07:57:15 2017
    ###########

    Pass 0:
    ####### Pass 0 #######
    The whole partition (488378638 blocks) is to be scanned
    Skipping 23115 blocks (super block, journal, bitmaps) 488355523 blocks will be read
    0%....20%....40%..block 245253713: The number of items (29451) is incorrect, should be (1) - corrected
    block 245253713: The free space (29797) is incorrect, should be (3536) - corrected
    pass0: vpf-10110: block 245253713, item (0): Unknown item type found [33554688 184551936 0x4000000 ??? (15)] - deleted
    Segmentation fault
    root@Tower:~# mount -o loop /mnt/disk9/hd5.dd /mnt/recovery                     mount: /dev/loop1: can't read superblock
    root@Tower:~# ls  /mnt/disk9/hd5.dd
    /mnt/disk9/hd5.dd
    root@Tower:~#

     

    What is the verdict?

    I could rollback to one of the prior versions, but I would have to go through successive tries to find out which one has a reliable reiserfsck.

     

  3. Here are another two runs, on the dd image pulled from a 2TB HDD:

    root@Tower:~# dd if=/dev/sdg1 of=/mnt/hdd5-reiserfs.dd bs=4096 conv=noerror
    488378638+0 records in
    488378638+0 records out
    2000398901248 bytes (2.0 TB, 1.8 TiB) copied, 23448.1 s, 85.3 MB/s

    root@Tower:~# reiserfsck --rebuild-tree --scan-whole-partition /mnt/hdd5-reiserfs.dd
    reiserfsck 3.6.25

    *************************************************************
    ** Do not  run  the  program  with  --rebuild-tree  unless **
    ** something is broken and MAKE A BACKUP  before using it. **
    ** If you have bad sectors on a drive  it is usually a bad **
    ** idea to continue using it. Then you probably should get **
    ** a working hard drive, copy the file system from the bad **
    ** drive  to the good one -- dd_rescue is  a good tool for **
    ** that -- and only then run this program.                 **
    *************************************************************

    Will rebuild the filesystem (/mnt/hdd5-reiserfs.dd) tree
    Will put log info to 'stdout'

    Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
    Replaying journal: Done.
    Reiserfs journal '/mnt/hdd5-reiserfs.dd' in blocks [18..8211]: 0 transactions replayed
    ###########
    reiserfsck --rebuild-tree started at Mon Mar 20 20:12:55 2017
    ###########

    Pass 0:
    ####### Pass 0 #######
    The whole partition (488378638 blocks) is to be scanned
    Skipping 23115 blocks (super block, journal, bitmaps) 488355523 blocks will be read
    0%....20%....40%..block 245253713: The number of items (29451) is incorrect, should be (1) - corrected
    block 245253713: The free space (29797) is incorrect, should be (3536) - corrected
    pass0: vpf-10110: block 245253713, item (0): Unknown item type found [33554688 184551936 0x4000000 ??? (15)] - deleted
    Segmentation fault
    root@Tower:~#

    And trying again:

    root@Tower:/mnt# reiserfsck --rebuild-tree --scan-whole-partition hdd5-reiserfs.dd
    reiserfsck 3.6.25

    *************************************************************
    ** Do not  run  the  program  with  --rebuild-tree  unless **
    ** something is broken and MAKE A BACKUP  before using it. **
    ** If you have bad sectors on a drive  it is usually a bad **
    ** idea to continue using it. Then you probably should get **
    ** a working hard drive, copy the file system from the bad **
    ** drive  to the good one -- dd_rescue is  a good tool for **
    ** that -- and only then run this program.                 **
    *************************************************************

    Will rebuild the filesystem (hdd5-reiserfs.dd) tree
    Will put log info to 'stdout'

    Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
    Replaying journal: Done.
    Reiserfs journal 'hdd5-reiserfs.dd' in blocks [18..8211]: 0 transactions replayed
    ###########
    reiserfsck --rebuild-tree started at Mon Mar 20 22:31:37 2017
    ###########

    Pass 0:
    ####### Pass 0 #######
    The whole partition (488378638 blocks) is to be scanned
    Skipping 23115 blocks (super block, journal, bitmaps) 488355523 blocks will be read
    0%....20%....40%..block 245253713: The number of items (29451) is incorrect, should be (1) - corrected
    block 245253713: The free space (29797) is incorrect, should be (3536) - corrected
    pass0: vpf-10110: block 245253713, item (0): Unknown item type found [33554688 184551936 0x4000000 ??? (15)] - deleted
    Segmentation fault
    root@Tower:/mnt#

     

  4. Hello;

    Thanks for making this docker available. I decided to experiment with it; simplicity is definitely a huge advantage over all the other media servers out there...

    Can you check if you have the same error message in your log and if not, suggest why is happening to me, and a possible solution:

    [2017/03/12 16:18:28] utils.c:279: warn: make_dir: cannot create directory '/var/run/minidlna'
    [2017/03/12 16:18:28] minidlna.c:400: error: Unable to create pidfile directory: /var/run/minidlna/minidlna.pid

     

    Further to that - I've got quite a few warnings about some issues found with my music. (corrupted oggs, names too long, not valid header, etc.

    How do you suggest to clean these up?

    do you recommend a tool whichcan check for corruptions, and other issues (like the one mentioned above)?

    Thanks

    hg

  5. Hi,

     

    Background: 

    I upgraded yesterday to the new 6.3.2 version (and upgraded to a new motherboard - x10SLL-F-O - in the same time) apparently w/o issues (Thank you!).

    However, after a short time I started receiving plugin errors (missing files, and an endless loop from a tenacious plugin wanting to send statistics from my system).

    Reading also in your note:

    Limetech quote:

    Plugin Authors: as posted earlier, your plugin may not function properly depending how how POST requests are handled, see:

    http://lime-technology.com/forum/index.php?topic=55986.0

     

    Plugin Users: please post issues you find in the appropriate Plugin Support topic.

     

    And to reiterate: true plugins (not Docker containers) run as the

    root

    user and have full access to everything on your server: Install 3rd party plugins at your own risk.

    End Limetech quote.

     

    I have decided to remove all the plugins from my server - as I don't have time to hunt for compatibility issues and resolve strange behaviors. I'm running now the barebone system, and want to use docker or VMs for additional functionality.

     

    Now here is my question: 

    regarding plugins - I'm assuming there are no limetech endorsed and versions controlled plugins? Is that right?

     

    Among those I had installed were a few which made sense to have close by  (all were strictly tools, one to create and verify checksums, another adding an expanded tool set, etc) - perhaps you can create limetech optional add-on packages which make sense to run as root, and are safe to run (version controlled).

    Please comment. Thanks again.

  6. Hello,

    Thank you for sharing this application with the unraid community.

    I recently added your plugin to my unraid server. I'm reporting a couple of issues, and I have a couple of questions.

    1) false positives

    Ignored Errors & Warnings Suggested Fix

    Docker Application tvheadend is currently set up to run in host mode The template for this application specifies that the application should run in bridge mode.

    For your reference this link: https://hub.docker.com/r/linuxserver/tvheadend/

    "Host vs. Bridge

    If you use IPTV, SAT>IP or HDHomeRun, you need to create the container with --net=host and remove the -p flags. This is because of a limitation in docker and multicast."

    ---------------------

    Docker Application tvheadend, Container Port 9981 not found or changed on installed application When changing ports on a docker container, you should only ever modify the HOST port, as the application in question will expect the container port to remain the same as what the template author dictated. Fix this here:

    Application Support Thread

    Docker Application tvheadend, Container Port 9982 not found or changed on installed application When changing ports on a docker container, you should only ever modify the HOST port, as the application in question will expect the container port to remain the same as what the template author dictated. Fix this here:

    Application

    -------------------

    Both lines are unjustified. I reinstalled tvheadend several times, and from a couple of sources, on this site. But the ports are the same.  And I have tvheadend installed, but stopped. It has not been running for weeks.

     

    My questions :

    1) is the program checking for a change of state in the previously identified state, and should that have happened, are the warnings/errors removed?

    If that is not the program behavior, is there any possibility to add a remove/hide option, so that messages which are not necessary should not be displayed.

     

    2) I realize that is a matter of personal choice (I read your answer in the beginning of the thread) - but there is a semantic difference between an error and a warning. Seeing error messages I have two conscious choices to make, to go and check them each time, since an error must be treated with urgency, or, knowing that an error might not be exactly an error, I can choose to ignore it. (Remember Unraid is sending email notifications for various reasons, errors being one of them, and FCP is not the solely application generating notifications. There are other subsystems on unraid which can generate real errors). Desensitizing me to errors is the undesired effect of sending error messages when there are none.  The same notion with "Crying wolf" if you want...

     

    That's it. Thanks for reviewing my reply.

    hg

  7. Aha! got it now! :) Thanks so much!

     

    I didn't realized that the nerd pack was downloaded but not installed. I just turned on all the tools in the pack and inotify among them.

    Went back to checksum added one more directory in the configuration, and this time it didn't complain about inotifywait anymore. It just asked me to restart the monitor, and I did, and it appears that now it started: Monitor Status: Running Checksum Calculations Idle Verifier Status: Idle

    Now one last question: do I need to start a manual checksum first, or will it do it alone? - not finding any checksum (this is the first time it is running).

     

    Much appreciated.

     

  8. That was fast! :)

    Thank you for your reply. Essentially that's what I did. But nothing happened with inotifywait config file.

    Again - steps I've taken:

    - already had the NerdPak installed, long time ago. It also was up-to-date.

    - today I just installed checksum suite. It complained about inotifywait not running right after installation.

    - I thought NerdPak doesn't have inotify tools, and added the plugin again, but nothing happened, since it was already installed.  I could perhaps have uninstalled it, and reinstalled.

    - then I went to checsum (Create/Monitor settings) and started adding directories in the setup, such as /dir1 .../mnt/user/pictures; /dir2 .... /mnt/user/Education etc.

    - At the top of the page however I continue to have "Monitor Status: inotifywait NOT installed"

    - In docker dashboard, Inotify-command is not running. If I start it manually, it complains that the conf file I created is missing the command directive (which is true, because I commented it out when I edited manually the conf file). Inotify otherwise did not pick -up any config from checksum.

     

    Thanks again for your help.

    hg

     

     

     

  9. Hello;

    I know this tool is not developed anymore /and all discussions dried out about 3-4 months ago - but those still using it, perhaps can assist with a setup question.

     

    I just installed  checksum suite, and it complained of inotifywait not installed.

     

    After going back and forth several times (because I already had Nerdpack installed), i discovered that Inotify needed to be set to monitor directories. I configured it, but then none of those directories I've set in the confguration menu, made it into the config file. That stayed sample.conf, and if I deleted it, it got recreated again upon starting inotify docker.

    I then edited renamed sample.conf to inotify.conf, and entered all the directories. Since the default command directive  - present in the sample - didn't make sense, I commented it out.

    I restarted inotify, but it died right away, since it was missing the command directive.

    I figured the command has to point to checksum suite somehow, but it is not obvious.

    Anyone caring to point me in the right direction?

    Thank you!

  10. Thanks so much, Sparkly, for the quick reply and ... sorry for the trouble...

     

    The update didn't pick the new version up unfortunately, so I decided to delete container and image and re-download from the repository.

    Strange enough, even if your update is there in the template (I can see it), the version downloaded is still 5.0.1:

    From the log:

    ...

    INFO 16:28:42.306 [main] Starting Universal Media Server 5.0.1

     

    As for the web plug-gin- I found it somewhere. I have to search it again (I'm not sure it is in fact web management interface), and try it.

     

    Thanks again.

    hg

  11. Hello Sparklyballs;

     

    You pointed me  a while back to your version of dockerized UMS... and  I'd like to try your ums template - can you please update it to point to the latest version (currently 5.1.4 http://sourceforge.net/projects/unimediaserver/files/Official%20Releases/Linux/) of the sw? https://registry.hub.docker.com/u/sparklyballs/universal-media-server/dockerfile/

     

    As a matter of practicality, if you don't mind me suggesting this for easy maintenance ... you may want to  declare a version variable at the top of your  template, and use that, instead of hard coding the version further down in the code section.

     

    I'd really want to try adding to it ALSO the web plug-in, as I'm not sure how to manage it otherwise.

    Thank you !

    hg

     

  12. Hello;

    I'm a long time user of unraid and new to the latest features, including docker.

    So first I want to thank you very much for creating the user guide, that's quite helpful.

     

    In my particular situation, I tried a few things so far, and I'm going back and forth on my experiments, installing and uninstalling docker containers. And doing that I noticed that the cleanup part is not really working too well, as I still find things left behind after I deliberately chose to delete images and containers. Would be helpful if the guide can be enhanced to cover the entire life-cycle of the docker environment:

    - installing and uninstalling docker

    - installing and uninstalling applications in docker

    - different upgrade scenarios of  the environment

    etc

     

    Thank you

    hg

  13. Hi;

    I'm testing serviio, and from an end user perspective i'd like to simplify access to it. Having to connect to http://tower:23424/mediabrowser/ is not too user friendly, but I don't want to change the whole unraid setup...  I'm thinking that I could use new host name and a proxy forward on the lan. Is there a proxy available in unraid Docker library, or are there other suggestions to accomplish the same result?

     

    Thank you

    hg

  14. Hello everyone;

    I'm making some progress using some docker images from the forum. I'm quite thrilled to be able to add additional functionality to my unraid, which I ran for years just bare-bones. I'm in the early stage with serviio - loaded from Sparklyballs repository (Thank you, Sparklyballs!)- it is working, and as the license goes, I can test its pro features in the first two weeks of the installation. I'd like to check more of its features, including the plugins, before it defaults to the trimmed down version. Plugings reference: http://wiki.serviio.org/doku.php?id=servio_plugins

    Anyone using any such plugins on the docker, and possibly can share how to install them?

     

    Thank you  for any suggestions!

    hg

  15. That's clearly a possibility  :) I didn't think about.

     

    Thank you for sharing your experience.

    UMS features page (and comparison with other such media servers) is very appealing.

     

    I'll probably have to look into plex  again, but I didn't like the idea that I have to create accounts elsewhere, to enable whatever features I want or need.

    I want something which is only running on my lan/server, and all its features available within those boundaries - without other dependencies, aside from the usual upgrades pulled periodically from the internet.

     

    hg

     

     

  16. Hello Docker Gurus;

    I'm trying to add the following image from here https://github.com/mbentley/docker-ums

    And i'm hitting an error, which I'm not sure how to troubleshoot. Any possibility that someone may have already used this and knows what is missing?

     

    This is a snapshot of the log - pretty cryptic for me...

     

    Thank you for your help!

    hg

     

    Timestamp: 2015-06-24 21:40:20.028794643 -0400 EDT

    Code: System error

     

    Message: not a directory

     

    Frames:

    ---

    0: setupRootfs

    Package: github.com/docker/libcontainer

    File: rootfs_linux.go@29

    ---

    1: Init

    Package: github.com/docker/libcontainer.(*linuxStandardInit)

    File: standard_init_linux.go@52

    ---

    2: StartInitialization

    Package: github.com/docker/libcontainer.(*LinuxFactory)

    File: factory_linux.go@223

    ---

    3: initializer

    Package: github.com/docker/docker/daemon/execdriver/native

    File: init.go@35

    ---

    4: Init

    Package: github.com/docker/docker/pkg/reexec

    File: reexec.go@26

    ---

    5: main

    Package: main

    File: docker.go@29

    ---

    6: main

    Package: runtime

    File: proc.go@63

    ---

    7: goexit

    Package: runtime

    File: asm_amd64.s@2232

    Timestamp: 2015-06-25 13:29:52.826818529 -0400 EDT

    Code: System error

     

    Message: not a directory

     

    Frames:

    ---

    0: setupRootfs

    Package: github.com/docker/libcontainer

    File: rootfs_linux.go@29

    ---

    1: Init

    Package: github.com/docker/libcontainer.(*linuxStandardInit)

    File: standard_init_linux.go@52

    ---

    2: StartInitialization

    Package: github.com/docker/libcontainer.(*LinuxFactory)

    File: factory_linux.go@223

    ---

    3: initializer

    Package: github.com/docker/docker/daemon/execdriver/native

    File: init.go@35

    ---

    4: Init

    Package: github.com/docker/docker/pkg/reexec

    File: reexec.go@26

    ---

    5: main

    Package: main

    File: docker.go@29

    ---

    6: main

    Package: runtime

    File: proc.go@63

    ---

    7: goexit

    Package: runtime

    File: asm_amd64.s@2232

     

     

  17. Hello folks.

    I've just started testing v6rc3.

    I'm interested in tvheaden, etc. , as I have two hdhomerun devices on my LAN for ota reception. 

     

    I will/need to read your instructions carefully - but just to be clear from the start, is this requiring the change of unraid core system (bzroot etc.)?

    I really prefer to load this in a vm, and not mess up with Unraid main source.

     

    Thank you.

    hg

×
×
  • Create New...