What happens is that nothing changes. the share that won't mount with "mount -a" does not mount during thhe boot.
On Wed, Sep 23, 2020, at 10:31 AM, Morbius1 wrote: > What is missing from your description is what happens after your system > has finished rebooting. > > Does the share mount when you issue one of the following commands: > > sudo mount -a > > Or: > > sudo mount /mnt/server_e > > Both of those commands will reference the fstab declaration. > > If it does this may not be a "bug" in cifs itself but in the boot > process where the line in fstab is being executed before the network > stack is operational on the client so it cannot connect to any remote > share - until after the entire boot process is complete. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896699 > > Title: > Mounting a share in fstab fails with BAD_NETWORK_NAME > > Status in cifs-utils package in Ubuntu: > Incomplete > > Bug description: > The following command works: > mount -t cifs //192.168.1.200/Drive_E /mnt/server_e -o > credentials=/root/.smbcredentials_server > > The following fstab entry fails: > //server/Server_E /mnt/server_e cifs > uid=0,credentials=/root/.smbcredentials_server,file_mode=0755,dir_mode=0755,vers=2.1,sec=ntlmssp > 0 0 > > There is an entry in hosts for server. It also fails with > //192.168.1.200/Server_E > Sometimes it says: > 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. > [ 2079.955734] CIFS VFS: BAD_NETWORK_NAME: \\192.168.1.200\Server_E > CIFS VFS: cifs_mount failed w/return code = -2 > > trying vers=1.0 and vers=3.0 makes no difference. > > There is no documentations of CIFS VFS error codes > There is no documentation of how to specify the SMB dialect. > People appear to have been having trouble with these things for at > least the past 10 years. > > I never had a problem with this on debian. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: samba 2:4.11.6+dfsg-0ubuntu1.4 > ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 > Uname: Linux 5.4.0-47-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia ufsd > ApportVersion: 2.20.11-0ubuntu27.8 > Architecture: amd64 > CIFSMounts: /root/smb4k/192.168.1.200/Drive_E //192.168.1.200/Drive_E > cifs > rw,relatime,vers=3.1.1,cache=strict,username=essin,domain=WORKGROUP,uid=0,forceuid,gid=0,forcegid,addr=192.168.1.200,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1 > CasperMD5CheckResult: skip > CurrentDesktop: XFCE > Date: Tue Sep 22 17:35:02 2020 > InstallationDate: Installed on 2020-09-18 (4 days ago) > InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > ProcEnviron: > LANGUAGE=en_US > PATH=(custom, no user) > XDG_RUNTIME_DIR=<set> > LANG=en_US.UTF-8 > SHELL=/bin/bash > SambaClientRegression: Yes > SourcePackage: samba > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1896699/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896699 Title: Mounting a share in fstab fails with BAD_NETWORK_NAME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1896699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
