Windows Server: How to Repair the Boot Files in Windows Server 2008 or 2008 R2 if the Server Won’t Boot

There are a number of possible causes for the failure of a server to boot into Windows. This article deals with a problem in the boot files and demonstrates how to repair them.
Solution
IMPORTANT: Drive Letters Change in WinRE
When booting to the Windows Recovery Environment (WinRE), the drive letters are assigned on a first-come, first-serve basis. For example, the C: drive in Windows will often have a different letter in WinRE. The DiskPart utility can be used to keep track of the drives and what is stored on them.
Restoring Boot Files
 Note: If there is no System Reserved partition. It is okay to select the drive containing the Windows folder .
  • First Partition: 100 MB System Reserved (No drive letter)
  • Second Partition: 60 GB (C:) OS
  • Third Partition:1.5 TB (D:) Data
  • DVD Drive: E:
 Note: The DVD drive’s letter changes from E: to F: in WinRE.
  1. Boot to the Windows Server DVD.
  2. Open the command prompt.
  3. Server 2008 R2
  4. If no driver is needed, press Shift-F10 to open the command prompt.
  5. Continue with step 3.
  6. Server 2008 (or 2008 R2 if a driver is required)
  7. Click Next at the first screen.
Click Repair your computer.
iii. If no driver is needed, click Next and proceed to step vii below.
If a driver is needed, click Load Drivers.
  1. Insert the media containing the needed driver.
Note: The media can be a CD, DVD, or USB storage device
  1. Navigate to the folder containing the driver, select it, and click Open.
vii. Click Command Prompt.
  1. The command prompt appears.
Set the partition as active
4.Type DiskPart at the command prompt.
  1. Type List vol at the DiskPart prompt.
  2. Write down the drive letter of the DVD drive. In this example, it is F.
  3. Write down the drive letter of the system reserved drive. In this example, it is C.
  4. Type Select vol 1 (assuming volume 1 is the System Reserved volume, as it is here).
  5. Type active. This sets the selected volume as active.
  6. Type exit to return to the command line.
Copy Boot Manager
IMPORTANT: Replace the following example drive letters with the actual drive letters obtained in steps 5 and 6 above.
  1. Type Copy f:\BootMgr c:\ at the command prompt. One of two things will happen:
  2. If the file Bootmgr already exists on C:, type N to avoid overwriting it.
  3. If the file Bootmgr doesn’t already exist on C:, it will be copied.
BootRec /FixMBR
  1. Type Bootrec /Fixmbr at the command prompt.
BootRec /Fixboot
  1. Type Bootrec /Fixboot at the command prompt.
Bootrec /rebuildBCD
14.Type Bootrec /rebuildBCD at the command prompt.
  1. If no OS is found, the following appears:
This means that one of the following is true:
* The boot configuration database (BCD) already exists.
* The OS is not there.
* The OS is damaged beyond the ability of BootRec to recognize it.
  1. If BootRec /RebuildBCD succeeds, it will list any installations of Windows that it found. Press Y to accept and add them to the BCD.
The server is now configured to boot from the proper partition. Close the command prompt and reboot the system into normal mode.
Above method cab be also performed through the MS DART CD/ISO.
  • DaRT 8.1 – Windows 8.1, Windows Server 2012 R2
  • DaRT 8.0 – Windows 8, Windows Server 2012
  • DaRT 7.0 – Windows 7, Windows Server 2008 R2
  • DaRT 6.5 – Windows 7, Windows Server 2008 R2
  • DaRT 6.0 – Windows Vista, Windows Server 2008

Comments

Post a Comment

Popular posts from this blog

Siem architecture

What is SIEM?   Security Information and Event Management solutions are a combination of the formerly disparate product categories of SIM (security information management) and SEM   (security event management). SIEM technology provides real-time analysis of security alerts generated by network hardware and applications. The objective: To help companies respond to attacks faster and organize mountains of log data. Security Information and Event Management (SIEM) technologies take part in a crucial role in addressing the compliance, efficiency, and security needs of an enterprise. The central part of SIEM technologies is the ability to collect security data from all the critical assets on a network and present that data as actionable information via a single interface. SIEM solutions come as software, appliances, or managed services. Increasingly, SIEM solutions are being used to log security data and generate reports for compliance purposes.     SIEM S...
Read more

ESXI REMOVE ALL SNAPSHOTS HANGS AT 99%

Image
Check and make sure that the process is actually stuck and not just taking a very long time. To do this, follow these steps: 1. Make sure SSH service is running on the ESXi host Navigate to configuration -> security profile -> services -> Click on Properties Choose the ‘SSH’ service, ‘Options’, and click ‘Start’ Once SSH is enabled, connect to the ESXi host using your favorite ssh client. 2. Run ->   vim - cmd  vmsvc / getallvms Find the vmid of the virtual machine, in this case its 20. 3. Now run ->   vim - cmd  vmsvc / get . tasklist   20 <-   this is the # of the vm from above 4. Find the removeallsnapshots task # then run: vim - cmd  vimsvc / task _ info   185720854  <- this # will be different for you If you see:   “The object has already been deleted or has not been completely created”  or similar, your snapshot removal is probably frozen, but in order to be sure, let’s loo...
Read more

SharesFacebookTwitterGoogle+PinterestEmailSumoMe VMware ESX – “Unable to access a file since it is locked

Image
After transferring and/or trying to restart a VM in ESX you may be presented with the error message “Unable to access a file since it is locked”. Now what you need to do is work out what is actually locking this file and then (unsurprisingly) find a way to unlock it. Generally the problem will be caused by one of three things. 1.  Process Lock:  There is a process on the ESX server that still has hold of a file(s) used by the VM.  This is one of the most common causes.  To resolve this there have been a couple of good VMware Forum postings  here  and  here  that have been consolidated to  this useful posting over  at  GabesVirtualWorld.com   (*Note: It is worth checking out the comment by Kent at the bottom of the posting).  Also, check out Tecumseh’s posting  here . 2.  Disk Naming Conflict:  Two or more disks with the same VMDK name. This can be caused by another disk with the same VMDK file name...
Read more