System Boot Problems after True Image Backup
Hello all,
for a few days I installed and configured an new Server in my environment.
Details:
OS: Windows Server 2008 R2
with Software Raid1(mirroring)
Today i wanted to backup my server. I started the bootable media that I have created with the wizzard from Acronis True Image and tried to backup my hard drives.
But at the beginning an error comes up that Acronis can not handle all shown partitions. It seems that Acronis do have some problems with mirrored dynamic partitions.
Ok so i stopped here the way and wanted to boot up my server to use the internal backup function from w2k8 R2 but now my server do not startup anymore!!!
I get the following error:
"Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your windows installation disc and restart your computer.
2. Choose your language settings and click "Next."
3. Click "repair your computer."#
Status: 0xc000000e
Info: The boot selection failed because a required device is inaccessible"
Any ideas what i can do now?
Best regards,
Crus
Crus:
Boot the server from the Server 2008 installation CD to repair the installation. Choose the Automatic Repair function.
From the error message text that you posted, it sounds like the Boot Configuration Database (BCD) needs to be repaired to point to the proper location of the partitions. Your server installation and data should still be okay.
Hello Mark,
thanks for your answer.
You are in right. The data are still okay and I also think that there is something wrong with the boot configuration. I found some Threads in other communitys (Forum) where people have made the same expierence! It seems that TI is chaning something on the partitions or so.
Sorry, I forgot to say that i still tried to open the Recovery Console (repair computer) but i cannot pick up my opperating system from the list. (it is not listed) So I am not able to start the WinRe. (Windows Recovery Environment)
That is really a problem!
Any more ideas?
Best regards,
Crus
Crus:
If you are booting the server from the Server 2008 installation DVD you should still be able to start WinRE without your operating system appearing in the list. Keep proceeding until you get past that dialog box to the dialog that lets you repair the computer. See Figure 9 in this tutorial (it is written for Vista, but Server 2008 and Windows 7 are similar).
hello again,
thanks for your answer.
Ok, I ignored that my operating system is not listed and went through this dialog. But it seems that the installation-dvd from w2k8 r2 has not so much tools onboard in the WinRe as the vista installation-dvd. I can only choose between the following options:
- System Image Recovery
- Windows Memory Diagnostics
- Command Prompt
Over the command prompt I can switch to the folder: 'X:\sources\recovery' and here I was able to find a executable file called: 'startrep.exe'.
But this tool can´t fix the problem for me. At the beginning you can short see a message: 'Reparing disk errors. This might take over an hour to complete.' But after a few seconds an error comes up that Startup Repair cannot repar this computer automatically.
Between the start and the error you can also see that there is no hard-disk action. I think if the system not listed then you will not have access to the drive?
Crus:
I can try to help you repair the BCD manually from a command prompt.
First, boot to the command prompt and find out the drive letters of all of the partitions on your server's disk. Do the following:
C:
dir
D:
dir
...etc...
Make a note of which drive letter belongs to each partition on the disk, and especially which drive letter belongs to the main Server 2008 partition. Then type bcdedit and examine the output. Here is an example of what you might see:
Windows Boot Manager
--------------------
identifier {bootmgr}
device boot
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {9ba97b5b-251e-11dd-abc2-e9e6d4590921}
displayorder {current}
{df0009f9-a8ef-11dd-bfbd-0019dbda2159}
toolsdisplayorder {memdiag}
timeout 5
resume NoWindows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {9ba97b5b-251e-11dd-abc2-e9e6d4590921}
nx OptIn
Check the output listed next to each device entry. Do any of them say unknown? If so, which ones?
Hi Mark,
thanks for your tips.
I tried now many different ways to get access to my 'C' drive with the command prompt and now I was able to access my it (F:) drive.
I changed the information in the 'boot loader' and now my server is starting up again.
But I got one other problem now after the restart:
The Virtual Disk Service (Disk management) is not longer working!!!
If I try to start the service manually I get the following error:
Windows could not start the Virtual Disk service on local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
Any ideas on this?
Crus:
Now that you have the server booting again, try the automatic repair again to see if it will now work. It may correct this issue.
I suspect that if your BCD pointers were incorrect, probably the Disk ID changed. You may also want to check the following items:
- System Restore settings
- Windows Search settings
- Automatic Disk Defragmenter settings
If the disk ID changed, the internal pointers to these items may also have changed. You can reset them by re-selecting them in the appropriate areas of the control panel.
Hi,
sorry, i forgot to say that I already did a startup repair after the successful boot.
I tried the following:
1. I did a Shutdown after the successful boot
2. Unpluged the second hard drive (mirror)
3. Changed the BCD Settings (rebuilded)
4. Did an startup-repair
5. startet windows normaly
And now the service is still not working!
EDIT:
O.K i have noticed that other tools like 'Credential Manager' and so also not working...
So maybe I do only have one chance: completely re-install?
Crus:
All of the symptoms that you describe sound like what happens when the Disk ID changes. Windows references the Disk ID for many functions; assigning drive letters, identifying partitions, identifying pointers in the BCD, etc. If you had any idea of what the Disk ID was when the server was working, you could change it back with a Disk Editor. However, to find this out you would need to refer to a backup of the first sector on the disk (the MBR), or a backup of the registry, so if you don't have any of these then it may be easier at this point to just reinstall.
I think I understand what happened, but not why it happened. Booting from the Acronis boot CD should not be causing changes to the MBR of the disk.
Hi Mark,
at the moment I do not have any copies of the files you named. Because this acronis backup was my first backup try. And I also don´t know the Device ID before the crash happened.
In regards of that many 'malfunctions' I really think an re-installation should be better.
At this point I will say many, many thanks to you for your really good help.
Best regards,
Crus
Crus:
Sorry that it didn't turn out better. I wish I knew what happened!
Mark,
I wonder if the MBR repair function changed the disk signature. I've never done any testing on this, but depending on what it detects it may determine if it just fixes the code or if it resets it completely.
Paul:
Could be. But I always thought that all of the MBR fixing utilities only changed the 446 byte boot loader code in the MBR without touching the Disk Signature or the partition table.
Same issue resolved same way, 2 years down the road with issue still existing in Windows 8 apparently.
I restored W7 x64 Ultimate located on Raid 1 pair of disks from an Acronis TI 2013 .tib (2013 April) using the Acronis loader (CD). All fine. 3 restores: 1) the c: partition, 2) the system reserve partition, 3) the MBR.
This restore was prompted by a mess created by Office 2010 SP2 update, nothing else (no hardware problem and stable system).
Just to share & add a question / suggestion:
At reboot, very similar error code 0xc000000e and text except, in addition I got, "File:\Windows\system32\winloader.exe" with application corrupt or missing.
I knew about this quite misleading error message, and about fragility of bcd, so I did not worry as much as I did the previous time (about 2 years ago).
I installed my Windows Repair disc, which repaired the BCD.
A relief as, probably by my error of configuration, I had put this C:\ drive on an Intel Raid 1 volume, which makes taking out and putting 2 drives in another system just a bit more difficult (need two free sata spots on Intel controller). Then, it should be easier to run bcdedit (command mode) in repair mode on the recognised Raid 1 volume (not tried).
Question:
why Acronis can't structure the Acronis back up & restore (from CD or from W7) to avoid to need a Windows repair disc (bcdedit function) to boot at start up? I find this pretty serious.
I discovered that Acronis TI is described still today in Forums as not being able to handle this problem since Vista.
Perhaps this issue is not due primarily to Acronis but to Microsoft, but it is worth pointing out in bold and Worth guiding clients better in those annoying circumstances. Also, Acronis could integrate the bcdedit repair function on their CD? That would be great and reassuring.
acontrario
Brussels