Yesterday Typhoon Day, the company suddenly power off. After the call, start the server, found that some of the virtual machine state is not normal, and some become shutdown-the key
650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/73/FC/ Wkiol1ylmrdtwhn8aaawmcy6exy005.jpg "" 644 "height="/>
Check the hard disk and discover that the disk files are still there. Then, in Hyper-V Manager, remove the virtual machine that has the exception, and then create a new virtual machine that uses the hard disk that was used by the original virtual machine. There are two days the virtual machine can start normally, after entering the system to set the IP is good.
But there is an Exchange server that does not start properly
650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/73/FC/ Wkiol1ylmrcsr2gfaacswxbw4zs418.jpg "" 644 "height=" 147 "/>
From this point of view should be the boot boot has a problem, I would like to be repaired through the system installation disk. Insert the installation image into the virtual machine, boot from the CD,
650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/73/FC/wKioL1YLmrGxrzmwAAE0mn_ Toqc979.jpg "" 644 "height=" 479 "/>
Press SHIFT+F10 to enter the following screen
650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/73/FE/ Wkiom1ylmqacivtbaab2pfevc30114.jpg "" 644 "height=" 215 "/>
Then execute BOOTREC/FIXMBR
Bootrec/fixboot
Bootrec/rebuildbcd
650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/73/FE/ Wkiom1ylmqfcd2wraafnydemggi745.jpg "" 644 "height=" 414 "/>
But this still does not work, from the red box mark can see Rebuildbcd not succeed. From this point of view, I think the system should still be in, but the boot cannot be added normally. So, I loaded this VHD into another virtual machine that can start normally, performing BOOTREC/REBUILDBCD
650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/73/FC/ Wkiol1ylmrpax-4kaaezap2gvpk056.jpg "" 644 "height=" 279 "/>
After the successful addition of the server, the discovery is a dual system, indicating that the load is successful, select a second
650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/73/FE/ Wkiom1ylmqiymaigaac2qod1ste108.jpg "" 644 "height=" 177 "/>
OK, you can enter the system normally.
Repair journey of a Hyper-V 2012R2 virtual machine