NEWS
BackitUp NAS Error Speedport Smart 4
ioBroker Allgemein
91
Beiträge
4
Kommentatoren
7.9k
Aufrufe
3
Watching
-
@homoran sagte in BackitUp NAS Error Speedport Smart 4:
iobroker update -i
Ein paar Instanzen brauchen ein update, u.a. der BackitPu und der Admin. Die habe ich jetzt mal durchgeführt, aber die Fehlermedlung ist leider immer noch die selbe
@noidea sagte in BackitUp NAS Error Speedport Smart 4:
aber die Fehlermedlung ist leider immer noch die selbe
Das kann nicht sein, weil der Backitup-Adapter jetzt etwas anders gemountet wird. Die Meldung muss (leicht) anders sein.
Und bring die Kiste vollständig auf Stand.
-
Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "alexa2" : 3.23.2 , installed 3.23.2 Adapter "backitup" : 2.5.10 , installed 2.5.10 Adapter "discovery" : 3.1.0 , installed 3.0.3 [Updatable] Adapter "influxdb" : 3.2.0 , installed 3.1.8 [Updatable] Adapter "jarvis" : 3.1.2 , installed 3.1.2 Adapter "javascript" : 6.1.4 , installed 6.0.3 [Updatable] Controller "js-controller": 4.0.24 , installed 4.0.23 [Updatable] Adapter "modbus" : 5.0.11 , installed 5.0.5 [Updatable] Adapter "mqtt" : 4.0.7 , installed 4.0.7 Adapter "node-red" : 4.0.0 , installed 4.0.0 Adapter "robonect" : 0.1.4 , installed 0.1.4 Adapter "sainlogic" : 0.10.0 , installed 0.9.0 [Updatable] Adapter "shelly" : 6.0.0 , installed 6.0.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Adapter "terminal" : 1.0.0 , installed 0.2.6 [Updatable] Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.8.10 , installed 1.8.10@noidea wo kommt das jetzt her?
kein Prompt, kein Pfad, kein Befehl?? -
user@iobroker:~$ iobroker update -i Used repository: stable Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "alexa2" : 3.23.2 , installed 3.23.2 Adapter "backitup" : 2.5.10 , installed 2.5.10 Adapter "discovery" : 3.1.0 , installed 3.0.3 [Updatable] Adapter "influxdb" : 3.2.0 , installed 3.1.8 [Updatable] Adapter "jarvis" : 3.1.2 , installed 3.1.2 Adapter "javascript" : 6.1.4 , installed 6.0.3 [Updatable] Controller "js-controller": 4.0.24 , installed 4.0.23 [Updatable] Adapter "modbus" : 5.0.11 , installed 5.0.5 [Updatable] Adapter "mqtt" : 4.0.7 , installed 4.0.7 Adapter "node-red" : 4.0.0 , installed 4.0.0 Adapter "robonect" : 0.1.4 , installed 0.1.4 Adapter "sainlogic" : 0.10.0 , installed 0.9.0 [Updatable] Adapter "shelly" : 6.0.0 , installed 6.0.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Adapter "terminal" : 1.0.0 , installed 0.2.6 [Updatable] Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.8.10 , installed 1.8.10 user@iobroker:~$Das ist alles, was angezeigt wird, nicht mehr und nicht weniger.
Die nic. Nicht auf Stand gebrachten Instanzen, haben doch ersteinmal nichts mit dem Problem zu, oder?
-
user@iobroker:~$ iobroker update -i Used repository: stable Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "alexa2" : 3.23.2 , installed 3.23.2 Adapter "backitup" : 2.5.10 , installed 2.5.10 Adapter "discovery" : 3.1.0 , installed 3.0.3 [Updatable] Adapter "influxdb" : 3.2.0 , installed 3.1.8 [Updatable] Adapter "jarvis" : 3.1.2 , installed 3.1.2 Adapter "javascript" : 6.1.4 , installed 6.0.3 [Updatable] Controller "js-controller": 4.0.24 , installed 4.0.23 [Updatable] Adapter "modbus" : 5.0.11 , installed 5.0.5 [Updatable] Adapter "mqtt" : 4.0.7 , installed 4.0.7 Adapter "node-red" : 4.0.0 , installed 4.0.0 Adapter "robonect" : 0.1.4 , installed 0.1.4 Adapter "sainlogic" : 0.10.0 , installed 0.9.0 [Updatable] Adapter "shelly" : 6.0.0 , installed 6.0.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Adapter "terminal" : 1.0.0 , installed 0.2.6 [Updatable] Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.8.10 , installed 1.8.10 user@iobroker:~$Das ist alles, was angezeigt wird, nicht mehr und nicht weniger.
Die nic. Nicht auf Stand gebrachten Instanzen, haben doch ersteinmal nichts mit dem Problem zu, oder?
-
user@iobroker:~$ sudo apt update [sudo] password for user: Hit:1 https://repos.influxdata.com/debian jammy InRelease Hit:2 https://deb.nodesource.com/node_16.x jammy InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Get:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB] Get:5 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Get:6 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [831 kB] Get:7 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [566 kB] Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [785 kB] Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f Metadata [14.6 kB] Fetched 2422 kB in 2s (1226 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 61 packages can be upgraded. Run 'apt list --upgradable' to see them. W: https://repos.influxdata.com/debian/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. user@iobroker:~$ -
user@iobroker:~$ sudo apt update [sudo] password for user: Hit:1 https://repos.influxdata.com/debian jammy InRelease Hit:2 https://deb.nodesource.com/node_16.x jammy InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Get:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB] Get:5 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Get:6 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [831 kB] Get:7 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [566 kB] Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [785 kB] Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f Metadata [14.6 kB] Fetched 2422 kB in 2s (1226 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 61 packages can be upgraded. Run 'apt list --upgradable' to see them. W: https://repos.influxdata.com/debian/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. user@iobroker:~$@noidea sagte in BackitUp NAS Error Speedport Smart 4:
61 packages can be upgraded.
War mir fast klar. Auch Update-Stau.
Alles updaten.
-
@noidea sagte in BackitUp NAS Error Speedport Smart 4:
61 packages can be upgraded.
War mir fast klar. Auch Update-Stau.
Alles updaten.
-
@thomas-braun
Das mach ich mit,richtig?apt updateZuerst das influx-Repo korrigieren.
https://forum.iobroker.net/topic/62040/linux-debian-grafana-repo-muss-aktualisiert-werden/22
Dann
iob stop sudo apt update sudo apt full-upgrade sudo reboot -
Zuerst das influx-Repo korrigieren.
https://forum.iobroker.net/topic/62040/linux-debian-grafana-repo-muss-aktualisiert-werden/22
Dann
iob stop sudo apt update sudo apt full-upgrade sudo reboot@thomas-braun
Hab jetzt alles uptodate, aber nachwievor die gleiche FehlermeldungStarted iobroker ... [DEBUG] [mount] start with {"mountType":"CIFS","type":"storage","source":"local","mount":"//192.168.2.1","debugging":true,"fileDir":"/opt/iobroker/iobroker-data/backitup","wakeOnLAN":false,"macAd":"20:DE:20:DE:20:DE","wolTime":"25","smb":"vers=1.0","sudo":true,"cifsDomain":"WORKGROUP","clientInodes":false,"deleteOldBackup":false,"ownDir":false,"dir":"/SanDisk-USBExtremePro/Backup/Speedport","dirMinimal":"sharename/backupDir","user":"speedport","pass":"****","ignoreErrors":false} [DEBUG] [mount] - noserverino option: false [DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=1.0 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups" [DEBUG] [mount] - first mount attempt with smb option failed. try next mount attempt without smb option ... [DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups" [ERROR] [mount] - [undefined Error: Command failed: sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) [ERROR] [mount] - Error: Command failed: sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) -
@thomas-braun
Hab jetzt alles uptodate, aber nachwievor die gleiche FehlermeldungStarted iobroker ... [DEBUG] [mount] start with {"mountType":"CIFS","type":"storage","source":"local","mount":"//192.168.2.1","debugging":true,"fileDir":"/opt/iobroker/iobroker-data/backitup","wakeOnLAN":false,"macAd":"20:DE:20:DE:20:DE","wolTime":"25","smb":"vers=1.0","sudo":true,"cifsDomain":"WORKGROUP","clientInodes":false,"deleteOldBackup":false,"ownDir":false,"dir":"/SanDisk-USBExtremePro/Backup/Speedport","dirMinimal":"sharename/backupDir","user":"speedport","pass":"****","ignoreErrors":false} [DEBUG] [mount] - noserverino option: false [DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=1.0 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups" [DEBUG] [mount] - first mount attempt with smb option failed. try next mount attempt without smb option ... [DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups" [ERROR] [mount] - [undefined Error: Command failed: sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) [ERROR] [mount] - Error: Command failed: sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) -
user@iobroker:~$ smbclient -L 192.168.2.1 -U speedport Password for [WORKGROUP\speedport]: Sharename Type Comment --------- ---- ------- speedport Disk IPC$ IPC IPC Service (Speedport Smart 4 Typ A File-Server) Reconnecting with SMB1 for workgroup listing. Server Comment --------- ------- Workgroup Master --------- ------- WORKGROUP SPEEDPORT user@iobroker:~$ ls -lA /opt/iobroker/backups total 5416 -rw-rw-r--+ 1 iobroker iobroker 5423 Jan 22 18:36 grafana_2023_01_22-18_36_10_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 5420 Jan 22 19:59 grafana_2023_01_22-19_59_31_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 141185 Jan 22 18:36 influxDB_2023_01_22-18_36_08_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 143345 Jan 22 19:59 influxDB_2023_01_22-19_59_29_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 2563931 Jan 22 18:36 iobroker_2023_01_22-18_36_04_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 2563010 Jan 22 19:59 iobroker_2023_01_22-19_59_25_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 4691 Jan 22 18:36 jarvis.0_2023_01_22-18_36_15_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 4691 Jan 22 19:59 jarvis.0_2023_01_22-19_59_36_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 41159 Jan 22 18:36 javascripts_2023_01_22-18_36_15_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 41157 Jan 22 19:59 javascripts_2023_01_22-19_59_36_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 2685 Jan 22 18:36 zigbee.0_2023_01_22-18_36_09_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 2681 Jan 22 19:59 zigbee.0_2023_01_22-19_59_30_backupiobroker.tar.gz user@iobroker:~$Der Ordner backups ist wieder voll. Muss ich wieder leeren,oder?
Hab jetzt alles in dem Ordner gelöscht -
user@iobroker:~$ smbclient -L 192.168.2.1 -U speedport Password for [WORKGROUP\speedport]: Sharename Type Comment --------- ---- ------- speedport Disk IPC$ IPC IPC Service (Speedport Smart 4 Typ A File-Server) Reconnecting with SMB1 for workgroup listing. Server Comment --------- ------- Workgroup Master --------- ------- WORKGROUP SPEEDPORT user@iobroker:~$ ls -lA /opt/iobroker/backups total 5416 -rw-rw-r--+ 1 iobroker iobroker 5423 Jan 22 18:36 grafana_2023_01_22-18_36_10_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 5420 Jan 22 19:59 grafana_2023_01_22-19_59_31_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 141185 Jan 22 18:36 influxDB_2023_01_22-18_36_08_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 143345 Jan 22 19:59 influxDB_2023_01_22-19_59_29_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 2563931 Jan 22 18:36 iobroker_2023_01_22-18_36_04_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 2563010 Jan 22 19:59 iobroker_2023_01_22-19_59_25_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 4691 Jan 22 18:36 jarvis.0_2023_01_22-18_36_15_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 4691 Jan 22 19:59 jarvis.0_2023_01_22-19_59_36_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 41159 Jan 22 18:36 javascripts_2023_01_22-18_36_15_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 41157 Jan 22 19:59 javascripts_2023_01_22-19_59_36_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 2685 Jan 22 18:36 zigbee.0_2023_01_22-18_36_09_backupiobroker.tar.gz -rw-rw-r--+ 1 iobroker iobroker 2681 Jan 22 19:59 zigbee.0_2023_01_22-19_59_30_backupiobroker.tar.gz user@iobroker:~$Der Ordner backups ist wieder voll. Muss ich wieder leeren,oder?
Hab jetzt alles in dem Ordner gelöscht@noidea sagte in BackitUp NAS Error Speedport Smart 4:
Muss ich wieder leeren,oder?
Ja.
sudo -u iobroker rm /opt/iobroker/backups/*Versuch mal von Hand zu mounten:
sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=1.0 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups -
@noidea sagte in BackitUp NAS Error Speedport Smart 4:
Muss ich wieder leeren,oder?
Ja.
sudo -u iobroker rm /opt/iobroker/backups/*Versuch mal von Hand zu mounten:
sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=1.0 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backupsuser@iobroker:/$ sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=1.0 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) user@iobroker:/$ -
user@iobroker:/$ sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=1.0 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) user@iobroker:/$@noidea
Passwort muss natürlich ersetzt werden. -
user@iobroker:/$ sudo mount -t cifs -o username=speedport,password=****,domain=WORKGROUP,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=1.0 //192.168.2.1/SanDisk-USBExtremePro/Backup/Speedport /opt/iobroker/backups mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) user@iobroker:/$@noidea sagte in BackitUp NAS Error Speedport Smart 4:
Permission denied
passt!
hast du Sonderzeichen im passwort? versteht der Speedport das?
-
@noidea sagte in BackitUp NAS Error Speedport Smart 4:
Permission denied
passt!
hast du Sonderzeichen im passwort? versteht der Speedport das?
@homoran
Ich Blödmann. Natürlich muss ich das Passwort ersetzen. Sorry...Retrying with upper case share name mount error(6): No such device or address Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) user@iobroker:/$Jetzt kommt diese Meldung.
Ich habe keine Sonderzeichen im Passwort. Zum Testen ein einfaches Wort mit zwei Zahlen dahinter
-
@homoran
Ich Blödmann. Natürlich muss ich das Passwort ersetzen. Sorry...Retrying with upper case share name mount error(6): No such device or address Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) user@iobroker:/$Jetzt kommt diese Meldung.
Ich habe keine Sonderzeichen im Passwort. Zum Testen ein einfaches Wort mit zwei Zahlen dahinter
@noidea sagte in BackitUp NAS Error Speedport Smart 4:
dmesg -T | tail -n 20 -
@noidea sagte in BackitUp NAS Error Speedport Smart 4:
dmesg -T | tail -n 20 -
user@iobroker:/$ dmesg -T | tail -n 20 dmesg: read kernel buffer failed: Operation not permitted user@iobroker:/$ ``` code_textsudo dmesg -T | tail -n 20 -
sudo dmesg -T | tail -n 20user@iobroker:/$ sudo dmesg -T | tail -n 20 [Sun Jan 22 19:57:12 2023] CIFS: VFS: cifs_mount failed w/return code = -6 [Sun Jan 22 19:57:12 2023] CIFS: Attempting to mount \\192.168.2.1\SanDisk-USBExtremePro [Sun Jan 22 19:57:12 2023] CIFS: VFS: cifs_mount failed w/return code = -112 [Sun Jan 22 20:08:09 2023] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [Sun Jan 22 20:08:09 2023] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [Sun Jan 22 20:08:09 2023] CIFS: Attempting to mount \\192.168.2.1\SanDisk-USBExtremePro [Sun Jan 22 20:08:09 2023] CIFS: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE [Sun Jan 22 20:08:09 2023] CIFS: VFS: \\192.168.2.1 Send error in SessSetup = -13 [Sun Jan 22 20:08:09 2023] CIFS: VFS: cifs_mount failed w/return code = -13 [Sun Jan 22 20:10:33 2023] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [Sun Jan 22 20:10:33 2023] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [Sun Jan 22 20:10:33 2023] CIFS: Attempting to mount \\192.168.2.1\SanDisk-USBExtremePro [Sun Jan 22 20:10:33 2023] CIFS: VFS: cifs_mount failed w/return code = -6 [Sun Jan 22 20:10:33 2023] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [Sun Jan 22 20:10:33 2023] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [Sun Jan 22 20:10:33 2023] CIFS: Attempting to mount \\192.168.2.1\SANDISK-USBEXTREMEPRO [Sun Jan 22 20:10:33 2023] CIFS: VFS: cifs_mount failed w/return code = -6 user@iobroker:/$
878
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge