none
Server 2012 R2 共享文件访问中断,无法重连 RRS feed

  • 问题

  • 你好,

           最近半年遇到共享文件访问中断无法重连的问题。Server 2012 R2 共享文件夹,隔一段时间,出现访问中断。远程登陆服务器正常,检查LanManServer正常运行。但就无法访问共享。尝试重启LanManServer,之后服务会stopping,无法start。只能通过重启服务器修复改共享问题。

           在server 2012 R2 遇到该问题,后来重建服务器。迁移到server 2016,问题依然存在。

           现在平均一个星期出现一次,只能重启服务器修复。请求解决方案。

           能查到的日志只有SMBServer 

    Event ID 1016 

    The client attempted to reopen a continuously available handle, but the attempt failed. This typically indicates a problem with the network or underlying file being re-opened.

    Event ID 1020

    The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB.

    2018年7月20日 9:05

全部回复

  • 你好!

    感谢您的提问。

    根据报错初步判断,问题原因可能出在Storage文件服务器上。请尝试以下操作来修复,

    1 CMD中运行windows check disk 工具检查磁盘是否正常。

    https://technet.microsoft.com/en-us/library/ee872425.aspx

    2 从另外相同版且Lanmansevr服务可以正常启动的Windows Server上系统根目录windows/system32/drivers/srv2.sys 复制并替换到问题服务器上,重启服务尝试。

    3 2012R2安装以下更新:

    https://www.microsoft.com/en-sg/download/details.aspx?id=42738

    另外下面有几个和您问题类似的案例给您作个参考。

    https://social.technet.microsoft.com/Forums/lync/en-US/3316a5e0-fc2f-4300-917d-66e1527b4aa7/server-service-lanmanserver-will-not-start?forum=winserverfiles

    https://social.technet.microsoft.com/Forums/windows/en-US/e9567167-22db-4b8c-9f96-a08b97d507f9/server-2012-r2-file-server-stops-responding-to-smb-connections?forum=winserverfiles

    希望以上信息可以帮助到您。

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    2018年7月23日 9:35
    版主
  • 你好,

           网络及存储都已检查过,没有异常。环境是VM,虚拟机没有用直通存储。

           其实已经做过一次迁移了,但问题还是存在。现在系统版本是windows server 2016 standard

           你提供的类似案例,我之前也有serach过。按照上面的一下建议方案尝试了。也还是有问题,所以才来这里求解答。

           我在完整描述一次现象吧:

           服务器运行一段时间后(大概一周左右),就会出现所有Client端正在连接的会卡住,然后中断。新的client端访问共享,提示无法连接。服务器能正常远程,检查服务器,LanManServer服务运行,共享的sessios也是正常连着的。没其他异常。然后手动去重启LanManServer, 服务停止后,无法启动。提示服务starting或stopping。 重启服务器后,就正常了。

           就在刚才有出现一次,检查日志,也只有SMBServer 里面的日志。真是要折磨到疯呀。

          有说是SMB v1的问题,有说是补丁问题,论坛里也有不少遇到类似的问题,不算个别现象了。所以很想了解一下根本原因是什么。或者有什么有效的解决方式?

           在我的环境可以确认,存储和网络是没问题。根本问题还是出现在系统层面的。

           目前还有另外有一台,在相同的VM环境下的共享文件服务器,是windows server 2012 R2 standard。但这一台没有出现过这个问题。

           对于windows server 2016 standard的这个问题,有什么建议?

    2018年7月24日 3:06
  • 你好!

    感谢您的回复。

    从Windows server 2016 1709版本开始默认已经不使用SMB1.0(客户端和服务器端),并且再SMB协议网络通信下,客户端和服务器使用一致协商后的可支持的最大版本SMB协议。详细信息您可以参照以下链接:

    http://woshub.com/smb-1-0-support-in-windows-server-2012-r2/

    请注意:由于该网站不是由微软托管,链接可能会改变,官方并不保证此信息的准确性。

    请检查下服务器和客户端支持的SMB协议版本是否一致。

    另外,您看到的SMBServer日志,可以具体描述下或截下图么?(注意:请遮盖住您的隐私信息以防止个人信息的泄露。

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    2018年7月24日 6:56
    版主
  • 你好!

    请问您的这个事件进展如何?

    如还需帮助,可随时在论坛回复。

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    2018年7月26日 10:19
    版主
  • 你好!

    请问您的这个事件进展如何?

    如果我们提供的信息对您有帮助,您可以将其标记为答案,也可以给同社区其他成员遇到同样问题的时候,有一个方案的参考。

    如还需帮助,可随时在论坛回复的。

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    2018年7月29日 16:21
    版主
  • 你好,

          因为之前两个星期都没有再出现过问题了,所以暂时无法确认回复。

          但前天,再次发生这个问题。

          当出现问题后,所有连接都会卡住无法使用。检查LanManServer是运行中的。重启LanManServer,就会卡在stop后,无法再restart。 报错提示服务running / stopping 状态。只能通过重启才能恢复。

           从这个现象看来,这种中断是由于LanManServer完全卡死造成的,对此是否有相关解决的经验?

    日志如下,没出现问题的时候也会有这些日志,

    ------------------------------------------------------------------------------------------------------

    event id : 1016

    Reopen failed.

    Client Name: \\****
    Client Address: ****:30169
    User Name: *****
    Session ID: 0x4C0300000505
    Share Name: ****
    File Name: *****
    Resume Key: {00000000-0000-0000-0000-000000000000}
    Status: Object Name not found. (0xC0000034)
    RKF Status: STATUS_SUCCESS (0x0)
    Durable: true
    Resilient: false
    Persistent: false
    Reason: Reconnect durable file

    Guidance:

    The client attempted to reopen a continuously available handle, but the attempt failed. This typically indicates a problem with the network or underlying file being re-opened.

    -------------------------------------------------------------------------------------------------------

    event id : 1031

    The server detected a problem and has captured a live kernel dump to collect debug information.

    Reason: Stalled I/O
    Dump Location: %SystemRoot%\LiveKernelReports

    Guidance:

    The server supports the Live Dump feature, where the detection of a problem results in a kernel memory dump, but no bugcheck and reboot. This allows Microsoft Support to examine memory dumps without requiring a reboot or manual intervention. The reason code indicates the type of problem that was detected.

    Stalled I/O

    An I/O is taking an unreasonably long time to complete. Malfunctioning third-party file system minifilter drivers are a common source of this problem. Other causes include failed disks or a client-driven I/O workload that greatly exceeds the server's capacity.

    -------------------------------------------------------------------------------------------------------------

    event id : 1032

    The server detected a problem but was unable to capture a live kernel dump to collect debug information.

    Reason: Stalled I/O

    Guidance:

    The server supports the Live Dump feature, where the detection of a problem results in a kernel memory dump, but no bugcheck and reboot. This allows Microsoft Support to examine memory dumps without requiring a reboot or manual intervention. The reason code indicates the type of problem that was detected. In this case, the server's request to create a live kernel dump was rejected. This is usually due to the live kernel dump throttle, which prevents frequent dumps from consuming too much disk space. Either wait for the throttle limit to expire (by default, 7 days), or contact Microsoft Support for steps to override the throttle. This event is written to the log no more than once per day. The problem that caused the server to the request a live kernel dump may be occuring more frequently.

    Stalled I/O

    An I/O is taking an unreasonably long time to complete. Malfunctioning third-party file system minifilter drivers are a common source of this problem. Other causes include failed disks or a client-driven I/O workload that greatly exceeds the server's capacity.

    -------------------------------------------------------------------------------------------------------

    event id : 1020

    File system operation has taken longer than expected.

    Client Name: \\******
    Client Address: ******:52686
    User Name: ******
    Session ID: 0x500004000D85
    Share Name: *****
    File Name: ********
    Command: 6
    Duration (in milliseconds): 35419
    Warning Threshold (in milliseconds): 15000

    Guidance:

    The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB.

    2018年8月10日 1:21