Jump to content

Everend

Members
  • Posts

    131
  • Joined

  • Last visited

Posts posted by Everend

  1. Fresh reinstall did the trick.  (I think).  I removed all containers, removed docker, deleted everything (data/files/folders/users/shares) anything that could have been associated with the docker or any containers.  After reinstalling everything, mythtv seems to be working.  crashplan front end (via RDP) connected to the backend just after install. I shutdown & restarted the computer (unraid and all). now crashplan front end doesn't connect to the backend.  So making progress, but not complete yet.

  2. I wonder if it's a Docker issue instead.  The other container I installed is crashplan.  After initial installation it worked, but later (maybe after a restart) when I RDP into the crashplan port and try to connect the front end to the back end I get a message that it cannot connect to the backup engine.  So my current theory is that Docker isn't working right, instead of mapping to actual hard drives, it tried to install the containers into RAM, so when the computer restarts the container is hosed.

     

    thoughts?  Anyone... Anyone... Bueller?  Bueller?

  3. I just sent an email to a friend who told me about unRAID to see if he had any ideas, here is the meat of the email, in case I said something new in this email...

     

    So from within mythtv any time I config it to save something to /home/mythtv it should instead save it to /mnt/cache/mythtv.  I assume based on others examples that subfolders work this same way so /home/mythtv/recordings should map to /mnt/cache/mythtv/recordings.  /mnt/cache/ is how unRAID has mounted the 1.5TB cache drive. So if I SSH into unRAID as root, I see that drive's files/folders at that path.

      I can RDP into the mythtv docker container, it looks like a desktop (what I assume a linux desktop looks like). There is an icon which looks and acts like Windows Explorer, from this I can see the folders and files that mythtv is creating (including .mpg recordings)

      I can also connect Kodi to the mythtv backend and see live tv and recordings listed, playing as expected. 

      I can also connect to the backend via the mythtv web interface (which I think is the front end, but I'm not sure since I can't get it to play video, only look at the tv guide, schedule recordings, see status, that kind of thing. pretty much everything I would expect from a gui except the window to watch tv/recordings.  The mythweb has a status page which shows Total Space: 5,689 MB.  I would expect it to show much closer to 1.5TB (the size of the drive it should be saving to).

      The problem is that its not saving them to the drive I expect to find them and I'm afraid its actually saving to RAM but I really don't know enough about Linux to figure out he physical media associated with the file structure I see when I log into SSH using root/pw

      Earlier I used RDP logged into mythtv user to create a folder named 'testing', then from SSH w/root I used 'find -name testing' to find that folder here... "./var/lib/docker/btrfs/subvolumes/e3eb4128aafcf58dc7aecdbdebab205928ef824f3f600d180dc158ae9d96640f/"

      A bit later that folder "e3eb..." disappeared.  (I may have reinstalled the container, not sure).  Now 'find' doesn't find the mythtv location anymore. I recorded a show and see via RDP it crated a file  "1042_20150914164300.mpg.png" So I tried doing the find again but it did not find it.  If I run the find from /var or any subfolder it returns nothing. If I run find from root I get this message.

    root@Tower:/#  find -name 1042_20150914164300.mpg.png

    find: WARNING: Hard link count is wrong for `./proc/fs' (saw only st_nlink=10 but we already saw 8 subdirectories): this may be a bug in your file system driver.  Automatically turning on find's -noleaf option.  Earlier results may have failed to include directories that should have been searched.

    find: `./proc/20197': No such file or directory

     

    So does any of this ring any bells for you?

     

    unRAID is currently running a health check on one of the disks that will take several more hours. When that finishes I'll restart the system, maybe that will help :)

  4. I finally found the correlation between the folder structure I see while logged into mythtv through rdp & SSH into tower as root. 

     

    When I ssh into TOWER using the root user I find the mythtv files here...

    ./var/lib/docker/btrfs/subvolumes/e3eb4128aafcf58dc7aecdbdebab205928ef824f3f600d180dc158ae9d96640f/

     

    in the RDP window I created a new folder named testing, that folder appeared in the above directory in the SSH window.

     

    So where is the problem, is it the docker/installs fault for locating the mythtv files here instead of the mapping I attempted while installing the plugin or are the files supposed to be represented here but then linked/pointer to the cache drive and the pointer isn't working right?

     

    This install I changed the volume mappings to

      /home/mythtv -> /mnt/cache/mythtv

      /db -> /mnt/cache/mythtv/data

      /var/lib/mythtv -> /mnt/cache/mythtv

     

     

  5. While RDP into the box with mythtv user/password as described in the instructions here I see a gui directory explorer. The Volume Mappings are plainly viewed in the file system structure shown here. Also from within RDP I opened a xterm window, using cd & ls I can see the same folders/locations.

      From the unRAID console I logged into Tower as root.  I've explored the file system available there and have been unable to find a tie of any kind between the files/folders I see logged in as the mythtv xterm & root from the unRAID console.  I expected to see a user home directory for mythtv while exploring as root. I figured once I figured out where mythtv is saving everything, I'd have a better idea how to point it to the right place.

    please help!

    • I'm trying to get Mythtv setup on unraid, I've searched forums, watched videos, read more posts than I can remember and I still don't think its right, please help. I setup unRAID last weekend (replacing Win7 machine with NextPVR). I've spent about 10hrs now trying to get MythTV setup.
       
      Unraid 6.1.0  w/ Parity + 4 Disks
      Unassigned Devices v2015.09.07a
        - currently pre-zeroing an upgrade for the array disk4
        - 400GB IDE drive xfs formated - I'd like to use for mythtv
        - two DVD drives
      Mythtv Docker using sparklyballs instructions
       
      I read that I can have recordings & livetv use an Unassigned Device so the parity drive is not also being written to when recording. This sounded like a good idea to me because I don't see the need to parity protect the livetv buffer or new recordings. I'd rather use unprotected storage for these things, then move recordings to a protected drive if I decide I want to keep it. 90% of the time, I delete after watching.
        So I installed Unassigned Devices v2015.09.07a and mounted the IDE drive /mnt/disks/ST3400632A_5NF0NRE5  I renamed it ST340 at one point, then started over and forgot to rename it before mounting it so this pass through the installation/setup I just left the name Unassigned Devices gave it.
        Followed sparklyballs (and others posted in this string) to install the MythTV container.  Please verify the volume mappings I've used make sense...
      in the Volume Mappings section I see the header lables; "Container volume:  Host path:  Access: "  The next line is two blank boxes under Container volume & Host path, then Read/Write was preselected under the Access column.  The 2-4 rows of Container volume: is prefilled with..
      /home/mythtv -> /mnt/disks/ST3400632A_5NF0NRE5/mythtv
      /db - >/mnt/disks/ST3400632A_5NF0NRE5/mythtv/data
      /var/lib/mythtv -> /mnt/disks/ST3400632A_5NF0NRE5/mythtv
       
      When save I received 'success' messages and see "mythtv" folder appear on the mounted, unassigned disk.  Then from Win10 RDP into mythtv (that took quite a while to figure out how to do since I didn't know anything about rdp or guacamole), and followed through the backend setup. That went pretty much as sparklyballs described in the video starting this thread.
       
      The WebUI keeps giving me errors on various pages but I can see the TVGuide and select a program to record. I connected KODI (running on another machine) to MythTV and Live TV worked one time (ie I could tune into a station and see video).
       
      PROBLEM - I don't think MythTV is actually using ST3400632A_5NF0NRE5 drive.
      • The mounted, unassigned drive shows up in Win10 explorer along side all the other disks in the unRAID computer (array drive, flash drive, shares) but there are no files.
      • MythTV WebUI -> Backend Status page shows Total Space: 5,689 MB - Space Used: 2,884 MB - Space Free: 2,804 MB

    [*]From the unRAID console I've logged in as root, using ls and cd (about the only linux commands I know) I've found the ST3400632A_5NF0NRE5 drive and only see the same mythtv folder and the subfolders I created using Win10. No data of any kind.

     

     

    Other odd thing is the MythTV log file I can open through the unRaid Dashboard -> Apps -> MythTV -> Logs

    icon for kill switch is set
    default config file(s) appear to be in place
    .Xauthority file appears to in place
    kill switch is set
    setup desktop icon is set
    mythtv folders appear to be set
    Database(s) exists.
    Starting MariaDB...
    Checking whether database(s) are ready
    waiting.....
    waiting.....
    waiting.....
    waiting.....

    The log keeps repeating this sequence.

×
×
  • Create New...