Config is a WHS2011 (WS2008R2 derivative) on Intel UEFI-capable desktop board. I had a working configuration for a long time but for reasons beyond the discussion here, ended up re-installing it. Since WHS doesn't allow selecting where the OS
installs, first I removed the two RAID disks, expecting to be able to add them in later.
I installed it as a one disk system and it booted fine. When I added back in the two disks as Intel RAID, they are apparently now recognized as the first two disks and are where the EFI stuff wants to boot to and that fails and falls through to the
network boot agent. If I F10 and select the EFI hard disk option, it boots fine. If I F10 and select Windows Boot Manager it also fails. My thinking is that somehow the NVRAM and EFI data are not consistent with the "new" collection of disks, but don't
really know the EFI boot process well enough to prove it and find the specific problem.
I've read up on bcdedit and it looks like all of that mucks about in the relevant area, but I'm hesitant to go in and just hack since I don't want to brick the machine for the second time in a week.
Any suggestions where to begin on this would be greatly appreciated!
I almost didn't mention WHS since this problem is pretty much a WS2008R2 boot design issue; other than not allowing the initial install to occur on an arbitrary storage device, there is nothing unique to WHS here. I figured people who frequent this forum
might spend more time mucking in areas like the BCD.
From a WHS2011 BCD:
Windows Boot Loader
description Windows Server 2008 R2
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.