Fritz!Box 7330 via fstab mit Kernel 4.13 mounten (cifs)

Einrichten des lokalen Netzes, Verbindung zu anderen Computern und Diensten.
Antworten
geier22

Fritz!Box 7330 via fstab mit Kernel 4.13 mounten (cifs)

Beitrag von geier22 » 01.11.2017 18:36:56

Ich meine seit dem Update auf Kernel 4.13 bekomme ich das Mounten meines Fritz!Box- NAS nicht mehr hin.
Leider kann ich es nicht genau zeitlich bestimmen, da ich das NAS selten benutze und meist den Mount- Befehl in der fstab für die Fritz!BOX auskommentiert habe.
Über die Dateimanager lässt sich das NAS problemlos mouten als
smb://192.168.0.1/fritz.nas/
Meine ursprüngliche Zeile in der fstab sah so aus:

Code: Alles auswählen

Fritzbox //192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/ /media/fritzbox cifs credentials=/etc/samba/auth,noauto,x-systemd.automount,defaults   0    0
das gibt jetzt folgendes Ergebnis (ich lass auch das unwesentliche mal drin):

Code: Alles auswählen

journalctl -b-1 |grep mount
Nov 01 16:56:50 sparkyxfce kernel: EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
Nov 01 16:56:50 sparkyxfce systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Nov 01 16:56:50 sparkyxfce systemd[1]: Set up automount media-fritzbox.automount.
Nov 01 16:56:50 sparkyxfce kernel: EXT4-fs (sdc1): re-mounted. Opts: discard
Nov 01 16:56:50 sparkyxfce systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
Nov 01 16:56:50 sparkyxfce kernel: EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
Nov 01 16:56:50 sparkyxfce kernel: EXT4-fs (sdc5): mounted filesystem with ordered data mode. Opts: discard
Nov 01 16:56:50 sparkyxfce kernel: EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)
Nov 01 16:56:50 sparkyxfce systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 681 (update-binfmts)
Nov 01 16:56:55 sparkyxfce systemd[1]: media-fritzbox.automount: Got automount request for /media/fritzbox, triggered by 1154 (pool)
Nov 01 16:56:57 sparkyxfce systemd[1]: media-Musik.automount: Got automount request for /media/Musik, triggered by 1283 (conky)
Nov 01 16:56:57 sparkyxfce kernel: EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null)
Nov 01 16:56:58 sparkyxfce kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB3 (vers=3.0), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 specify vers=1.0 on mount. For somewhat newer servers such as Windows 7 try vers=2.1.
Nov 01 16:56:59 sparkyxfce systemd[1]: media-fritzbox.mount: Mount process exited, code=exited status=32
Nov 01 16:56:59 sparkyxfce systemd[1]: media-fritzbox.mount: Failed with result 'exit-code'.
Ich hab dann die Empfehlung mit den Versionsnummern befolgt ( vers=1.0 funktionierte nicht)

Code: Alles auswählen

#Fritzbox
//192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/ /media/fritzbox cifs credentials=/etc/samba/auth,noauto,x-systemd.automount,defaults,vers=2.1   0    0

Code: Alles auswählen

journalctl -b |grep mount
Nov 01 17:41:17 sparkyxfce kernel: EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
Nov 01 17:41:17 sparkyxfce kernel: EXT4-fs (sdc1): re-mounted. Opts: discard
Nov 01 17:41:18 sparkyxfce systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
Nov 01 17:41:18 sparkyxfce kernel: EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
Nov 01 17:41:18 sparkyxfce kernel: EXT4-fs (sdc5): mounted filesystem with ordered data mode. Opts: discard
Nov 01 17:41:18 sparkyxfce kernel: EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)
Nov 01 17:41:18 sparkyxfce systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 649 (update-binfmts)
Nov 01 17:41:28 sparkyxfce kernel: CIFS VFS: cifs_mount failed w/return code = -112
Nov 01 17:41:28 sparkyxfce systemd[1]: media-fritzbox.mount: Mount process exited, code=exited status=32
Nov 01 17:41:28 sparkyxfce systemd[1]: media-fritzbox.mount: Failed with result 'exit-code'.
Nov 01 17:41:28 sparkyxfce systemd[1]: Failed to mount /media/fritzbox.
Nov 01 17:41:34 sparkyxfce systemd[1]: media-Musik.automount: Got automount request for /media/Musik, triggered by 1563 (conky)
Nov 01 17:41:34 sparkyxfce kernel: EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null)
Hab ich da einen Syntax Fehler drin oder wo ist der Hund begraben ? Die Fritz!Box 7330 ist halt ein etwas älteres Modell.
Zuletzt geändert von geier22 am 08.11.2017 16:52:51, insgesamt 1-mal geändert.

dufty2
Beiträge: 1709
Registriert: 22.12.2013 16:41:16

Re: Fritz!Box 7330 via fstab mit Kernel 4.13 mounten

Beitrag von dufty2 » 03.11.2017 15:49:40

Wenn Du über den Dateimanager mounten lässt, wie schaut denn dann der Mount aus:
# mount | grep media
?

Ein manuelles Mounten via
# mount /media/fritzbox
funktioniert?

Mmmh, vielleicht stand um "Nov 01 17:41:28" das Netzwerk noch nicht zur Verfügung?

geier22

Re: Fritz!Box 7330 via fstab mit Kernel 4.13 mounten

Beitrag von geier22 » 03.11.2017 18:50:51

Bin jetzt nicht am Rechner, aber wenn ich die Fritz!Box über den Dateimanager einhänge, wird
sie nach /run/user/1000/gvfs/ gemountet, und erscheint dann als
smb://192.168.0.1/fritz.nas/ im Dateimanager.
Das Mounten im Dateimanager geschieht ja über das Dialogfenster. Da geht es dann: Server (IP) -- Windowsfreigabe usw....

Die ursprüngliche Zeile in der fstab hat ja ewig funktioniert. Habe es bloß nicht immer benutzt, weil ich den Stick an der Fritz!Box sehr selten brauche.

geier22

Re: Fritz!Box 7330 via fstab mit Kernel 4.13 mounten

Beitrag von geier22 » 08.11.2017 16:50:53

Nur der Vollständigkeit halber: Der Versuch, das Fritz Nas über die Konsole zu mouten:

Code: Alles auswählen

# mount //192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/ /media/fritzbox 
Password for root@//192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/:  *******************
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
andre Varianten: bei der Passwortabfrage, ist es egal ob ich das PW für die Fritz!Box oder für das NAS eingebe.

Code: Alles auswählen

# mount //192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/ credentials=/etc/samba/auth
Couldn't chdir to credentials=/etc/samba/auth: No such file or directory

Code: Alles auswählen

# mount.cifs //192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/ credentials=/etc/samba/auth
Couldn't chdir to credentials=/etc/samba/auth: No such file or directory

Code: Alles auswählen

# mount.cifs //192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/ credentials=/home/hans/.smbcredentials
Couldn't chdir to credentials=/home/hans/.smbcredentials: No such file or directory
oder

Code: Alles auswählen

# mount.cifs //192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/ /media/fritzbox credentials=/home/hans/.smbcredentials
Password for root@//192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/:  ***
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

geier22

Re: Fritz!Box 7330 via fstab mit Kernel 4.13 mounten (cifs)

Beitrag von geier22 » 09.11.2017 03:05:41

Ich habe jetzt noch ein paar logs zusammengetragen, in der Hoffnung, dass irgendjemand ein Licht aufgeht :mrgreen:
Die zugehörige Zeile in der fstab für das Fritz Nas: ich habe die Position dieser Versions- Nr. wider hinten hingetan, da dies wohl die einzige Stelle ist, an der nicht gemeckert wird.
Auf diese Zeile beziehen sich alle nachfolgenden Protokollmeldungen:

Code: Alles auswählen

#Fritzbox
//192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/  /media/fritzbox  cifs credentials=/etc/samba/auth,noauto,x-systemd.automount,uid=1000,gid=1001,vers=2.1   0    0
dmesg:

Code: Alles auswählen

    6.273567] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    8.241485] fuse init (API version 7.26)
[   10.211886] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null)
[   12.239639] FS-Cache: Loaded
[   12.240042] Key type dns_resolver registered
[   12.245890] FS-Cache: Netfs 'cifs' registered for caching
[   12.245926] Key type cifs.spnego registered
[   12.245929] Key type cifs.idmap registered
[   13.055283] CIFS VFS: cifs_mount failed w/return code = -112
[   13.289410] CIFS VFS: cifs_mount failed w/return code = -112
[   13.521847] CIFS VFS: cifs_mount failed w/return code = -112
[   13.755659] CIFS VFS: cifs_mount failed w/return code = -112
[   14.012197] CIFS VFS: cifs_mount failed w/return code = -112
 

aus syslog:

Code: Alles auswählen

Nov  9 00:37:27 sparkyxfce systemd[1]: Reached target Graphical Interface.
Nov  9 00:37:27 sparkyxfce systemd[1]: Starting Update UTMP about System Runlevel Changes...
Nov  9 00:37:27 sparkyxfce systemd[1]: Started Update UTMP about System Runlevel Changes.
Nov  9 00:37:27 sparkyxfce kernel: [   13.055283] CIFS VFS: cifs_mount failed w/return code = -112
Nov  9 00:37:27 sparkyxfce systemd[1]: media-fritzbox.mount: Mount process exited, code=exited status=32
Nov  9 00:37:27 sparkyxfce systemd[1]: media-fritzbox.mount: Failed with result 'exit-code'.
Nov  9 00:37:27 sparkyxfce systemd[1]: Failed to mount /media/fritzbox.
Nov  9 00:37:27 sparkyxfce systemd[1]: Startup finished in 3.441s (kernel) + 9.615s (userspace) = 13.057s.
Nov  9 00:37:27 sparkyxfce systemd[1]: media-fritzbox.automount: Got automount request for /media/fritzbox, triggered by 1091 (gvfs-udisks2-vo)
Nov  9 00:37:27 sparkyxfce systemd[1]: Mounting /media/fritzbox...
Nov  9 00:37:27 sparkyxfce ntpd[783]: Listen normally on 6 eth0 192.168.0.40:123

aus boot.log:

Code: Alles auswählen

Starting /etc/rc.local Compatibility...
         Mounting /media/fritzbox...
         Starting keep memory of all UPnP devices that announced themselves...
[[0;32m  OK  [0m] Started /etc/rc.local Compatibility.
[[0;32m  OK  [0m] Started keep memory of all UPnP devices that announced themselves.
[[0;1;31mFAILED[0m] Failed to mount /media/fritzbox.
See 'systemctl status media-fritzbox.mount' for details.
[[0;1;33mDEPEND[0m] Dependency failed for Remote File Systems.
         Starting LSB: disk temperature monitoring daemon...
         Starting LSB: Mono XSP4...
         Starting LSB: exim Mail Transport Agent...
         Starting Permit User Sessions...
         Starting LSB: Brings up/down network automatically...
         Starting LSB: Start some power management scripts...

Code: Alles auswählen

$ systemctl status media-fritzbox.mount
● media-fritzbox.mount - /media/fritzbox
   Loaded: loaded (/etc/fstab; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2017-11-09 00:37:28 CET; 1h 44min ago
    Where: /media/fritzbox
     What: //192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/
     Docs: man:fstab(5)
           man:systemd-fstab-generator(8)
  Process: 1652 ExecMount=/bin/mount //192.168.0.1/fritz.nas/TOSHIBA-TransMemory-Mx-01/ /media/fritzbox -t cifs -o credentials=/etc/samba/auth,x-systemd.automount,uid=1000,gid=1001,vers=2.1 (code=exited, status=32)

Nov 09 00:37:28 sparkyxfce systemd[1]: Mounting /media/fritzbox...
Nov 09 00:37:28 sparkyxfce systemd[1]: media-fritzbox.mount: Mount process exited, code=exited status=32
Nov 09 00:37:28 sparkyxfce systemd[1]: media-fritzbox.mount: Failed with result 'exit-code'.
Nov 09 00:37:28 sparkyxfce systemd[1]: Failed to mount /media/fritzbox.
Nov 09 00:37:28 sparkyxfce systemd[1]: media-fritzbox.mount: Start request repeated too quickly.
Nov 09 00:37:28 sparkyxfce systemd[1]: media-fritzbox.mount: Failed with result 'exit-code'.
Nov 09 00:37:28 sparkyxfce systemd[1]: Failed to mount /media/fritzbox.
hans@sparkyxfce:~$ 
Und zu guter Letzt noch journalctl:

Code: Alles auswählen

$ journalctl --since="2017-11-09 00:37:27" --until="2017-11-09 00:37:29"
-- Logs begin at Fri 2017-10-20 00:59:52 CEST, end at Thu 2017-11-09 03:02:43 CET. --
Nov 09 00:37:27 sparkyxfce exim4[1362]: Starting MTA: exim4.
Nov 09 00:37:27 sparkyxfce systemd[1]: Started LSB: exim Mail Transport Agent.
Nov 09 00:37:27 sparkyxfce systemd[1]: Reached target Multi-User System.
Nov 09 00:37:27 sparkyxfce systemd[1]: Reached target Graphical Interface.
Nov 09 00:37:27 sparkyxfce systemd[1]: Starting Update UTMP about System Runlevel Changes...
Nov 09 00:37:27 sparkyxfce systemd[1]: Started Update UTMP about System Runlevel Changes.
Nov 09 00:37:27 sparkyxfce kernel: CIFS VFS: cifs_mount failed w/return code = -112
Nov 09 00:37:27 sparkyxfce systemd[1]: media-fritzbox.mount: Mount process exited, code=exited status=32
Nov 09 00:37:27 sparkyxfce systemd[1]: media-fritzbox.mount: Failed with result 'exit-code'.
Nov 09 00:37:27 sparkyxfce systemd[1]: Failed to mount /media/fritzbox.
Nov 09 00:37:27 sparkyxfce systemd[1]: Startup finished in 3.441s (kernel) + 9.615s (userspace) = 13.057s.
Nov 09 00:37:27 sparkyxfce systemd[1]: media-fritzbox.automount: Got automount request for /media/fritzbox, triggered by 1091 (gvfs-udisk
Nov 09 00:37:27 sparkyxfce systemd[1]: Mounting /media/fritzbox...
Nov 09 00:37:27 sparkyxfce ntpd[783]: Listen normally on 6 eth0 192.168.0.40:123
Nov 09 00:37:27 sparkyxfce ntpd[783]: new interface(s) found: waking up resolver
Nov 09 00:37:27 sparkyxfce systemd[1]: media-fritzbox.mount: Mount process exited, code=exited status=32
Nov 09 00:37:27 sparkyxfce systemd[1]: media-fritzbox.mount: Failed with result 'exit-code'.
Nov 09 00:37:27 sparkyxfce systemd[1]: Failed to mount /media/fritzbox.
Nov 09 00:37:27 sparkyxfce systemd[1]: media-fritzbox.automount: Got automount request for /media/fritzbox, triggered by 1091

Antworten