luckyluke2
asked on
VMware Windows Server 2008 r2 BSOD 0xc0000225 boot selection failed
Hi everyone,
We have 4 VMware servers (3 x Windows 2003 and 1 x Windows 2008) on an IBM x3400 server, running ESXI 4.1.0
The Windows 2008 r2 server has stopped booting and continually receives a Blue Screen of Death 0xc00007b, when the server restarts and repair is chosen the error is: 0xc0000225, the boot selection failed because a required deivce is inaccessible.
I have tried a repair (startrep) using the Win Server 2008 CD and receive error that cannot be repaired (tried this several times just to be sure). Whilst repairing, I went to the command prompt and can start regedit, can also see the C: drive contents (even though it looks like D: drive, hope that makes sense).
I really don't know what happened, no windows updates have been run, the other servers are ok on the host. This server is primarily used for Backup Exec. My big mistake is after taking over from previous IT person, I have now found this server was not part of VEEAM backup. Of course this server had to fail !!!
Thanks in advance
We have 4 VMware servers (3 x Windows 2003 and 1 x Windows 2008) on an IBM x3400 server, running ESXI 4.1.0
The Windows 2008 r2 server has stopped booting and continually receives a Blue Screen of Death 0xc00007b, when the server restarts and repair is chosen the error is: 0xc0000225, the boot selection failed because a required deivce is inaccessible.
I have tried a repair (startrep) using the Win Server 2008 CD and receive error that cannot be repaired (tried this several times just to be sure). Whilst repairing, I went to the command prompt and can start regedit, can also see the C: drive contents (even though it looks like D: drive, hope that makes sense).
I really don't know what happened, no windows updates have been run, the other servers are ok on the host. This server is primarily used for Backup Exec. My big mistake is after taking over from previous IT person, I have now found this server was not part of VEEAM backup. Of course this server had to fail !!!
Thanks in advance
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
do you have any issues with the datastore?
ASKER
Hi,
As far as I can tell, there is only 1 datastore and as mentioned, the 3 other servers on the host aren't affected. There are 4 x 450GB drives setup as raid 5. All disks are good, no failures.
Are there any VMware datastore checking tools?
Thanks
As far as I can tell, there is only 1 datastore and as mentioned, the 3 other servers on the host aren't affected. There are 4 x 450GB drives setup as raid 5. All disks are good, no failures.
Are there any VMware datastore checking tools?
Thanks
This error normally generated when Disk or Disk size is changed. Try running below commands
1. Boot the machine with Windows Server 2008 DVD
2. Select your language
3. Select repair your computer
4. Run following commands
c:\> cd \windows\system32
> bcdedit /set {bootmgr} device boot
> bcdedit /set {default} device boot
> bcdedit /set {default} osdevice boot
5.Restart
If this doesn't fix the issue, try running chkdsk and check the health of VM disk.
1. Boot the machine with Windows Server 2008 DVD
2. Select your language
3. Select repair your computer
4. Run following commands
c:\> cd \windows\system32
> bcdedit /set {bootmgr} device boot
> bcdedit /set {default} device boot
> bcdedit /set {default} osdevice boot
5.Restart
If this doesn't fix the issue, try running chkdsk and check the health of VM disk.
ASKER
Thanks subhashishlaha, I will try this tomorrow at work. I forgot to mention above that I also did try ckdsk /f and it did not work.
Can you suggest how I check the health of the VM Disk.? As mentioned, I think there is only 1 datastore and 3 other VM servers accessing the same datastore without problem. No failed disks either.
BTW: When I accessed the command prompt today. The C: drive showed "system reserved". I think this may be something to do with the VMWare host, it is D: drive which looks to be the system drive. Even though the server definately only had a C: drive. Hope that makes sense
Thanks
Luke...
Can you suggest how I check the health of the VM Disk.? As mentioned, I think there is only 1 datastore and 3 other VM servers accessing the same datastore without problem. No failed disks either.
BTW: When I accessed the command prompt today. The C: drive showed "system reserved". I think this may be something to do with the VMWare host, it is D: drive which looks to be the system drive. Even though the server definately only had a C: drive. Hope that makes sense
Thanks
Luke...
With VM disk health check I meant running chkdsk. As you mentioned, you already executed it then its not required.
In regards to System reserved partition driver letter i.e. C:, sometimes when you boot in WinPE - it assign drive letter to System reserved partition.
To execute above commands, you can run from X: drive which is WinPE drive or you can go into D:\Windows\system32 which is your System drive.
In regards to System reserved partition driver letter i.e. C:, sometimes when you boot in WinPE - it assign drive letter to System reserved partition.
To execute above commands, you can run from X: drive which is WinPE drive or you can go into D:\Windows\system32 which is your System drive.
ASKER
Hi subhashishlaha,
Unfortunately that didn't fix problem. Still same message.
I have attached screen shot of bcdedit details.
Thanks
server.JPG
Unfortunately that didn't fix problem. Still same message.
I have attached screen shot of bcdedit details.
Thanks
server.JPG
ASKER
Hi,
Can someone tell me how I should reference the device partition as above screen shot. I issued the command
>bcdedit /set {bootmgr} device partition=c:
I am thinking to try something like:
>bcdedit /set {bootmgr} device partition=\Datastore1 (where Datastore1 is our VMware datastore)
Can someone tell me how I should reference the device partition as above screen shot. I issued the command
>bcdedit /set {bootmgr} device partition=c:
I am thinking to try something like:
>bcdedit /set {bootmgr} device partition=\Datastore1 (where Datastore1 is our VMware datastore)
Hello Luke
Try running below command to fix it
bcdedit /set {bootmgr} device partition=\Device\Harddisk
Please refer below screenshot of my test machine having System reserved partition.
You should not set \Datastore1 as partition bcoz this BCD manager is inside VM and it can only see the Disk presented in VM. It will not see the Datastore on which VM resides.
bcd.JPG
Try running below command to fix it
bcdedit /set {bootmgr} device partition=\Device\Harddisk
Please refer below screenshot of my test machine having System reserved partition.
You should not set \Datastore1 as partition bcoz this BCD manager is inside VM and it can only see the Disk presented in VM. It will not see the Datastore on which VM resides.
bcd.JPG
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Suggested solutions were unable to resolve issue, but were helpful in trying all possible fixes before deciding to rebuild server.