Welcome to LIGHT Forum.......The place to be.......Enjoy your stay and have fun ....

Announcement

Collapse
No announcement yet.

Mounting Wizard v1.3 by Daniel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mounting Wizard v1.3 by Daniel

    Mounting Wizard v1.3 by Daniel

    This new plugin will help the users to mount nfs and samba servers in the AZBox. It auto-starts the mount points when the AZBox boots, contains some options to mount nfs, and its posible to mount samba with user and password.

    If you find bugs, or you have any suggestion contact me.

    To install just extract the files on the attachment "MW.zip" and copy those two files to some compatible pen or copy them to the /tmp folder by ftp and install.

    -----------------------------------------
    v1.1
    New version with a bug fixed.
    - user and password are now possible to modify on samba.

    -----------------------------------------
    v1.2
    New version with capability to add folders inside local system folders.

    -----------------------------------------
    v1.3
    New version with improvements and bugs fixed.
    - few modifications on the interface.
    - internal code improvements.
    - bug that appeared when initializing nfs or samba with folders added to system folders.

    © Dan

    http://light-files.site50.net/php_up...boxHD/Plugins&

  • #2
    Synology DS210j NAS problems with AZbox HD...

    Errrmmmm.... no go....

    I set up the Synology DS210j properly, it is working GENERALLY but - not with AZbox HD specifically... Namely, I can access it from my PC but not from AZbox HD, Mounting Wizard [v. 1.3 by Daniel] or not [actually, it got confused at some point and the stuff I put into it got changed...]!

    Interestingly, I can get in with AZbox HD's FTP Client! But I can not play anything from it, just move files [to the DOM, I think, because it froze quickly] etc.

    But that won't do... When I try via Movies -> Network, for instance, it doesn't ask me for username/password and when it gets in the NAS - it can't see anything...

    I activated the NFS server, as well as Windows one, created shared folders, given permissions [NFS one specifically, too!], added exceptions in the firewall, in the router and so on and so forth...

    Nada! I am lost for words...

    Does anyone know EXACTLY how to mount NFS server's shared folders, put in the obviously necessary username/password and be able to stream to AZ HD from it, please?

    But wait: my Windows7 has username and password but AZbox HD isn't asking for them in order to get in, and it still is able to go into Win7 shared folders and play from them! Weird or what?

    If it is possible, after all, to get into the NAS and play from it onto AZ HD: would it be possible to record onto a dedicated TV Record folder in the NAS, as opposed to a built-in HDD or a USB attached HDD???

    Thanx in advance!
    Last edited by gorski; 18-08-2010, 17:06.

    Comment


    • #3
      I was messing and messing with it until...

      Heh, just discovered that in Win Server I haven't put the IP address and now CIFS works... [it seems...??]

      But I can't tell which one actually works... I deleted the Mounting Wizard having tried it, as I stated earlier, which meddling left a few files behind and maybe they are working? Here is StartUpNFS from DISK2/etc:

      Code:
      192.168.x.x:/volume1/video /DATA/movie 1 0 1
       192.168.x.x:/volume1//music /DATA/music 1 0 1
       192.168.x.x:/volume1/photo /DATA/picture 1 0 1
       192.168.x.x:/volume1/TV Record 1 0 1
       /DATA/recordfile 0 0 0 0
      These folders can't be seen via "Network" but by going directly into Movies, as it's being mounted right there!

      It doesn't ask for username/password, even though I have them for the NAS.

      Still, VOB is going great, MKV, too. Must test more...

      Generally: IT'S WORKING!!!!

      From my laptop [WLAN to the router and then LAN/cable] it wasn't as good. I had many more problems, then going straight via the LAN cables from the NAS! On top of that, lately I have mostly streamed from the USB HDD attached to my laptop. That made it even more difficult!

      Anyways, as Zeini and co. said in their Wiki article: I can't record over the net to NAS, though, it seems... Here is a little online translation from German to English of the article:

      The Network File System - NFS abbreviated (also Network File Service) - a system developed by Sun Microsystems protocol that allows access to files over a network. Process, the files are not transferred as in FTP, but the user can access files that reside on a remote computer, access, as if they were stored on their local hard drive. If NFS is UNIX network protocol.

      The equivalent to NFS on Windows and OS / 2 environment is Server Message Block (SMB). While authenticated at the SMB user, authenticates the more popular the NFS V3 client machine, only NFS V4 allows user authentication.

      NFS services are also available on Microsoft Windows servers, UNIX workstations, which may have access to their files. On Windows, a maximum possible NFS V3. However, it is mostly used in mixed environments with SMB Samba on Unixseite.

      These instructions cover manual integration of network drives using NFS mounts.

      Requirements:
      - Telnet connection to your AZ-Box. How does this read here.
      - NFS sharing a folder was created on a PC or NAS. On Windows, NFS shares can be realized only after installation of an NFS server. is used when a Windows PC without a NFS server, only the application of SMB mounts possible.

      An NFS mount command is as follows.

      Code:
      mount -t nfs -o nolock,rsize=8192,wsize=8192 "IP-Adresse des  PC":/Freigabename Mountziel
      {Btw, Zeini explained: "NFS-Freigabe means NFS-Sharingname of the PC or NAS - in this example from the device with IP 192.168.0.2"}

      In our example, the mount command looks like this:

      Code:
      mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.0.2:/Movies  /DATA/movie
      By entering this command via Telnet, the NFS share with the Movies folder / DATA movie / connected to the AZ box. The NFS share movies has been set up on the PC or the NAS with the IP address 192.168.0.2 before.

      After successfully entering the Mount command via Telnet, are in the file manager on the AZ box mounted the files in the folder in the film, visible.

      Code:
      192.168.0.2:/Movies = NFS-Freigabe
      , which you have established, for example, on your PC or NAS. 192.168.0.2 with the IP of the PC or NAS is in the network and Movies is the name of the share. The two information must be adapted to each of these events.

      /DATA/movie = the destination on the AZBOX. In the case of "film".

      Any number of NFS mounts are performed. Each mount command must however have a different target on the AZ-BOX. Multiple NFS mounts the directory / DATA / movie are not allowed. When multiple folders to be mounted with movies, there is the possibility subfolder in the / DATA / movie to create and to mount it.

      You can create a subfolder, with, for example the name of movies in which you type the following commands:

      Code:
      mkdir /DATA/movie/Movies
      This folder must be only once did he create will be retained after a restart of the Az-Box.

      The mount command would look like this:

      Code:
      mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.0.2:/Movies  /DATA/movie/Movies
      Apart from "film" there's "music" and "Photos".
      These folders can be mounted as follows:
      Code:
      Film = /DATA/movie 
       Musik = /DATA/music 
       Foto = /DATA/picture
      It is not possible to mount a recording of the folder directly record to a network drive. How you can still take up to a network drive in post recording will be introduced to network drive.

      However, the so prepared NFS mounts you can now set up permanent NFS-mounts via a startup script.
      So, simply substitute, as to whatever you have named your folders, plus your correct NAS IP address and...

      One more thing: I was trying the described manner of getting it started, so I was also using the PuTTy [Telnet] set of commands, as described.... Maybe that did it?

      Dunno - must investigate to be able to do it again, when necessary...

      Thanx a bunch!!!!!!!!!!!!!

      Comment


      • #4
        It was the NFS procedure with Telnet [PuTTy] that did it in my case, thanx to Zeini & co.!!! Here it is again:

        Code:
        mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.x.x:/volume1/video /DATA/movie
        
        mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.x.x:/volume1//music /DATA/music
        
        mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.x.x:/volume1/photo /DATA/picture
        
        mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.x.x:/volume1/TV Record /DATA/recordfile
        This command mounts the folder into HOME -> Movie -> Movie as /DATA/movie and similarly will do with music or photos, of course...

        But now I have to figure out how to do it automatically, so I don't have to do it every time I want to watch something... or restart/reboot AZbox HD...

        Any takers for a statup NFS script, like the CIFS one here attached, please?

        Thanx!!!
        Attached Files

        Comment


        • #5
          It works 'till you reboot AZ HD!

          Maybe this might help? Will try it once the good lady is in bed...

          This howto describes how to mount a NFS share with a plugin script.
          It mounts the NFS shares to /DATA/movies /DATA/music etc
          So you can select them via the menu of the AZbox.

          Note: 192.168.x.xx = Ip of your NAS or server

          Make a new folder in the OpenXCAS plugin directory on the Azbox, using for instance PuTTy:

          Code:
          cd /EMU/OpenXCAS
          mkdir mount
          cd mount
          create a file in this folder with the name mount.sh with the following content:

          Code:
          #!/bin/sh
          mount -t nfs 192.168.x.xx:/dir/to_your/video /DATA/movie -o nolock,soft,rsize=8192,wsize=8192
          mount -t nfs 192.168.x.xx:/dir/to_your/music /DATA/music
          Create a file called openxcas.conf in the same folder:

          Code:
          [module]
          name = mount
          daemon = mount.sh
          version = 1.0
          then chmod 755 * in the same folder to give the files execute rights.

          Go up one folder into /EMU/OpenXCAS and add a line in the module.seq file called mount (a # in front of a line means the plugin is deactivated).

          Then you can select the plugin in the OpenXCAS menu called mount and start it with the OK or yellow button.

          You should see the new files in the Movie and Music menu entries.

          if you already have a HDD this might conflict with existing /DATA mounts and a harddisk that you might have installed, it will not corrupt anything it just wont work
          Thanks to emmanneil AND LilleMama

          Here are the ABC instructions for Linux NFS stuff...

          Code:
          https://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/s1-nfs-mount.html
          Code:
          http://docs.sun.com/app/docs/doc/817-5093/fsmount-69423?a=view
          Code:
          http://nfs.sourceforge.net/nfs-howto/
          
          http://nfs.sourceforge.net/nfs-howto/ar01s04.html
          4.3. Mount Options
          4.3.1. Soft versus Hard Mounting

          There are some options you should consider adding at once. They govern the way the NFS client handles a server crash or network outage. One of the cool things about NFS is that it can handle this gracefully. If you set up the clients right. There are two distinct failure modes:

          soft

          If a file request fails, the NFS client will report an error to the process on the client machine requesting the file access. Some programs can handle this with composure, most won't. We do not recommend using this setting; it is a recipe for corrupted files and lost data. You should especially not use this for mail disks --- if you value your mail, that is.
          hard

          The program accessing a file on a NFS mounted file system will hang when the server crashes. The process cannot be interrupted or killed (except by a "sure kill") unless you also specify intr. When the NFS server is back online the program will continue undisturbed from where it was. We recommend using hard,intr on all NFS mounted file systems.

          Picking up from the previous example, the fstab would now look like:

          # device mountpoint fs-type options dump fsckord
          ...
          master.foo.com:/home /mnt/home nfs rw,hard,intr 0 0
          ...

          The rsize and wsize mount options specify the size of the chunks of data that the client and server pass back and forth to each other.

          The defaults may be too big or to small; there is no size that works well on all or most setups. On the one hand, some combinations of Linux kernels and network cards (largely on older machines) cannot handle blocks that large. On the other hand, if they can handle larger blocks, a bigger size might be faster.

          Getting the block size right is an important factor in performance and is a must if you are planning to use the NFS server in a production environment. See Section 5, “Optimizing NFS Performance” for details.
          Code:
          http://www.freebsd.org/doc/handbook/network-nfs.html
          There has to be a way!! Just look at this:

          Code:
          http://www.linuxconfig.org/HowTo_configure_NFS
          Ubuntu:

          Code:
          http://www.cyberciti.biz/tips/ubuntu-linux-nfs-client-configuration-to-mount-nfs-share.html
          Experts, help, please...

          Comment


          • #6
            I figured it out... I combined what Zeini & co. wrote on their Wiki site with BuyukBang's PM and made it work!

            At the moment I am testing BuyukBang's new Priority Manager 1.8. One of the functions is automount NFS shared folders from external machines.

            I figured a way different to what he had in mind but it works at my end... He needs to test it at his end first and then we'll see when more of you test if it is kinda universal...

            From my Synology NAS [Linux OS] I simply activate NFS sharing, create Sharing Folders and then install and configure Priority Manager 1.8 and it all works really well, including VOB files [DVDs]. Must test more demanding mkv files. Already tried 720 and all was fine, more or less. Must find stuff with DTS sound...

            Cheerio!

            Comment


            • #7
              Here's what I did, quickly described:

              1) On Synology DS210j NAS, I created the shared folders [I will mention them later on].

              2) Then, I activated NFS [Linux streaming protocol, as opposed to Windows, CIFS].

              3) I also created a user AZboxHD [with all the details, as you will see, including the password]. Otherwise all else is done from admin account, with a password. One needs to give rights to that user [Write/Read according what your needs are, in various folders].

              4) Each Shared Folder needs to be edited -> NFS Privileges. Here I gave them to my AZbox HD in the form of its IP address [192.168.x.x].

              Even though I have a admin account with username/password to log in - it is then not necessary, when you do the

              5) Settings in Priority Manager:

              NFS_MOUNT=1


              REMOTE_IP=192.168.x.x


              CHECK_PATH=/DATA/movie -> this is because I have no HDD attached to my AZbox HD, otherwise [if you do have an internal or external USB HDD] BuyukBang tells me one should create a new, different folder from the default one and then the CHECK_PATH and the following lines differ slightly.

              Here are mine [for DS210j NAS, which is seen as having "volume1" as its storage capacity + the Sharing Folders, as you can see below = video, music, photo and TVrecord]:

              Code:
               NFS[1]="mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.x.x:/volume1/video /DATA/movie"
               NFS[2]="mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.x.x:/volume1/music /DATA/music"
               NFS[3]="mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.x.x:/volume1/photo /DATA/picture"
               NFS[4]="mount -t nfs -o nolock,rsize=8192,wsize=8192 192.168.x.x:/volume1/TVRecord /DATA/recordfile"
              5a) Here are my other settings from his PM 1.8 Beta, that I am testing [you must do your own, according to your setup and needs/preferences!!!]:

              Code:
              #!/bin/sh
               # PRIORITY MANAGER V1.8 BY BUYUKBANG
               #---------------------------------------------------------------------------------------#
               PRIORITY_MANAGEMENT=1
               KILL_TV_EMU=0 
               #---------------------------------------------------------------------------------------#
               HIDDEN_CHN_LST_PASS=00000
               #---------------------------------------------------------------------------------------#
               DOM_SPEED=1
               #---------------------------------------------------------------------------------------#
               UPGRADE_BUSYBOX=1
               #---------------------------------------------------------------------------------------#
               CRON=0
               #---------------------------------------------------------------------------------------#
               SWAPPER=1
               SWAPSIZE=204800            # ==> SIZE OF SWAP FILE IN BYTES.
               SWAPDEVICE=/DATA/usb1/sda1
                                          # ==> CHOOSE DEVICE, WHERE TO CREATE SWAPFILE
                                          # FOR INTERNAL HDD DISK SET SWAPDEVICE AS  : /DATA/hdb1
                                          # FOR USB1 HDD/FLASH DISK SET SWAPDEVICE AS: /DATA/usb1/sda1
                                          # FOR USB2 HDD/FLASH DISK SET SWAPDEVICE AS: /DATA/usb2/sda1
               #---------------------------------------------------------------------------------------#
               DEEP_SLEEP=0
               #---------------------------------------------------------------------------------------#
               MOVE_PLUGINS=0
               #---------------------------------------------------------------------------------------#
               SCHEDULED_BACKUP=0
               #---------------------------------------------------------------------------------------#
               ACTIONS=0
               #---------------------------------------------------------------------------------------#
               CIF_MOUNT=0
               #--------------------------------------------------------------------------------------#
               VERBOSE_MODE=0
              BuyukBang will explain in more detail other possibilities, as in Linux there are always more ways to do the same thing...

              My experience with streaming from my Synology DS210j NAS so far:

              AVI - no problem.

              VOB [DVD files] - no problem!

              IMAX.Ride.Around.The.World.2006.1080p.BluRay.x264. mkv, with DTS sound -> drop-out just once, for a fraction of a second and a picture slow down for about 5 - 10 secs at one point [19th minute].

              At the same time I was copying large files onto my NAS from a USB HDD attached to it.

              Later on, I also tried a couple of concerts, mkv 1080, with DTS. Similar results. Watchable!!! Occasionally your picture will slow down for a few secs and DTS drop-outs will happen rarely! But it's watchable!

              In fact, I am impressed!!!!!!!!!!!!!!!!

              Both with what BuyukBang has done and with Synology DS210j NAS!!!

              But I have to somewhat change my perception of AZbox HD accordingly, I'm afraid.... It's not as bad as it seemed initially, when it comes to streaming to AZbox HD. One needs a Linux based NAS or PC, with NFS installed and properly configured and... maybe... Windows based sharing [CIFS] is more limited, it seems...

              Comment

              Working...
              X