Windows Server 2008 R2 VM won't boot

Jon Scriven
Jon Scriven used Ask the Experts™
on
Hi,

This all started when I added an additional disk to a vm.

The disk I added didn't show up in Disk Management and so I gave the server a reboot and that was where the nightmare began!  I got a blue screen:-

BSOD
Windows went into recovery mode.

I rebooted and removed the disk in vmware.  Same message.

I then ran DISKPART and for some reason the System Reserved disk shows as drive C and the Windows disk shows as drive D. (normally they are the other way round).  Wasn't sure why this happened as I am not really famililar with how the System Reserved disk works when you are booted into repair mode.

I have tried all sorts of things in DISKPART.  Setting drives as ACTIVE and INACTIVE.  Changing the drive letters around (between C and D) and rebooting, but hasn't made any difference.

I have ran Startup and Repair (startrep.exe) which said it was resolving a problem the first time round, but hasn't seen a problem since.

I have also tried a bootrec /fixmbr and this has not resolved the problem either.

Now I am not sure how best to proceed.  All the data appears to be intact, so I am loathe to do a rebuild, but I can't work out what is wrong with this picture.

Any ideas anyone?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
have you check the SCSI order of disks?

temporarily removed the new disk to test
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
New disk is removed currently.  How do I check the SCSI order?
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
(remember these are virtual disks too)
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
check the VM settings, disk
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
As far as I can see is is SCSI 0:0 which includes both the system reserved and the windows drive.  This did not change.  The disk I added was SCSI 0:4 (there are already 1, 2 and 3 too).  That has been removed now.

Should the Windows or the System Reserved be set as Active?

Should the drive letters change when it is in repair/recovery mode?
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
No - happy to try that, but want to be sure the drives are set correctly before I do.....
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
Second link should help with that (our messages crossed).  I think I have already tried that, but will try again and then run the System File Checker through.
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
OK - I have gone through the second link (which had conflicting information from other links I had seen - so not sure which is correct....).

Got the same blue screen after all of that.

One interesting thing was that after I ran the:-

Bootrec /rebuildbcd

I got the message Total identified windows installations 0

This led me to a couple of threads which I am looking at which might have more information. (see below) - First i'll try the SFC though....

http://social.technet.microsoft.com/Forums/en-US/itprovistadeployment/thread/8647c865-59a2-44dc-8be2-1a65731bbe38

http://www.networksteve.com/forum/topic.php?TopicId=15906
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
Just kicked that off running which will probably take some time.

I noticed a couple of extra bootrec switches in the link I posted which I will also try if the sfc doesn't work.
Jon ScrivenSenior IT Infrastructure Officer
Commented:
After a horrific 4 hours, things are working again!  Don't think I will try adding the drive again tonight.  Thanks for your help.

Solution was:-

http://preempalverec.blogspot.com/2011/12/windows-2008-r2-shows-inaccessible-boot.html 

combined with method 2:-

http://social.technet.microsoft.com/Forums/en-US/itprovistadeployment/thread/8647c865-59a2-44dc-8be2-1a65731bbe38

then

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/b58e67c8-2928-4d1d-8460-81b383f5f48f

Thanks for all your help!
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
I've requested that this question be closed as follows:

Accepted answer: 250 points for brwwiggins's comment #37999048
Assisted answer: 250 points for brwwiggins's comment #37999041
Assisted answer: 0 points for scriven_j's comment #37999339

for the following reason:

There were a couple of extra bootrec switches needed
Jon ScrivenSenior IT Infrastructure Officer
Commented:
Thought I would just add this link to another problem I have which seems to have been related to this initial problem and might be helpful to others who have similar issues.

http://www.experts-exchange.com/Software/VMWare/Q_27731136.html
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
The problem was not totally resolved as I had a knock on problem which I have added a link to.  I would like to include this as part of the assisted solution too.
Jon ScrivenSenior IT Infrastructure Officer

Author

Commented:
There was a knock on problem meaning that the added drive still wasn't recognised by the Guest OS.  Have added a link to that solution.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial