Quantcast
Aktuelles
Digital Eliteboard - Das Digitale Technik Forum

Registriere dich noch heute kostenlos, um Mitglied zu werden! Sobald du angemeldet bist, kannst du auf unserer Seite aktiv teilnehmen, indem du deine eigenen Themen und Beiträge erstellst und dich über deinen eigenen Posteingang mit anderen Mitgliedern unterhalten kannst! Zudem bekommst du Zutritt zu Bereichen, welche für Gäste verwehrt bleiben

Registriere dich noch heute kostenlos, um Mitglied zu werden! Sobald du angemeldet bist, kannst du auf unserer Seite aktiv teilnehmen, indem du deine eigenen Themen und Beiträge erstellst und dich über deinen eigenen Posteingang mit anderen Mitgliedern unterhalten kannst! Zudem bekommst du Zutritt zu Bereichen, welche für Gäste verwehrt bleiben

NFS Freigabe bleibt nicht erhalten

hude4

Ist oft hier
Registriert
12. März 2013
Beiträge
106
Reaktionspunkte
6
Punkte
48
Guten Morgen alle zusammen,
ich kämpfe schon seit einigen Tagen mit einem Problem herum und komme einfach nicht weiter. Ich hoffe ihr könnt mir dabei helfen.
Zuerst mal meine Hardware:
Gigablue UE4K und Gigablue QuadPlus
NAS mit Openmediavault
alle mit LAN verbunden

Ich möchte gerne mit den Gigablue´s per NFS auf die freigaben meiner NAS zugreifen. Das habe ich auch schon recht gut hinbekommen. ABER die Freigaben bleiben nicht bestehen. sobald ich einen Neustart des Receivers mache sind die Freigaben verschwunden
Hier mal meine Einstellungen und wie ich vorgegangen bin:
Exports NAS:
Code:
/export/Serien 192.168.1.5(fsid=1,rw,sync,wdelay,hide,no_subtree_check,fsid=0,s$

dann einen Ordner auf der Gig erstellet
Code:
 mkdir /media/hdd/Serien

mount einbinden:
Code:
 mount -t nfs 192.168.1.76:/export/Serien /media/hdd/Serien

Tadaaa Freigabe ist Vorhanden und zugriff funktionier auch. Soweit so gut.
Box neu gestartet, freigaben verschwunden....
Google suche gestartet und stundenlang mit der auto.network und fstab herumprobiert. Die Freigaben wollen einfach nicht bestehen bleiben...

Hier mal die auto.network
Code:
Serien -fstype=nfs,rw,soft,nolock,rsize=8192,wsize=8192 192.168.1.76:/media/hdd/Serien

Und die Export Datei habe ich natürlich auch bearbeitet (hier vom Client)
Code:
/media/hdd/movie/Serien 192.168.1.76(rw,sync,no_subtree_check,sec=sys,secure,no_root_squash,no_all_squash)

Und hier die vom Server
Code:
/export/Serien 192.168.1.4/5(fsid=1,rw,sync,no_subtree_check,sec=sys,secure,no_root_squash,no_all_squash)

Ich hoffe ihr könnt mir dabei weiterhelfen dieses Problem zu lösen.

Lg Mario
 
Zuletzt bearbeitet:
Hallo,
was meinst du mit "die Export Datei habe ich natürlich auch bearbeitet (hier vom Client)" ??
Die exports-Datei ist nur beim Server von Interesse. Darin wird festgelegt, was via NFS freigegeben wird.
In den /etc/exports Dateien der Clients werden nur eigene Freigaben eingetragen.

Gruß
TOM
 
Kann es sein, daß automount beim Start nicht geladen wird?
Prüf das mal nach (Befehl: ps -e).

LG Kati

Und poste mal Deine auto.master und evtl. die autofs.conf.
Die fstab spielt hier m.E. keine Rolle.

LG Kati
 
Bitteschön :)
Automount wird geladen (PID530)

Code:
root@gbquadplus:~# ps -e
  PID TTY          TIME CMD
    1 ?        00:00:01 init
    2 ?        00:00:00 kthreadd
    3 ?        00:00:14 ksoftirqd/0
    5 ?        00:00:00 kworker/0:0H
    7 ?        00:00:03 rcu_sched
    8 ?        00:00:00 rcu_bh
    9 ?        00:00:00 migration/0
   10 ?        00:00:00 lru-add-drain
   11 ?        00:00:00 cpuhp/0
   12 ?        00:00:00 cpuhp/1
   13 ?        00:00:00 migration/1
   14 ?        00:00:00 ksoftirqd/1
   15 ?        00:00:00 kworker/1:0
   16 ?        00:00:00 kworker/1:0H
   17 ?        00:00:00 kdevtmpfs
   18 ?        00:00:00 oom_reaper
   19 ?        00:00:00 writeback
   20 ?        00:00:00 crypto
   21 ?        00:00:00 kworker/0:1
   22 ?        00:00:00 bioset
   23 ?        00:00:00 kblockd
   24 ?        00:00:00 ata_sff
   25 ?        00:00:00 cfg80211
   26 ?        00:00:00 kworker/1:1
   27 ?        00:00:00 rpciod
   28 ?        00:00:00 xprtiod
   29 ?        00:00:01 kswapd0
   30 ?        00:00:00 vmstat
   31 ?        00:00:00 nfsiod
   32 ?        00:00:00 cifsiod
   59 ?        00:00:00 bioset
   60 ?        00:00:00 bioset
   61 ?        00:00:00 bioset
   62 ?        00:00:00 bioset
   63 ?        00:00:00 bioset
   64 ?        00:00:00 bioset
   65 ?        00:00:00 bioset
   66 ?        00:00:00 bioset
   67 ?        00:00:00 scsi_eh_0
   68 ?        00:00:00 scsi_tmf_0
   69 ?        00:00:00 scsi_eh_1
   70 ?        00:00:00 scsi_tmf_1
   71 ?        00:00:00 scsi_eh_2
   72 ?        00:00:00 scsi_tmf_2
   76 ?        00:00:00 bioset
   80 ?        00:00:00 bioset
   81 ?        00:00:00 bioset
   82 ?        00:00:00 bioset
   83 ?        00:00:00 bioset
   84 ?        00:00:00 deferwq
   85 ?        00:00:00 ubi_bgt0d
   86 ?        00:00:00 ubifs_bgt0_0
  124 ?        00:00:00 kworker/1:1H
  140 ?        00:00:00 kworker/0:1H
  141 ?        00:00:00 jbd2/sda1-8
  142 ?        00:00:00 ext4-rsv-conver
  168 ?        00:00:03 nx_sched
  169 ?        00:00:34 nx_sched_high_s
  170 ?        00:00:00 nx_sched_low_st
  171 ?        00:00:00 playback_pacing
  172 ?        00:02:32 dpcr_integrator
  173 ?        00:00:00 nx_sched_idle_s
  174 ?        00:00:01 nx_sched_low
  175 ?        00:00:00 nx_sched_high
  184 ?        00:01:47 tMCU
  186 ?        03:20:19 tLCD
  221 ?        00:00:00 kdvb-ca-en50221
  250 ?        00:00:00 bioset
  251 ?        00:00:00 xfsalloc
  252 ?        00:00:00 xfs_mru_cache
  422 ?        00:00:00 dbus-daemon
  427 ?        00:00:00 ipv6_addrconf
  428 ?        00:00:00 dropbear
  459 ?        00:00:21 tCIMAX
  467 ?        00:00:00 udhcpc
  477 ?        00:00:00 odhcp6c
  488 ?        00:00:00 rpcbind
  503 ?        00:00:00 lockd
  504 ?        00:00:00 nfsd
  505 ?        00:00:00 nfsd
  506 ?        00:00:00 nfsd
  507 ?        00:00:00 nfsd
  508 ?        00:00:00 nfsd
  509 ?        00:00:00 nfsd
  510 ?        00:00:00 nfsd
  511 ?        00:00:00 nfsd
  513 ?        00:00:00 rpc.mountd
  530 ?        00:02:46 automount
  540 ?        00:00:00 rpc.statd
  544 ?        00:00:00 inetd
  557 ?        00:00:11 openvpn
  567 ?        00:00:01 smbd
  572 ?        00:00:00 smbd-notifyd
  573 ?        00:00:00 cleanupd
  575 ?        00:00:05 nmbd
  588 ?        00:00:00 wsdd
  591 ?        00:00:00 shellinaboxd
  592 ?        00:00:00 shellinaboxd
  597 ?        00:00:00 syslogd
  599 ?        00:00:00 klogd
  602 ?        00:00:00 telnetd
  609 ?        00:00:28 avahi-daemon
  610 ?        00:00:00 avahi-daemon
  620 ?        00:00:00 OSCam_11.572-r7
  622 ?        00:29:25 OSCam_11.572-r7
  628 ?        00:00:00 vsftpd
  635 ?        00:00:02 crond
  643 ?        00:00:00 enigma2.sh
  670 ?        01:21:33 enigma2
 2879 ?        00:00:00 kworker/0:0
 3691 ?        00:00:00 dropbear
 3697 pts/0    00:00:00 bash
 3740 ?        00:00:00 kworker/0:2
 3829 pts/0    00:00:00 ps
 9011 ?        00:00:01 kworker/u4:0
19419 ?        00:00:01 kworker/u4:1
32600 ?        00:00:00 smbd

Hier die auto.master
Code:
/media/autofs  /etc/auto.network  --ghost

auto.conf
Code:
#
# Define default options for autofs.
#
[ autofs ]
#
# master_map_name - default map name for the master map.
#
#master_map_name = auto.master
#
# timeout - set the default mount timeout in secons. The internal
#        program default is 10 minutes, but the default installed
#        configuration overrides this and sets the timeout to 5
#        minutes to be consistent with earlier autofs releases.
#
timeout = 300
#
# master_wait - set the default maximum time to wait for the
#         master map to become available if it cannot
#         be read at program start (default 10, wait
#         for 10 seconds then continue).
#
# master_wait = 10
#
# negative_timeout - set the default negative timeout for
#              failed mount attempts (default 60).
#
#negative_timeout = 60
#
# mount_wait - time to wait for a response from mount(8).
#            Setting this timeout can cause problems when
#            mount would otherwise wait for a server that
#            is temporarily unavailable, such as when it's
#            restarting. The default setting (-1) of waiting
#            for mount(8) usually results in a wait of around
#            3 minutes.
#
#mount_wait = -1
#
# umount_wait - time to wait for a response from umount(8).
#
#umount_wait = 12
#
# browse_mode - maps are browsable by default.
#
browse_mode = no
#
# mount_nfs_default_protocol - set the default protocol that mount.nfs(8)
#                   uses when performing a mount. Autofs needs
#                   to know the default NFS protocol that
#                   mount.nfs(8) uses so it can do special case
#                   handling for its availability probe for
#                   different NFS protocols. Since we can't
#                   identify the default automatically we need
#                   to set it in our configuration.
#
#mount_nfs_default_protocol = 3
#
# append_options - append to global options instead of replace.
#
#append_options = yes
#
# logging - set default log level "none", "verbose" or "debug"
#
#logging = none
#
# force_standard_program_map_env - disable the use of the "AUTOFS_"
#            prefix for standard environemt variables when
#            executing a program map. Since program maps
#            are run as the privileded user this opens
#            automount(8) to potential user privilege
#            escalation when the program map is written
#            in a language that  can load components from,
#            for example, a user home directory.
#
# force_standard_program_map_env = no
#
# use_mount_request_log_id - Set whether to use a mount request log
#            id so that log entries for specific mount
#            requests can be easily identified in logs
#            that have multiple conncurrent requests.
#
#use_mount_request_log_id = no
#
# Define base dn for map dn lookup.
#
# Define server URIs
#
# ldap_uri - space seperated list of server uris of the form
#          <proto>://<server>[/] where <proto> can be ldap
#          or ldaps. The option can be given multiple times.
#          Map entries that include a server name override
#          this option.
#
#         This configuration option can also be used to
#         request autofs lookup SRV RRs for a domain of
#         the form <proto>:///[<domain dn>]. Note that a
#         trailing "/" is not allowed when using this form.
#         If the domain dn is not specified the dns domain
#         name (if any) is used to construct the domain dn
#         for the SRV RR lookup. The server list returned
#         from an SRV RR lookup is refreshed according to
#         the minimum ttl found in the SRV RR records or
#         after one hour, whichever is less.
#
#ldap_uri = ""
#
# ldap_timeout - timeout value for the synchronous API  calls
#          (default is LDAP library default).
#
#ldap_timeout = -1
#
# ldap_network_timeout - set the network response timeout (default 8).
#
#ldap_network_timeout = 8
#
# search_base - base dn to use for searching for map search dn.
#         Multiple entries can be given and they are checked
#         in the order they occur here.
#
#search_base = ""
#
# Define the LDAP schema to used for lookups
#
# If no schema is set autofs will check each of the schemas
# below in the order given to try and locate an appropriate
# basdn for lookups. If you want to minimize the number of
# queries to the server set the values here.
#
#map_object_class = nisMap
#entry_object_class = nisObject
#map_attribute = nisMapName
#entry_attribute = cn
#value_attribute= nisMapEntry
#
# Other common LDAP naming
#
#map_object_class = automountMap
#entry_object_class = automount
#map_attribute = ou
#entry_attribute = cn
#value_attribute= automountInformation
#
#map_object_class = automountMap
#entry_object_class = automount
#map_attribute = automountMapName
#entry_attribute = automountKey
#value_attribute= automountInformation
#
# auth_conf_file - set the default location for the SASL
#           authentication configuration file.
#
#auth_conf_file = /etc/autofs_ldap_auth.conf
#
# map_hash_table_size - set the map cache hash table size.
#             Should be a power of 2 with a ratio of
#             close to 1:8 for acceptable performance
#             with maps up to around 8000 entries.
#             See autofs.conf(5) for more details.
#
#map_hash_table_size = 1024
#
# use_hostname_for_mounts - nfs mounts where the host name resolves
#             to more than one IP address normally need
#             to use the IP address to esure a mount to
#             a host that isn't responding isn't done.
#             If that behaviour is not wanted then set
#            ths to "yes", default is "no".
#
#use_hostname_for_mounts = "no"
#
# disable_not_found_message - The original request to add this log message
#              needed it to be unconditional. That produces, IMHO,
#              unnecessary noise in the log so a configuration option
#              has been added to provide the ability to turn it off.
#              The default is "no" to maintain the current behaviour.
#
#disable_not_found_message = "no"
#
# sss_master_map_wait - When sssd is starting up it can sometimes return
#            "no such entry" for a short time until it has read
#             in the LDAP map information. Internal default is 0
#             seconds, don't wait but if there is a problem with
#             autofs not finding the master map at startup (when
#             it should) then try setting this to 10 to work
#             around it.
#
#sss_master_map_wait = 0
#
# Options for the amd parser within autofs.
#
# amd configuration options that are aren't used, haven't been
# implemented or have different behaviour within autofs.
#
# A number of the amd configuration options are not used by autofs,
# some because they are not relevant within autofs, some because
# they are done differently in autofs and others that are not yet
# implemented.
#
# Since "mount_type" is always autofs (because there's no user space
# NFS server) the configuration entries relating to that aren't used.
# Also, server availability is done differently within autofs so the
# options that relate to the amd server monitoring sub-system are
# also not used.
#
# These options are mount_type, auto_attrcache, portmap_program,
# nfs_vers_ping, nfs_allow_any_interface, nfs_allow_insecure_port,
# nfs_proto, nfs_retransmit_counter, nfs_retransmit_counter_udp,
# nfs_retransmit_counter_tcp, nfs_retransmit_counter_toplvl,
# nfs_retry_interval, nfs_retry_interval_udp, nfs_retry_interval_tcp,
# nfs_retry_interval_toplvl and nfs_vers.
#
#
# Other options that are not used within the autofs implementation:
#
# log_file, truncate_log - autofs used either stderr when running in
#    the foreground or sends its output to syslog so an alternate
#    log file (or truncating the log) can't be used.
#
# print_pid - there's no corresponding option for this within autofs.
#
# use_tcpwrappers, show_statfs_entries - there's no user space NFS
#    server to control access to so this option isn't relevant.
#    The show_statfs_entries can't be implemented for the same
#    reason.
#
# debug_mtab_file - there's no user space NFS server and autofs
#    avoids using file based mtab whenever possible.
#
# sun_map_syntax - obviously, are provided by autofs itself.
#
# plock, show_statfs_entries, preferred_amq_port - not supported.
#
# ldap_cache_maxmem, ldap_cache_seconds - external ldap caching
#    is not used by autofs.
#
# ldap_proto_version - autofs always attempts to use the highest
#    available ldap protocol version.
#
# cache_duration, map_reload_interval, map_options - the map
#    entry cache is continually updated and stale entries
#    cleaned on re-load, which is done when map changes are
#    detected so these configuration entries are not used
#    by autofs.
#
# localhost_address - is not used within autofs. This
#    configuration option was only used in the amd user
#    space server code and is not relevant within autofs.
#
#
# Options that are handled differently within autofs:
#
# pid_file - must be given as a command line option on startup.
#
# print_version - program version and feature information is obtained
#    by using the automount command line option "-V".
#
# debug_options, log_options - autofs has somewhat more limited
#    logging and debug logging options. When the log_options
#    options is encountered it is converted to the nearest
#    matching autofs logging option. Since the configuration
#    option debug_options would be handled the same way it
#    is ignored.
#
# restart_mounts - has no sensible meaning within autofs because autofs
#    always tries to re-connect to existing mounts. While this
#    has its own set of problems not re-connecting to existing
#    mounts always results in a non-functional automount tree if
#    mounts were busy at the last shutdown (as is also the case
#    with amd when using mount_type autofs).
#
# forced_unmounts - detaching mounts often causes serious problems
#    for users of existing mounts. It is used by autofs in some
#    cases, either at the explicit request of the user (with a
#    command line or init option) and in some special cases during
#    program operation but is avoided whenever possible.
#
#
# A number of configuration options are not yet implemented:
#
# fully_qualified_hosts - not yet implemented.
#
# unmount_on_exit - since autofs always tries to re-connect
#    to mounts left mounted from a previous shutdown this
#    is a sensible option to implement and that will be
#    done.
#
# exec_map_timeout - a timeout is not currently used for
#    for program maps, might be implemented.
#
# tag - the tag option is not implemented within autofs.
#
#
# Supported options:
#
# arch, karch, os, osver - these options default to what is returned
#    from uname(2) and can be overridden if required.
#
# full_os - has no default and must be set in the configuration
#    if used in maps.
#
# cluster - if not set defaults to the host domain name. This option
#    corresponds to the HP_UX cluster name (according to the amd
#    source) and is probably not used in Linux but is set anyway.
#
# vendor - has a default value of "unknown", it must be set in the
#    configuration if used in maps.
#
# auto_dir - is the base name of the mount tree used for external
#    mounts that are sometimes needed by amd maps. Its default
#    value is "/a".
#
# map_type - specifies the autofs map source, such as file, nis,
#    ldap etc. and has no default value set.
#
# map_defaults - is used to override /defaults entries within maps
#    and can be used to provide different defaults on specific
#    machines without having to modify centrally managed maps.
#    It is empty by default.
#
# search_path - colon seperated paths to search for maps that
#    are not specified as a full path.
#
# dismount_interval - is equivalent to the autofs timeout option. It
#    is only possible to use this with type "auto" mounts due
#    to the way the autofs kernel module performs expiry. It
#    takes its default value from the autofs internal default
#    of 600 seconds.
#
# browsable_dirs - make map keys visible in directory listings.
#    Note that support for the "fullybrowsable" option cannot
#    be added using the existing kernel to user space autofs
#    implementation.
#
# autofs_use_lofs - if set to "yes" autofs will attempt to use bind
#    mounts for type "link" entries when possible.
#
# nis_domain - allows setting of a domain name other than the system
#    default.
#
# local_domain - is used to override (or set) the host domain name.
#
# normalize_hostnames - if set to "yes" then the contents of ${rhost}
#    is translated in its official host name.
#
# domain_strip - if set to "yes" the domain name part of the host
#     is strippped when normalizing hostnames. This can be useful
#    when using of the same maps in a multiple domain environment.
#
# normalize_slashes - is set to "yes" by default and will collapse
#    multiple unescaped occurrences of "/" to a single "/".
#
# selectors_in_defaults, selectors_on_default - has a default value
#    of "no". If set to "yes" then any defaults entry will be
#    checked for selectors to determine the values to be used.
#    selectors_in_defaults is the preferred option to use.
#
# ldap_base - has no default value. It must be set to the base dn
#    that is used for queries if ldap is to be used as a map
#    source.
#
# ldap_hostports - has no default value set. It must be set to
#    the URI of the LDAP server to be used for lookups when
#    ldap is used a map source. It may contain a comma or
#    space seperated list of LDAP URIs.
#
# hesiod_base - the base name used for hesiod map sources.
#
# Additional configuration options added:
#
# linux_ufs_mount_type - set the default system filesystem type that's
#    used for mount type ufs. There's no simple way to determine
#    what the system default filesystem is and am-utils needs to
#    be continually updated to do this and can easily get it wrong
#    anyway.
#
#
# Define global options for the amd parser within autofs.
#
[ amd ]
#
# Override the internal default with the same timeout that
# is used by the override in the autofs configuration, sanity
# only change.
#
dismount_interval = 300
#
# map_type = file
#
# Overriding this can cause autofs to use less resources because
# it will use symlinks instead of bind mounts in certain cases.
# You should ensure that the autofs kernel module your using
# supports expration of symlinks for best results (although this
# appears to work reasonably well most of the time without the
# update).
#
# autofs_use_lofs = yes
#
# Several configuration options can be set per mount point.
# In particulr map_type, map_name, map_defaults, search_path,
# browsable_dirs, dismount_interval and selectors_in_defaults
# (not all of which are currently implemented, see above).
#
# Also, if a section for an amd mount point is defined here
# it isn't necessary to specify the format in the corresponding
# master map entry and the format will be inherited for type
# "auto" mounts.
#
# [ /expamle/mount ]
# dismount_interval = 60
# map_type = nis
 
Zuletzt bearbeitet von einem Moderator:
OK habe ich erledigt, jedoch ohne Erfolg.
hier nochmal die auto.network

Code:
Serien -fstype=nfs,rw,soft,nolock,rsize=8192,wsize=8192 192.168.1.76:/export/Serien

stimmt die eigentlich???
 
Du mußt nach der Änderung den Receiver neu starten.
Gemacht?

Die auto.network ist ok, wenn die Parameter stimmen, also z.B.:

- 192.168.1.76 muß die IP-Adresse des NAS sein
- Der Freigabename des NAS muß "Serien" sein und um Verzeichnis /export liegen

Oben in Beitrag 1 hattest Du ein anderes Unterverzeichnis angegeben: /media/hdd/Serien

Nun ist es plötzlich /export/Serien?
 
Ja receiver habe ich mehrmals neu gestartet

Also das ist die Export von meinem NAS:
Code:
/export/Serien 192.168.1.4/5(fsid=1,rw,sync,no_subtree_check,sec=sys,secure,no_root_squash,no_all_squash

Mein Nas hat 192.168.1.76

mein Reci hat 192.168.1.5

und auf dem receiver hab ich das stehen:

Code:
Serien -fstype=nfs,rw,sync,no_subtree_check,sec=sys,secure,no_root_squash,no_all_squash 192.168.1.76:/export/Serien
 
Hm. Also in Posting 1 sind m.E. mehrere Widersprüche.

Einmal schreibst Du:
Exports :

/export/Serien 192.168.1.5(fsid=1,rw,sync,wdelay,hide,no_subtree_check,fsid=0,s$

Dann:

Und hier die vom Server

/export/Serien 192.168.1.4/5(fsid=1,rw,sync,no_subtree_check,sec=sys,secure,no_root_squash,no_all_squash)

Welche ist denn die richtige?

Wie auch immer: Wenn der automount richtig funktioniert, dann benötigst Du keinen mount-Befehl.

Ah, noch was: Die /etc/enigma2/automounts.xml solltest Du löschen oder umbenennen.
Und noch der Vollständigkeit halber: Die auto.network sollte die Dateirechte 644 haben, keinesfalls 755.
 
Zuletzt bearbeitet:
Natürlich ist der letzte Post der Aktuelle. Habe in der Zwischenzeit immer wieder neue Einstellungen probiert
Leider Funktioniert keine der Einstellungen

OK automounts.xml wurde gelöscht und dateireche auch geändert
 
Zuletzt bearbeitet:
Zurück
Oben