failover cluster corrupts virtual machines

%3CLINGO-SUB%20id%3D%22lingo-sub-1359619%22%20slang%3D%22en-US%22%3Efailover%20cluster%20corrupts%20virtual%20machines%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1359619%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20all%2C%20i'm%20facing%20a%20strange%20situation%2C%20my%20servers%20are%20corrupting%20the%20VMs%20and%20I%20don't%20know%20why.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%202-NODE%20ready%20to%20build%20a%20fail-over%20cluster%20but%20with%20some%20other%20bugs%20(the%20validation%20cluster%20is%20tno%20completing%20succefully)%20but%20this%20is%20another%20topic.%20I%20have%20both%20servers%20not%20clustered%20connected%20via%20iSCSI%20to%20a%20Storage%20where%20all%20the%20VMs%20a%20stored.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20know%20why%20but%20suddenly%20the%20VMs%20just%20shows%20save-critical%20when%20I%20go%20the%20see%20the%20VMs%20they%20are%20corrupt.%20Can%20someone%20tell%20me%20what%20could%20be%20the%20problem%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20running%20Windows%20Server%202016%2C%20servers%20all%20patches%2C%20Huawei%20support%20says%20that%20there%20is%20OS%20issues%20I%20should%20contact%20them%20and%20I'm%20driving%20crazy.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20windows%20event%20view%20i%20got%20this%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-basic%22%3E%3CCODE%3E%23%23%23%23%23%23%23%23%23%20NTFS%20%23%23%23%23%23%23%23%23%23%23%23%0A%0AA%20corruption%20was%20discovered%20in%20the%20file%20system%20structure%20on%20volume%20F%3A.%0A%0AA%20corruption%20was%20found%20in%20a%20file%20system%20index%20structure.%20%20The%20file%20reference%20number%20is%200x9000000000009.%20%20The%20name%20of%20the%20file%20is%20%22%3CUNABLE%20to%3D%22%22%20determine%3D%22%22%20file%3D%22%22%20name%3D%22%22%3E%22.%20%20The%20corrupted%20index%20attribute%20is%20%22%3A%24SII%3A%24INDEX_ROOT%22.%20%20The%20corrupted%20index%20block%20is%20located%20at%20Vcn%200xffffffffffffffff%2C%20Lcn%200xffffffffffffffff.%20%20The%20corruption%20begins%20at%20offset%20496%20within%20the%20index%20block.%3C%2FUNABLE%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eanother%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-basic%22%3E%3CCODE%3EThe%20program%20explorer.exe%20version%2010.0.14393.3241%20stopped%20interacting%20with%20Windows%20and%20was%20closed.%20To%20see%20if%20more%20information%20about%20the%20problem%20is%20available%2C%20check%20the%20problem%20history%20in%20the%20Security%20and%20Maintenance%20control%20panel.%0A%20Process%20ID%3A%201a58%0A%20Start%20Time%3A%2001d622b30c56d07f%0A%20Termination%20Time%3A%200%0A%20Application%20Path%3A%20C%3A%5CWindows%5Cexplorer.exe%0A%20Report%20Id%3A%205693312b-8ea8-11ea-9c66-9418827b869b%0A%20Faulting%20package%20full%20name%3A%20%0A%20Faulting%20package-relative%20application%20ID%3A%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20on%20the%20Hyper-v%20session%20this%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-basic%22%3E%3CCODE%3EFailed%20to%20load%20Hyper-V%20state%20for%20virtual%20machine%20'DC_AD_1'%20from%20the%20configuration%3A%20Unspecified%20error%20(0x80004005).(Virtual%20machine%20ID%200FCE04B7-E74D-4C11-A2AC-9F562E28223A).%20Hyper-V%20may%20not%20work%20properly.%20An%20attempt%20to%20reload%20the%20configuration%20will%20be%20made%20in%20a%20few%20minutes.%0A%0AFailed%20to%20load%20Hyper-V%20state%20for%20virtual%20machine%20'ebr_APP_6'%20from%20the%20configuration%3A%20Unspecified%20error%20(0x80004005).(Virtual%20machine%20ID%209FC8648C-84BF-408D-831A-EF5D763E29F4).%20Hyper-V%20may%20not%20work%20properly.%20An%20attempt%20to%20reload%20the%20configuration%20will%20be%20made%20in%20a%20few%20minutes.%0A%0AFailed%20to%20load%20Hyper-V%20state%20for%20virtual%20machine%20'ebr_db_14'%20from%20the%20configuration%3A%20Unspecified%20error%20(0x80004005).(Virtual%20machine%20ID%20B9AECCD2-8C7F-43CC-B8AC-FAE7AA0E394F).%20Hyper-V%20may%20not%20work%20properly.%20An%20attempt%20to%20reload%20the%20configuration%20will%20be%20made%20in%20a%20few%20minutes.%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3ECheck%20the%20images%20attached%20for%20more%20details.%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3ENelson%20Chamba%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1359619%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EClustering%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1362654%22%20slang%3D%22en-US%22%3ERe%3A%20failover%20cluster%20corrupts%20virtual%20machines%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1362654%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooks%20like%20there%20is%20no%20feedback%2C%20can%20someone%20tell%20me%20if%20there%20is%20any%20data-recovery%20tool%20from%20MS%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Dear all, i'm facing a strange situation, my servers are corrupting the VMs and I don't know why.

 

I have 2-NODE ready to build a fail-over cluster but with some other bugs (the validation cluster is tno completing succefully) but this is another topic. I have both servers not clustered connected via iSCSI to a Storage where all the VMs a stored.

 

I don't know why but suddenly the VMs just shows save-critical when I go the see the VMs they are corrupt. Can someone tell me what could be the problem?

 

I'm running Windows Server 2016, servers all patches, Huawei support says that there is OS issues I should contact them and I'm driving crazy.

 

On windows event view i got this:

######### NTFS ###########

A corruption was discovered in the file system structure on volume F:.

A corruption was found in a file system index structure.  The file reference number is 0x9000000000009.  The name of the file is "<unable to determine file name>".  The corrupted index attribute is ":$SII:$INDEX_ROOT".  The corrupted index block is located at Vcn 0xffffffffffffffff, Lcn 0xffffffffffffffff.  The corruption begins at offset 496 within the index block.

 

another 

The program explorer.exe version 10.0.14393.3241 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 1a58
 Start Time: 01d622b30c56d07f
 Termination Time: 0
 Application Path: C:\Windows\explorer.exe
 Report Id: 5693312b-8ea8-11ea-9c66-9418827b869b
 Faulting package full name: 
 Faulting package-relative application ID:

 

and on the Hyper-v session this:

Failed to load Hyper-V state for virtual machine 'DC_AD_1' from the configuration: Unspecified error (0x80004005).(Virtual machine ID 0FCE04B7-E74D-4C11-A2AC-9F562E28223A). Hyper-V may not work properly. An attempt to reload the configuration will be made in a few minutes.

Failed to load Hyper-V state for virtual machine 'ebr_APP_6' from the configuration: Unspecified error (0x80004005).(Virtual machine ID 9FC8648C-84BF-408D-831A-EF5D763E29F4). Hyper-V may not work properly. An attempt to reload the configuration will be made in a few minutes.

Failed to load Hyper-V state for virtual machine 'ebr_db_14' from the configuration: Unspecified error (0x80004005).(Virtual machine ID B9AECCD2-8C7F-43CC-B8AC-FAE7AA0E394F). Hyper-V may not work properly. An attempt to reload the configuration will be made in a few minutes.

Check the images attached for more details.

Regards,

Nelson Chamba

1 Reply

Hi all,

 

Looks like there is no feedback, can someone tell me if there is any data-recovery tool from MS?