OK, I was able to get the machine to boot using this article:
I used Bootrec.exe /rebuildbcd
I'll still award points if anyone has a better way or can provide some insight.
Thank you for this post. I ran into the same issue today when trying to power on a 2008 R2 VM that I had previously attached the hard disk to another machine.
I had to do one extra step, when in the recovery console, the OS wasn't recognized. I had my SCSI controller set to paravirtual, so I changed it to LSI Logic SAS. Then the OS was recognized and I ran the same command:
Still don't know why it happens, I would like to know that as well.
I had the same issue. Turns out 08 volumes (even boot) can be extended thru gui via disk management on same server you are trying to extend! See here - http://support.microsoft.com/kb/325590
Check out - How to extend the boot partition in Windows Server 2008
Wish I knew this 10 minutes ago.
I had the same issue and wish I had known about KB325590 10 minutes ago as well I found and sucessfully used the following KB article http://support.microsoft.com/kb/2261423 to resolve the same issue. It is related more to corruption due to backups, but the error described is exactly the same. After verifying the three settings they talk about, I went with the step 7 option "Or, locate X:\Sources\Recovery, and then run StartRep.exe to start a quick automated startup repair utility that corrects boot environment values."
and it worked without any issues. Thanks for all of your help.
Thank you guys,
got the same issue today. Tried:
this one: VMware KB: Windows 2008 R2 disk volume becomes read-only and fails to boot it didn't work and then:
and got blue screen after reboot. But it let me to choose "Last known good configuration" option, and it finally resolved my problem.
Anyway thanks to everybody who shared his experience with that!
Thanks very much for the information about BOOTREC.exe /rebuildBCD..
This just saved a 2008 box that I blew up, trying to attach the HD to another VM in order to add some space to the C:\ drive.. I thought I read somewhere that would work.. but now that I read the OP's message, perhaps that just worked in 2003, and not 2008 (or 2012).. I just ran the .iso, followed the repair instruction -- and now its back online..
Very glad to have found this article.. !