none
Windows Server2008 R2 Eeterpries系统内盘符突然消失导致共享不能访问的问题 RRS feed

  • 问题

  • 硬件环境:HP DL388G9 2颗E5-2620V4 2.10GHz的CPU 32G内存  阵列卡P440ar-2G 1T 7.2K 2.5 SAS*6 做的RAID 5

    操作系统 Windows Server 2008R2 Enterpries

    应用 Windwos  SQL Server 2008R2    RosemirrioHA  Trend micro officescan 

    角色 域内数据库服务器 文件共享服务器

    环境 两台DL 380 G9通过Rose mirrio HA做双机热备 进行共享文件和数据库的同步 两台主机一台IP为.11另一台为.12,共享地址为.2。配置RAID5之后总的磁盘容量为4.5T 其中分区如下 磁盘分区C盘为系统 D盘位共享文件磁盘 E盘存放数据库   客户端通过ODBC连接服务器端的数据库,通过网络驱动卷访问共享磁盘D

    故障 8月24日中午13点左右 客户端反应共享磁盘不能访问,于是登录服务器查看 发现盘符D在计算机中消失,电脑运行卡顿,RosemirroHA报源丢失,不能进行手动接管。为了尽快恢复故障对故障主机进行重启操作,操作后计算机中发现盘符D 车间也能够访问共享文件,但10分钟左右D盘再次消失,客户端无法访问。遂强制Rose MirroHA接管 切换到备机。下午16时许备机接管服务后登录故障主机 故障主机D盘恢复 运行正常。目前未发现杀毒软件报警以及硬件故障提示,想帮忙分析一下故障点在哪里 怎么进行排查,下面我会把故障前后的应用日志和系统日志贴出来,

    系统日志中 每天都有恨多连续的ID 1111的报错 帮忙看下是什么原因

    ID 1111 

    Driver HP ColorLaserJet M153-M154 PCL-6 (V4) required for printer HP ColorLaserJet M153-M154 is unknown. Contact the administrator to install the driver before you log in again.(局域网内打印机的型号不同)

    下面是系统故障时的几个紧急日志

    Log Name:      System
    Source:        Microsoft-Windows-GroupPolicy
    Date:          2020-08-24 2:25:30
    Event ID:      1096
    Task Category: None
    Level:         Error
    Keywords:      
    User:          IBE\hxh
    Computer:      IBESQL-P.ibe.triotech.com.cn
    Description:
    The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object LDAP://CN=User,cn={4250CF61-FF40-458A-9302-7B5F6E215DF3},cn=policies,cn=system,DC=ibe,DC=triotech,DC=com,DC=cn. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the file name and path that caused the failure.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
        <EventID>1096</EventID>
        <Version>0</Version>

     <Level>2</Level>

        <Task>0</Task>
        <Opcode>1</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2020-08-23T18:25:30.922826600Z" />
        <EventRecordID>92351</EventRecordID>
        <Correlation ActivityID="{6A66E169-B707-441F-937F-C80FEED994CD}" />
        <Execution ProcessID="2352" ThreadID="7704" />
        <Channel>System</Channel>
        <Computer>IBESQL-P.ibe.triotech.com.cn</Computer>
        <Security UserID="S-1-5-21-3727111372-1041532967-1050207845-1582" />
      </System>
      <EventData>
        <Data Name="SupportInfo1">2</Data>
        <Data Name="SupportInfo2">1254</Data>
        <Data Name="ProcessingMode">0</Data>
        <Data Name="ProcessingTimeInMilliseconds">22386</Data>
        <Data Name="ErrorCode">53</Data>
        <Data Name="ErrorDescription">The network path was not found. </Data>
        <Data Name="DCName">\\ibedc.ibe.triotech.com.cn</Data>
        <Data Name="GPOCNName">LDAP://CN=User,cn={4250CF61-FF40-458A-9302-7B5F6E215DF3},cn=policies,cn=system,DC=ibe,DC=triotech,DC=com,DC=cn</Data>
        <Data Name="FilePath">\\ibe.triotech.com.cn\SysVol\ibe.triotech.com.cn\Policies\{4250CF61-FF40-458A-9302-7B5F6E215DF3}\User\registry.pol</Data>
      </EventData>
    </Event

     下面是一些系统日志记录

    2020-08-24 2:25:30 1096
    The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object LDAP://CN=User,cn={4250CF61-FF40-458A-9302-7B5F6E215DF3},cn=policies,cn=system,DC=ibe,DC=triotech,DC=com,DC=cn. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the file name and path that caused the failure.
    2020-08-24 2:25:31 1085
    Windows failed to apply the Scripts settings. Scripts settings might have its own log file. Please click on the "More information" link.
    2020-08-24 13:44:51 ID 4227
    TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.

    2020年8月26日 3:14

全部回复