You are not logged in.

#1 2018-01-13 02:17:37

orrin5250
Member
Registered: 2016-10-12
Posts: 24

[SOLVED] Unable to mount network drive

Well I am stumped after multiple rounds of troubleshooting.

I am unable to mount my NAS drive.  Very strange as in the past I have had it configured to automount reliably.  It is connected by ethernet cable to my (new) Xfinity router.  I can ping the drive's IP address.  The drive is also responding to attempts to connect via browser.  I have also successfully accessed it from a windows machine.  So I know it is functioning out there on the network.

On Arch however, no luck.

Attempting to mount manually:

$ sudo mount -v -t cifs //10.0.0.228/share /mnt/share -o user=orrin,password=xxxxx,vers=1.0
mount.cifs kernel mount options: ip=10.0.0.228,unc=\\10.0.0.228\share,vers=1.0,user=orrin,pass=********
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Journal content:

Jan 12 21:10:17 ryzen sudo[29475]:    orrin : TTY=pts/0 ; PWD=/home/orrin/Dropbox/todo ; USER=root ; COMMAND=/usr/bin/mount -v -t cifs //10.0.0.228/share /mnt/share -o user=orrin,password=xxxxx,vers=1.0
Jan 12 21:10:17 ryzen sudo[29475]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 12 21:10:17 ryzen kernel: CIFS VFS: mdfour: Crypto md4 allocation error -2
Jan 12 21:10:17 ryzen kernel: CIFS VFS: could not allocate crypto API arc4
Jan 12 21:10:17 ryzen kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
Jan 12 21:10:17 ryzen kernel: CIFS VFS: Send error in SessSetup = -13
Jan 12 21:10:17 ryzen kernel: CIFS VFS: cifs_mount failed w/return code = -13
Jan 12 21:10:17 ryzen sudo[29475]: pam_unix(sudo:session): session closed for user root

Adding sec=ntlm (just trying things):

$ sudo mount -v -t cifs //10.0.0.228/share /mnt/share -o user=orrin,password=xxxxx,vers=1.0,sec=ntlm
mount.cifs kernel mount options: ip=10.0.0.228,unc=\\10.0.0.228\share,vers=1.0,sec=ntlm,user=orrin,pass=********
mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Journalctl content:

Jan 12 20:41:11 ryzen sudo[28859]:    orrin : TTY=pts/0 ; PWD=/home/orrin/Dropbox/todo ; USER=root ; COMMAND=/usr/bin/mount -v -t cifs //10.0.0.228/share /mnt/share -o user=orrin,password=xxxxx,vers=1.0,sec=ntlm
Jan 12 20:41:11 ryzen sudo[28859]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 12 20:41:11 ryzen kernel: CIFS VFS: mdfour: Crypto md4 allocation error -2
Jan 12 20:41:11 ryzen kernel: CIFS VFS: Error -2 during NTLM authentication
Jan 12 20:41:11 ryzen kernel: CIFS VFS: Send error in SessSetup = -2
Jan 12 20:41:11 ryzen kernel: CIFS VFS: cifs_mount failed w/return code = -2
Jan 12 20:41:11 ryzen sudo[28859]: pam_unix(sudo:session): session closed for user root

Googling these CIFS VFS errors didn't turn up much that seemed helpful.

Any other info I should provide?  Thanks.

Last edited by orrin5250 (2018-01-15 10:08:59)

Offline

#2 2018-01-13 12:34:26

seth
Member
Registered: 2012-09-03
Posts: 5,446

Re: [SOLVED] Unable to mount network drive

uname -a
pacman -Qs linux
modinfo md4

Offline

#3 2018-01-14 09:38:20

orrin5250
Member
Registered: 2016-10-12
Posts: 24

Re: [SOLVED] Unable to mount network drive

Thanks.

$ uname -a
Linux ryzen 4.13.11-1-ARCH #1 SMP PREEMPT Thu Nov 2 10:25:56 CET 2017 x86_64 GNU/Linux
$ pacman -Qs linux

local/alsa-lib 1.1.5-1
    An alternative implementation of Linux sound support
local/alsa-utils 1.1.5-2
    An alternative implementation of Linux sound support
local/archlinux-keyring 20180108-1
    Arch Linux PGP keyring
local/avahi 0.7-2
    Service Discovery for Linux using mDNS/DNS-SD -- compatible with Bonjour
local/filesystem 2017.10-2 (base)
    Base Arch Linux files
local/iptables 1.6.1-2
    Linux kernel packet control tool
local/keyutils 1.5.10-1
    Linux Key Management Utilities
local/kmod 24-1
    Linux kernel module management tools and library
local/ladspa 1.13-6
    Linux Audio Developer's Simple Plugin API (LADSPA)
local/libaio 0.3.110-1
    The Linux-native asynchronous I/O facility (aio) library
local/libiec61883 1.2.0-4
    A higher level API for streaming DV, MPEG-2 and audio over Linux IEEE 1394
local/libimobiledevice 1.2.0+66+g5a85432-1
    Library that talks the protocols to support iPhone and iPod Touch devices on Linux
local/libraw1394 2.1.2-1
    Provides an API to the Linux IEEE1394 (FireWire) driver
local/libutil-linux 2.31.1-1
    util-linux runtime libraries
local/libva 2.0.0-2
    Video Acceleration (VA) API for Linux
local/libxshmfence 1.2-1
    a library that exposes a event API on top of Linux futexes
local/linux 4.14.13-1 (base)
    The Linux kernel and modules
local/linux-api-headers 4.14.8-1
    Kernel headers sanitized for use in userspace
local/linux-firmware 20171206.fdee922-1
    Firmware files for Linux
local/linux-headers 4.14.13-1
    Header files and scripts for building modules for Linux kernel
local/lirc 1:0.9.4.d-1
    Linux Infrared Remote Control utilities
local/man-pages 4.14-1 (base)
    Linux man pages
local/mdadm 4.0-1 (base)
    A tool for managing/monitoring Linux md device arrays, also known as Software RAID
local/mplayer 37998-2
    Media player for Linux
local/net-tools 1.60.20160710git-1
    Configuration tools for Linux networking
local/nvidia 387.34-19
    NVIDIA drivers for linux
local/pacman-mirrorlist 20171203-1
    Arch Linux mirror list for use by pacman
local/util-linux 2.31.1-1 (base base-devel)
    Miscellaneous system utilities for Linux
local/v4l-utils 1.12.5-1
    Userspace tools and conversion library for Video 4 Linux
local/wicd 1.7.4-1
    Wired and wireless network manager for Linux
local/wicd-gtk 1.7.4-1
    Wired and wireless network manager for Linux - GTK client
modinfo: ERROR: Module alias md4 not found.

Offline

#4 2018-01-14 09:42:00

seth
Member
Registered: 2012-09-03
Posts: 5,446

Re: [SOLVED] Unable to mount network drive

local/linux 4.14.13-1 (base)
    The Linux kernel and modules
Linux ryzen 4.13.11-1-ARCH #1 SMP PREEMPT Thu Nov 2 10:25:56 CET 2017 x86_64 GNU/Linux

You forgot to mount the boot partition while updating the kernel and now boot an old kernel which won't be able to load any modules at runtime.
The missing md4 is then one of the lesser problems, actually.

Offline

#5 2018-01-14 09:45:00

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 6,435

Re: [SOLVED] Unable to mount network drive

Or he simply hasn't rebooted

Offline

#6 2018-01-14 10:01:28

orrin5250
Member
Registered: 2016-10-12
Posts: 24

Re: [SOLVED] Unable to mount network drive

I have rebooted, and now:

$ uname -a
Linux ryzen 4.14.13-1-ARCH #1 SMP PREEMPT Wed Jan 10 11:14:50 UTC 2018 x86_64 GNU/Linux

and

local/linux 4.14.13-1 (base)
    The Linux kernel and modules

Offline

#7 2018-01-14 12:05:24

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 7,606
Website

Re: [SOLVED] Unable to mount network drive

Any change in the journal output when you try to mount the network drive?

Aside: does your NAS really only support v1.0 of the cifs/smb protocol, or are you just flailing around with mount options in the hopes that something will work?


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#8 2018-01-14 14:09:33

seth
Member
Registered: 2012-09-03
Posts: 5,446

Re: [SOLVED] Unable to mount network drive

I would have assumed things to work now - at least the original error can should™ no longer occur, it's because the md4 module isn't loaded (basically no kernel crypto working)

Offline

#9 2018-01-15 10:08:20

orrin5250
Member
Registered: 2016-10-12
Posts: 24

Re: [SOLVED] Unable to mount network drive

seth wrote:

I would have assumed things to work now - at least the original error can should™ no longer occur, it's because the md4 module isn't loaded (basically no kernel crypto working)

Aaannnnd it works!  Thanks.

WorMzy wrote:

Aside: does your NAS really only support v1.0 of the cifs/smb protocol, or are you just flailing around with mount options in the hopes that something will work?

Most definitely just flailing smile.  I had discovered in other posts that this can be an issue.  I wasn't sure how to determine what protocol my NAS supports specifically.  You have to understand I am just your friendly neighborhood ER doc who hates windows and loves linux, and especially I love arch.  I don't have a tech background but I can muddle through (with the wiki, forums, and google) in most cases for my needs.  Every once in a while something pops up that is beyond me and I need help.  And then I learn something new.  I will forever be in the newbie corner.

For what it's worth I just tried mounting without vers option and I get "mount error(112): Host is down" with journal as follows:

Jan 15 05:04:39 ryzen kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.

Interesting because I never had to designate that option previously.  But for my purposes it works now so I'm good.

Thanks again everyone.

Last edited by orrin5250 (2018-01-15 10:19:08)

Offline

Board footer

Powered by FluxBB