These reboots can cause virtual machines to become corrupt, if the reboot happens in a major write operation.
Now a week ago the server rebooted again unexpectedly and because of this my Lync Server would no longer boot up. I tried repairing the machine using SFC tool with the known syntax:
[Code]
SFC /ScanNow /OffBootDir C: /OffWinDir C:\Windows
[/Code]
It can happen that following message appears:
"There is a Windows Repair pending which requires a reboot of the system"
If this message apears, you can revert the pending changes, or remove/rename the pending.xml file.
To revert the pending change, use following code:
[Code]
dism.exe /image:C:\ /cleanup-image /revertpendingactions
[/Code]
Rename the pending.xml, which is found under C;\Windows\System32.
But after the reboot the system wouldn't boot. The next step would be to repair the Windows boot loader using StartRep.exe
Started the system in repair modus (CMD), where the systems start in X:\Windows\System32
type X\Resources\Recovery\StartRep.exe and press enter. The system asks you if you wish to repair the system boot loader, where you click Finnish. After clicking finish the system restarted perfectly into Windows, even all Lync services where started as intended.
Rename the pending.xml, which is found under C;\Windows\System32.
But after the reboot the system wouldn't boot. The next step would be to repair the Windows boot loader using StartRep.exe
Started the system in repair modus (CMD), where the systems start in X:\Windows\System32
type X\Resources\Recovery\StartRep.exe and press enter. The system asks you if you wish to repair the system boot loader, where you click Finnish. After clicking finish the system restarted perfectly into Windows, even all Lync services where started as intended.
No comments:
Post a Comment