Tumbleweed: NFS-Mounts gehen manchmal, manchmal aber auch nicht

Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

Hinweis: In dem Thema Tumbleweed: NFS-Mounts gehen manchmal, manchmal aber auch nicht gibt es 11 Antworten auf 2 Seiten. Der letzte Beitrag () befindet sich auf der letzten Seite.
  • An den Vodafone-Router kann man nur analoge Telefone mit Kabel anstecken. Ich habe aber nur DECT-Telefone (kabellos), daher brauche die die Fritzbox 6591 direkt am Kabelanschluss.

    Habe jetzt auf wicked und feste IP umgestellt. Bekomme beim Booten jetzt allerdings Fehler bei den NFS-Mounts, kann aber nicht lesen, was genau, weil es zu schnell durch rollt. Vermutlich das, was ich dann in /var/log/messages finde. Nach dem KDE-Login sind aber alle Mounts da.

    Quellcode

    1. 2019-10-03T13:12:16.187568+02:00 frodo systemd[1]: home-oliver-dvblink.mount: Mount process finished, but there is no mount.
    2. 2019-10-03T13:12:16.187697+02:00 frodo systemd[1]: home-oliver-dvblink.mount: Failed with result 'protocol'.
    3. 2019-10-03T13:12:16.187772+02:00 frodo btrfsmaintenance-refresh-cron.sh[1322]: Refresh timer btrfs-balance for weekly
    4. 2019-10-03T13:12:16.187847+02:00 frodo systemd[1]: Failed to mount /home/oliver/dvblink.
    5. 2019-10-03T13:12:16.187928+02:00 frodo systemd[1]: Dependency failed for Remote File Systems.
    6. 2019-10-03T13:12:16.188988+02:00 frodo systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
    7. 2019-10-03T13:12:16.189169+02:00 frodo systemd[1]: home-oliver-Drive.mount: Mount process finished, but there is no mount.
    8. 2019-10-03T13:12:16.189242+02:00 frodo systemd[1]: home-oliver-Drive.mount: Failed with result 'protocol'.
    9. 2019-10-03T13:12:16.189412+02:00 frodo systemd[1]: Failed to mount /home/oliver/Drive.
    10. 2019-10-03T13:12:16.190321+02:00 frodo systemd[1]: home-oliver-tausch.mount: Mount process finished, but there is no mount.
    11. 2019-10-03T13:12:16.190400+02:00 frodo systemd[1]: home-oliver-tausch.mount: Failed with result 'protocol'.
    12. 2019-10-03T13:12:16.190547+02:00 frodo systemd[1]: Failed to mount /home/oliver/tausch.
    13. 2019-10-03T13:12:16.191501+02:00 frodo systemd[1]: data.mount: Mount process finished, but there is no mount.
    14. 2019-10-03T13:12:16.191575+02:00 frodo systemd[1]: data.mount: Failed with result 'protocol'.
    15. 2019-10-03T13:12:16.191727+02:00 frodo systemd[1]: Failed to mount /data.
    16. 2019-10-03T13:12:16.192644+02:00 frodo systemd[1]: home-oliver-MyVideos.mount: Mount process finished, but there is no mount.
    17. 2019-10-03T13:12:16.192725+02:00 frodo systemd[1]: home-oliver-MyVideos.mount: Failed with result 'protocol'.
    18. 2019-10-03T13:12:16.192857+02:00 frodo systemd[1]: Failed to mount /home/oliver/MyVideos.
    19. 2019-10-03T13:12:16.194210+02:00 frodo systemd[1]: backup.mount: Mount process finished, but there is no mount.
    20. 2019-10-03T13:12:16.194285+02:00 frodo systemd[1]: backup.mount: Failed with result 'protocol'.
    21. 2019-10-03T13:12:16.194437+02:00 frodo systemd[1]: Failed to mount /backup.
    22. 2019-10-03T13:12:16.196813+02:00 frodo systemd[1]: Starting Permit User Sessions...
    23. 2019-10-03T13:12:16.199358+02:00 frodo systemd[1]: Starting Automounts filesystems on demand...
    24. 2019-10-03T13:12:16.203342+02:00 frodo systemd[1]: Started Permit User Sessions.
    25. 2019-10-03T13:12:16.205428+02:00 frodo systemd[1]: Starting Hold until boot process finishes up...
    26. 2019-10-03T13:12:16.207138+02:00 frodo systemd[1]: Starting X Display Manager...
    Alles anzeigen

    Für den Inhalt des Beitrages 136198 haftet ausdrücklich der jeweilige Autor: Oceanwaves

  • Habe es jetzt lesen können:

    Quellcode

    1. frodo:~ # systemctl status backup.mount
    2. ● backup.mount - /backup
    3. Loaded: loaded (/etc/fstab; generated)
    4. Active: failed (Result: protocol) since Thu 2019-10-03 15:10:15 CEST; 3min 13s ago
    5. Where: /backup
    6. What: diskstation:/volume1/backup
    7. Docs: man:fstab(5)
    8. man:systemd-fstab-generator(8)
    9. Oct 03 15:10:14 frodo systemd[1]: Mounting /backup...
    10. Oct 03 15:10:15 frodo systemd[1]: backup.mount: Mount process finished, but there is no mount.
    11. Oct 03 15:10:15 frodo systemd[1]: backup.mount: Failed with result 'protocol'.
    12. Oct 03 15:10:15 frodo systemd[1]: Failed to mount /backup.
    13. frodo:~ # systemctl --failed
    14. UNIT LOAD ACTIVE SUB DESCRIPTION
    15. ● backup.mount loaded failed failed /backup
    16. ● data.mount loaded failed failed /data
    17. ● home-oliver-Drive.mount loaded failed failed /home/oliver/Drive
    18. ● home-oliver-dvblink.mount loaded failed failed /home/oliver/dvblink
    19. ● home-oliver-MyVideos.mount loaded failed failed /home/oliver/MyVideos
    20. ● home-oliver-tausch.mount loaded failed failed /home/oliver/tausch
    21. LOAD = Reflects whether the unit definition was properly loaded.
    22. ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    23. SUB = The low-level unit activation state, values depend on unit type.
    24. 6 loaded units listed.
    Alles anzeigen
    Für die Mounts im User-Verzeichnis sieht es genauso aus. Die Mounts sind allerdings da.

    Klingt nach diesem Problem: sytemd: mount units fail with "Mount process finished, but there is no mount." · Issue #10872 · systemd/systemd · GitHub

    Für den Inhalt des Beitrages 136202 haftet ausdrücklich der jeweilige Autor: Oceanwaves