Link to home
Create AccountLog in
Avatar of Jon Scriven
Jon ScrivenFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Windows Server 2008 R2 VM won't boot

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:-

User generated image
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?
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

have you check the SCSI order of disks?

temporarily removed the new disk to test
Avatar of Jon Scriven

ASKER

New disk is removed currently.  How do I check the SCSI order?
(remember these are virtual disks too)
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?
SOLUTION
Avatar of brwwiggins
brwwiggins
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
No - happy to try that, but want to be sure the drives are set correctly before I do.....
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.
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
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.
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
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
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
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.
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.