This is not a dual boot setup.

After adding a second pair of Raptors to a system and enabling RAID 0+1 and running the recovery, that is the error we are getting.

File: \Windows\System32\winload.exe

Status: 0xc000000e

Info: The selected entry could not be loaded because the application is missing or corrupt.

When I try to run the BCDEdit commands found here and on the Internet, I get the following error:

The boot configuration data store could not be opened.

The requested system device could not be found.

Okay folks, what are my next steps please? Thanks.

During the HIR process, what prompts did you receive and for what drivers?  There should be and HIR Logs folder in the root of the system that was restored.  Please send those to support@storagecraft.com

Scott
STC

Scott,

Since nothing changed but the drive setup, I did not HIR. The original setup was RAID 1 so the drivers were already in the OS.

Should I have HIRd?

Because you change your RAID configuration, you would need to use HIR as the drivers may be different.  You do not need to run the entire restore again, since you can run only the HIR part of the process by booting back into the recovery environment and using the HIR Configuration Tool against the restored volume.  Hopefully HIR will have the necessary driver in its driver library, but if not you may need to provide it.  Give it a try and let us know if you continue to have trouble.

-Kevin

I reran the recovery and used HIR with the current drivers via Intel's Web site.

Still the same error. :(

Any word? We are fortunate that the machine in question is not needed ... but we do need to bring it back online!

Philip

Okay, this is a stretch, but what the heck.  Try these steps:

Go back into the recovery environment (assuming you're using a 3.3 ISO), delete all partitions on the target disk (I'm assuming you can do this because you migrated to new disks and so they should have been blank initially anyway so I'm basically just suggesting that you clean the slate).  Then perform the restore again, using HIR, and in the restore wizard disk map page (where you specify the target of the restore) right-click on the disk map list and edit the partition creation policy - specify that you want to SECTOR align the start and SECTOR align the end of newly created partitions.  Then in the same disk map list on the same destination page of the restore wizard, right-click on the empty target disk and specify that you want to create an exact fit partition at the beginning of the disk.  After the partition is created and shows up in the refreshed list, select it and move on with the restore.  Then let us know what happens when you try to boot the newly-restored OS.  I'm basing this experiment on some feedback we got yesterday evening from our partners in Australia which may be related to your specific issue.

I think the issue has to do with incorrect information in your BCD.  Most likely your "device" and "osdevice" values are incorrect and need to be patched to something like "partition=C:".  You could do this by booting the Recommended (vista-based) recovery environment and then use the BCD edit tool from the Tools menu.

Nate,

Been there done that many ways come Sunday. Nothing worked in the way of bcdedit or bootrec commands.

I will try your suggestion above to see if we get anywhere.

Thanks,

Philip

Philip,

In all the cases in which I received the error message:
>>The boot configuration data store could not be opened.
>>The requested system device could not be found.
The solution was directly reference the BCD store file. For me, this problem seemed to come up when trying to boot multiple Vista installations, especially of on Logical partitions.

When you boot to the Vista DVD and start the Command Prompt, find out what drive letter is assigned to your Vista boot partition (it's usually C: ). Then you need to run BCDEDIT and force it to load the correct file:
bcdedit /store c:\boot\bcd

You should be able to see if any of the partition references are incorrect (unknown). If they are, you should be able to fix them by running the necessary commands. For example:
bcdedit /store c:\boot\bcd /set {default} device partition=C:
bcdedit /store c:\boot\bcd /set {default} osdevice partition=C:
bcdedit /store c:\boot\bcd /set {bootmgr} device partition=C:

Tried and failed. Back to square 1: WinLoad error.

Have to rebuild the box I guess.

What's next? Are we going to be seeing this error for other Vista/Win2K8 recovery attempts?

If so, that makes me very nervous. All of a sudden, ShadowProtect is not so reliable anymore?

Philip

MC,

BCDEdit does not work by itself nore in combination with the BootRec command. Nothing seems to do it.

Thanks anyway.