[quote=“Forzaalfa, post:42, topic:185496”]Thanks for helping me troubleshoot:
[code]root@MiOS_VERA:~# mount -t cifs -o username=,password=, vers=2.0 //[IP]/VeraLogs /VeraLogs
BusyBox v1.19.4 (2016-11-29 21:02:24 EET) multi-call binary.
Usage: mount [OPTIONS] [-o OPTS] DEVICE NODE
Mount a filesystem. Filesystem autodetection requires /proc.
-a Mount all filesystems in fstab
-i Don't run mount helper
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE Filesystem type
-O OPT Mount only filesystems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a]sync Writes are [a]synchronous
[no]atime Disable/enable updates to inode access times
[no]diratime Disable/enable atime updates to directories
[no]relatime Disable/enable atime updates relative to modification time
[no]dev (Dis)allow use of special device files
[no]exec (Dis)allow use of executable files
[no]suid (Dis)allow set-user-id-root programs
[r]shared Convert [recursively] to a shared subtree
[r]slave Convert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
[r]bind Bind a file or directory [recursively] to another location
move Relocate an existing mount point
remount Remount a mounted filesystem, changing flags
ro/rw Same as -r/-w
There are filesystem-specific -o flags.
root@MiOS_VERA:~#
[/code]
I assume its showing me options to say i wrote something wrong?
Haven’t rebooted manually for a year at least, but windows update roams free on that computer, so it probably did…
Rebooted now, didn’t help. :[/quote]
Lose the space before ‘vers’
mount -t cifs -o username=,password=,vers=2.0 //[IP]/VeraLogs /VeraLogs
No promises…
Also try vers=1.0 and 3.0
C