ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Hyper-V Failover Cluster FAILURE(S)

    IT Discussion
    6
    140
    12.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • KyleK
      Kyle @scottalanmiller
      last edited by

      @scottalanmiller said in Hyper-V Failover Cluster FAILURE(S):

      Do the switches report any overloading? A huge backup at the L3 routing points could do this, but would be super uncommon. But SAN traffic should never be routed, ever, and this would be a reason for that.

      Switches are not reporting any errors either. We pulled all those logs and found no network errors or hardware failure.

      1 Reply Last reply Reply Quote 0
      • DashrenderD
        Dashrender
        last edited by

        Is there a single switch that handles all traffic for SAN(storage traffic) and failover and network traffic for these hosts?

        What kind of connection does the switch have to the router?

        KyleK 1 Reply Last reply Reply Quote 0
        • KyleK
          Kyle @Dashrender
          last edited by

          @dashrender said in Hyper-V Failover Cluster FAILURE(S):

          Is there a single switch that handles all traffic for SAN(storage traffic) and failover and network traffic for these hosts?

          What kind of connection does the switch have to the router?

          Due to a huge web of issues I couldn't tell you exactly how everything is connected but I do know the Servers and SAN's are on their own switches and then handed off to the LAN.

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • DashrenderD
            Dashrender
            last edited by

            @scottalanmiller how critical, and if not critical - then recommended, is having SAN traffic on it's own switches, not shared with anything else?

            scottalanmillerS KyleK 2 Replies Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller @Dashrender
              last edited by

              @dashrender said in Hyper-V Failover Cluster FAILURE(S):

              @scottalanmiller how critical, and if not critical - then recommended, is having SAN traffic on it's own switches, not shared with anything else?

              Pretty critical. there is a reason that no one would ever try it any other way. SANs need low latency and you dont' want it waiting on a busy backplane. Also, a switch that is good for SAN is not good for the LAN and vice versa. So it wouldn't be cost effective to mix them anyway. Hence, it never comes up. No upsides, loads of downsides.

              DashrenderD 1 Reply Last reply Reply Quote 1
              • scottalanmillerS
                scottalanmiller @Kyle
                last edited by

                @kyle said in Hyper-V Failover Cluster FAILURE(S):

                @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                Is there a single switch that handles all traffic for SAN(storage traffic) and failover and network traffic for these hosts?

                What kind of connection does the switch have to the router?

                Due to a huge web of issues I couldn't tell you exactly how everything is connected but I do know the Servers and SAN's are on their own switches and then handed off to the LAN.

                Handed off to the LAN? SAN traffic never goes on a LAN, ever. If it does, it means you have no SAN and just black storage traffic on the LAN. The whole point of a SAN is that it is completely isolated and doesn't intermingle with the LAN.

                1 Reply Last reply Reply Quote 0
                • KyleK
                  Kyle @Dashrender
                  last edited by

                  @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                  @scottalanmiller how critical, and if not critical - then recommended, is having SAN traffic on it's own switches, not shared with anything else?

                  I believe they did it to connect the 2 SAN's and 1 Datto that are connect via iSCSI on 10G connections and then the Hyper-V is handing traffic off to the LAN for everything else.

                  DashrenderD 1 Reply Last reply Reply Quote 0
                  • DashrenderD
                    Dashrender @Kyle
                    last edited by

                    @kyle said in Hyper-V Failover Cluster FAILURE(S):

                    @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                    @scottalanmiller how critical, and if not critical - then recommended, is having SAN traffic on it's own switches, not shared with anything else?

                    I believe they did it to connect the 2 SAN's and 1 Datto that are connect via iSCSI on 10G connections and then the Hyper-V is handing traffic off to the LAN for everything else.

                    Those two SANs and the DATTO should be on their own switches that have no connections to the rest of the network.

                    I've read about people bitching that they have to have another control station to manage this mini network, but it's the cost of using SAN.

                    KyleK 1 Reply Last reply Reply Quote 1
                    • KyleK
                      Kyle @Dashrender
                      last edited by

                      @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                      @kyle said in Hyper-V Failover Cluster FAILURE(S):

                      @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                      @scottalanmiller how critical, and if not critical - then recommended, is having SAN traffic on it's own switches, not shared with anything else?

                      I believe they did it to connect the 2 SAN's and 1 Datto that are connect via iSCSI on 10G connections and then the Hyper-V is handing traffic off to the LAN for everything else.

                      Those two SANs and the DATTO should be on their own switches that have no connections to the rest of the network.

                      I've read about people bitching that they have to have another control station to manage this mini network, but it's the cost of using SAN.

                      The 172.20 is the servers & SAN. 172.30 is the internal network.

                      DashrenderD 1 Reply Last reply Reply Quote 0
                      • DashrenderD
                        Dashrender @scottalanmiller
                        last edited by

                        @scottalanmiller said in Hyper-V Failover Cluster FAILURE(S):

                        @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                        @scottalanmiller how critical, and if not critical - then recommended, is having SAN traffic on it's own switches, not shared with anything else?

                        Pretty critical. there is a reason that no one would ever try it any other way. SANs need low latency and you dont' want it waiting on a busy backplane. Also, a switch that is good for SAN is not good for the LAN and vice versa. So it wouldn't be cost effective to mix them anyway. Hence, it never comes up. No upsides, loads of downsides.

                        I assumed this to be the case, but haven't dug into it.

                        1 Reply Last reply Reply Quote 0
                        • DashrenderD
                          Dashrender @Kyle
                          last edited by

                          @kyle said in Hyper-V Failover Cluster FAILURE(S):

                          @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                          @kyle said in Hyper-V Failover Cluster FAILURE(S):

                          @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                          @scottalanmiller how critical, and if not critical - then recommended, is having SAN traffic on it's own switches, not shared with anything else?

                          I believe they did it to connect the 2 SAN's and 1 Datto that are connect via iSCSI on 10G connections and then the Hyper-V is handing traffic off to the LAN for everything else.

                          Those two SANs and the DATTO should be on their own switches that have no connections to the rest of the network.

                          I've read about people bitching that they have to have another control station to manage this mini network, but it's the cost of using SAN.

                          The 172.20 is the servers & SAN. 172.30 is the internal network.

                          This isn't really informational. What's important is to know, if there are any switches that have traffic for both 172.20.x.x and 172.30.x.x on them. If yes, that's one of the first things to change.

                          KyleK 1 Reply Last reply Reply Quote 0
                          • ObsolesceO
                            Obsolesce
                            last edited by

                            If the only thing that changed was the IP addressing of (your nodes?), then it may be a DNS related issue. Check all of your cluster related DNS/IP.

                            DashrenderD 1 Reply Last reply Reply Quote 0
                            • DashrenderD
                              Dashrender @Obsolesce
                              last edited by

                              @tim_g said in Hyper-V Failover Cluster FAILURE(S):

                              If the only thing that changed was the IP addressing of (your nodes?), then it may be a DNS related issue. Check all of your cluster related DNS/IP.

                              eh? You would expect DNS to be in use on the SAN network?

                              ObsolesceO 1 Reply Last reply Reply Quote 1
                              • KyleK
                                Kyle @Dashrender
                                last edited by

                                @dashrender the 172.20 addresses are accessible from the 172.30 block.

                                DashrenderD 1 Reply Last reply Reply Quote 0
                                • DashrenderD
                                  Dashrender
                                  last edited by

                                  why is this thread being wiped out?

                                  1 Reply Last reply Reply Quote 1
                                  • DashrenderD
                                    Dashrender @Kyle
                                    last edited by

                                    @kyle said in Hyper-V Failover Cluster FAILURE(S):

                                    @dashrender the 172.20 addresses are accessible from the 172.30 block.

                                    Why is this necessary?
                                    What network is the DATTO on?

                                    1 Reply Last reply Reply Quote 0
                                    • ObsolesceO
                                      Obsolesce @Dashrender
                                      last edited by

                                      @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                                      @tim_g said in Hyper-V Failover Cluster FAILURE(S):

                                      If the only thing that changed was the IP addressing of (your nodes?), then it may be a DNS related issue. Check all of your cluster related DNS/IP.

                                      eh? You would expect DNS to be in use on the SAN network?

                                      Obviously not, I re-read, and missed that bit about the error being specific to the SAN.

                                      This means there's a communication interruption (most likely) between a node(s) and the CSV, which is on the SAN.

                                      Are there any more related errors or is there any additional error info to go by?

                                      KyleK 2 Replies Last reply Reply Quote 0
                                      • KyleK
                                        Kyle @Obsolesce
                                        last edited by

                                        @tim_g said in Hyper-V Failover Cluster FAILURE(S):

                                        @dashrender said in Hyper-V Failover Cluster FAILURE(S):

                                        @tim_g said in Hyper-V Failover Cluster FAILURE(S):

                                        If the only thing that changed was the IP addressing of (your nodes?), then it may be a DNS related issue. Check all of your cluster related DNS/IP.

                                        eh? You would expect DNS to be in use on the SAN network?

                                        Obviously not, I re-read, and missed that bit about the error being specific to the SAN.

                                        This means there's a communication interruption (most likely) between a node(s) and the CSV, which is on the SAN.

                                        Are there any more related errors or is there any additional error info to go by?

                                        I'll post the logs when I get back to the house. A typical 5142 and a few others referencing the inability for the VM's not being able to contact the CSV.

                                        1 Reply Last reply Reply Quote 0
                                        • KyleK
                                          Kyle @Obsolesce
                                          last edited by

                                          @tim_g

                                          Error,10/11/2017 1:26:43 PM,Ntfs,55,None,"A corruption was discovered in the file system structure on volume \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}.

                                          The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.
                                          "
                                          Warning,10/11/2017 1:26:43 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: ??, DeviceName: .
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:43 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: ??, DeviceName: .
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Error,10/11/2017 1:26:43 PM,Ntfs,55,None,"A corruption was discovered in the file system structure on volume \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}.

                                          The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.
                                          "
                                          Warning,10/11/2017 1:26:43 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: ??, DeviceName: .
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:43 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: ??, DeviceName: .
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:43 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: ??, DeviceName: .
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:43 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: Quorum, DeviceName: \Device\HarddiskVolume15.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:43 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: Quorum, DeviceName: \Device\HarddiskVolume15.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:42 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: ??, DeviceName: .
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:42 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: ??, DeviceName: .
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:39 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Information,10/11/2017 1:26:35 PM,Application Popup,26,None,Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x000007FFDA197438 0x000007FFDA197438 0x000007FFDA197438 0x000007FFDA197438
                                          Warning,10/11/2017 1:26:35 PM,Ntfs,50,None,{Delayed Write Failed} Windows was unable to save all the data for the file \Cluster\0.hive. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
                                          Warning,10/11/2017 1:26:34 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}, DeviceName: \Device\HarddiskVolume8.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:34 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}, DeviceName: \Device\HarddiskVolume8.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:34 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}, DeviceName: \Device\HarddiskVolume8.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:34 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}, DeviceName: \Device\HarddiskVolume8.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:34 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}, DeviceName: \Device\HarddiskVolume8.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:33 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}, DeviceName: \Device\HarddiskVolume8.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:33 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}, DeviceName: \Device\HarddiskVolume8.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Error,10/11/2017 1:26:33 PM,Microsoft-Windows-FailoverClustering,1069,Resource Control Manager,"Cluster resource 'Tegile Quorum Drive' of type 'Physical Disk' in clustered role 'Cluster Group' failed.

                                          Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet."
                                          Error,10/11/2017 1:26:33 PM,Microsoft-Windows-Kernel-General,6,None,An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): ''.
                                          Warning,10/11/2017 1:26:33 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}, DeviceName: \Device\HarddiskVolume8.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:33 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{efbdae12-b4db-11e3-9409-f992ab11bd5e}, DeviceName: \Device\HarddiskVolume8.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:33 PM,Microsoft-Windows-FailoverClustering,1558,Quorum Manager,The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
                                          Error,10/11/2017 1:26:32 PM,Microsoft-Windows-FailoverClustering,1557,Quorum Manager,Cluster service failed to update the cluster configuration data on the witness resource. Please ensure that the witness resource is online and accessible.
                                          Warning,10/11/2017 1:26:30 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:30 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Error,10/11/2017 1:26:29 PM,Microsoft-Windows-FailoverClustering,5142,Cluster Shared Volume,Cluster Shared Volume 'Volume1' ('Tegile CSV3 Volume 3') is no longer accessible from this cluster node because of error 'ERROR_TIMEOUT(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Error,10/11/2017 1:26:29 PM,Microsoft-Windows-FailoverClustering,5142,Cluster Shared Volume,Cluster Shared Volume 'Volume1' ('Tegile CSV3 Volume 3') is no longer accessible from this cluster node because of error 'ERROR_TIMEOUT(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:29 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:28 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:27 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:25 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:25 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:25 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:25 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:25 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Warning,10/11/2017 1:26:25 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Error,10/11/2017 1:26:25 PM,Microsoft-Windows-FailoverClustering,5120,Cluster Shared Volume,Cluster Shared Volume 'Volume1' ('Tegile CSV3 Volume 3') is no longer available on this node because of 'STATUS_DEVICE_BUSY(80000011)'. All I/O will temporarily be queued until a path to the volume is reestablished.
                                          Warning,10/11/2017 1:26:25 PM,Microsoft-Windows-Ntfs,140,None,"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: CSV3, DeviceName: \Device\HarddiskVolume14.
                                          ({Device Busy}
                                          The device is currently busy.)"
                                          Information,10/11/2017 1:26:25 PM,iScsiPrt,34,None,"A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name."
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,7,None,The initiator could not send an iSCSI PDU. Error status is given in the dump data.
                                          Error,10/11/2017 1:26:25 PM,iScsiPrt,20,None,Connection to the target was lost. The initiator will attempt to retry the connection.

                                          1 Reply Last reply Reply Quote 0
                                          • DashrenderD
                                            Dashrender
                                            last edited by

                                            Error,10/11/2017 1:26:32 PM,Microsoft-Windows-FailoverClustering,1557,Quorum Manager,Cluster service failed to update the cluster configuration data on the witness resource. Please ensure that the witness resource is online and accessible.

                                            The Witness uses it's own NIC right? If the Witness isn't working correctly, I'm guessing the switch is the root of the issue, but only a guess.

                                            No logs on the SAN showing anything wrong?

                                            KyleK 3 Replies Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 6
                                            • 7
                                            • 5 / 7
                                            • First post
                                              Last post