mount cifs with SMB 3.0 stop working

Bug #1730607 reported by Andrey Vertexx
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
High
Joseph Salisbury
Xenial
Incomplete
High
Joseph Salisbury

Bug Description

I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and a Windows Server 2012 R2 File Server with a File Share. I mounted a file share to my linux server with a cifs-utils.
Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 stopped working and my share not mounted.

sudo mount -t cifs //myserver.xxx.net/WebBackup -o username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive - not working

mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

if i change to vers=2.1 - it it work
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Nov 7 16:11 seq
 crw-rw---- 1 root audio 116, 33 Nov 7 16:11 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
InstallationDate: Installed on 2016-02-20 (626 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro
ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-98-generic N/A
 linux-backports-modules-4.4.0-98-generic N/A
 linux-firmware 1.127.23
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 4.4.0-98-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 11/26/2012
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v1.0
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v1.0
dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v1.0
dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
dmi.product.name: Virtual Machine
dmi.product.version: Hyper-V UEFI Release v1.0
dmi.sys.vendor: Microsoft Corporation
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Nov 21 11:15 seq
 crw-rw---- 1 root audio 116, 33 Nov 21 11:15 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
InstallationDate: Installed on 2016-02-20 (639 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-101-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro
ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-101-generic N/A
 linux-backports-modules-4.4.0-101-generic N/A
 linux-firmware 1.127.23
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty trusty
Uname: Linux 4.4.0-101-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 11/26/2012
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v1.0
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v1.0
dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v1.0
dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
dmi.product.name: Virtual Machine
dmi.product.version: Hyper-V UEFI Release v1.0
dmi.sys.vendor: Microsoft Corporation

Revision history for this message
Andrey Vertexx (vertexx) wrote :
Revision history for this message
Andrey Vertexx (vertexx) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1730607

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: xenial
Revision history for this message
Andrey Vertexx (vertexx) wrote : BootDmesg.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Andrey Vertexx (vertexx) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : ProcModules.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : UdevDb.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : UdevLog.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This may be a duplicate of bug 1729337. Can you try the test kernel I posted in that bug and see if it resolves your issue?

Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → High
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I'm also working a bisect for trusty in that other bug, so the link to the kernel you should test is:

http://kernel.ubuntu.com/~jsalisbury/lp1729337/xenial

Changed in linux (Ubuntu Xenial):
status: New → In Progress
Changed in linux (Ubuntu):
status: Triaged → In Progress
Changed in linux (Ubuntu Xenial):
importance: Undecided → High
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
Andrey Vertexx (vertexx) wrote :

Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-101-generic x86_64) still have a problem.

description: updated
Revision history for this message
Andrey Vertexx (vertexx) wrote : BootDmesg.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : ProcModules.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : UdevDb.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : UdevLog.txt

apport information

Revision history for this message
Andrey Vertexx (vertexx) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14

Changed in linux (Ubuntu Xenial):
status: In Progress → Incomplete
Changed in linux (Ubuntu):
status: In Progress → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.