Cant boot Server 2003 after having installed Windows 7

#1
Hello guys

Hope you can help me with this, because I really need to get my Server 2003 running, as that is working platform (need it for my job).

I had three operating systems in my computer: Ubunt, Win XP and Win Server 2003. Grub was the booting program, that offers you go to Windows loader. When I selected this, I could choose between XP and Server 2003, according to XP boot.ini file.

Yesterday I got Windows 7 installed over XP. Everything seemed to be fine. I got back Grub booting with Super Grub. When I boot the computer I choose Windows booting, and now, Windows 7 menu is shown.

First options here were:

- Previous Windows version
- Windows7

Firtst entry did not work: when you select it the computer just hungs up doing nothing, showing nothing, totally black.

I installed EasyBCD and tried to edit boot menu: adding new entry to be autodetected or selecting the drive, but I get just absolutely nothing. When I choose this new entry to be loaded, same result: black screen.

These are my curent booting settings:

There are a total of 3 entries listed in the bootloader.

Default: Windows 7
Timeout: 15 seconds
Boot Drive: C:\

Entry #1
Name: Versi¢n anterior de Windows
BCD ID: {ntldr}
Drive: C:\
Bootloader Path: \ntldr

Entry #2
Name: Windows 7
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe

Entry #3
Name: Server 2003
BCD ID: {18fe5dc2-7e9a-11e0-b4ef-a83f19c151fa}
Drive: D:\
Bootloader Path: \NST\easyldr1
I tried also copying a regular boot.ini file (see below) into the Server 2003 partition, but all I got with this is, instead a black screen, a message saying that system in " \NST\easyldr1" cannot be loaded by some hardware/software error (no more options but to go back)

Code:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect
As said, I am totally desperated with this, I really need my server 2003 getting launched

Any help will be very appreciated!!!

Addendum:

Just in case it helps, here its my partition map. Although it is Spanish, I guess you can read it

The first two are the ubuntu partitions (systema and swap), then C (win7), D (server 2003), and E (data, no system)

 
Last edited:

Terry60

Knows where his towel is.
Staff member
#2
#3
How did you get W7 at the front of the HDD if XP was there first ?
Did you clone XP and move it ?
If so, be aware of problems which cloning XP can bring about
Goodells.Net :: Understanding MultiBooting
Thanks for your interest Terry60

I installed W7 overwritting XP, but withoug formatting that partition (so now I have a big windows.old folder that I have to get rid of)

I made some changes and tests: deleted all entries in the boot except for the W7, and manually created (using bcdedit) the new one, now my settings are like this:

Code:
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.

C:\Windows\system32>bcdedit

Administrador de arranque de Windows
----------------------------------
Identificador           {bootmgr}
device                  boot
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder            {current}
                        {ntldr}
toolsdisplayorder       {memdiag}
timeout                 10

Cargador de arranque de Windows
-----------------------------
Identificador           {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Microsoft Windows 7
locale                  es-ES
osdevice                partition=C:
systemroot              \Windows
resumeobject            {a5607d6c-7efe-11e0-a5f9-806e6f6e6963}
sos                     No
debug                   No

Cargador del SO Windows heredado
--------------------------------------------------
Identificador           {ntldr}
device                  partition=C:
path                    \ntldr
description             Windows Server 2003
But still same result: when I select to run Server 2003, I just get a black screen, nothing else

I could add new entry to grub with server 2003, but because of easybcd , now I have no boot.ini, ntdetect and ntldr files in d: partition, so, unless I got this wroing, It cannot be launched without W7

Any help?
 

Terry60

Knows where his towel is.
Staff member
#4
"...because of easybcd , now I have no boot.ini, ntdetect and ntldr files in d: partition.."
This is nothing to do ith EasyBCD. XP was previously controlling the XP/2k3 dual boot and the boot files were in the partition you overwrote.
Delete the 2k3 entry and add a new one using auto-detect. Easy BCD will create all the necessary files (not in D, but in "system", where they should be)
Don't alter the BCD entry to D. Leave it the way EasyBCD sets it up.
 
#5
"...because of easybcd , now I have no boot.ini, ntdetect and ntldr files in d: partition.."
This is nothing to do ith EasyBCD. XP was previously controlling the XP/2k3 dual boot and the boot files were in the partition you overwrote.
Delete the 2k3 entry and add a new one using auto-detect. Easy BCD will create all the necessary files (not in D, but in "system", where they should be)
Don't alter the BCD entry to D. Leave it the way EasyBCD sets it up.
Hi Terry,

I did what you are saying: delete all entries except the primmary one, and create a new one with autodetect from unit C:, that created what I quoted above:

Code:
Identificador           {ntldr} 
device                  partition=C: 
path                    \ntldr 
description             Windows Server 2003
But this is not working. When I select this entry in the boot menu, screen goes black and does nothing at all
 

Terry60

Knows where his towel is.
Staff member
#6
The path in that BCD entry doesn't look like it's been created by EasyBCD.
What does EasyBCD "view settings" show (detailed mode) ?
 

mqudsi

Mostly Harmless
Staff member
#7
Definitely not an EasyBCD 2.0/2.1 path.
 
#8
Hello guys,

I am back here, with some new tests I did on my computer, let me give you all details to check if you can help me out.

First of all I just checked: I am usinb EasyBCD 2.0.2

STEP 1
Changed file c:\boot.ini to point to a non-existing partition for Server 2003. Result was still black screen. Restored boot.ini to correct partition

STEP 2
Fix Windows booting. I booted from windows 7 installation CD, and it detected there was an issue on booting, and fixed it.
I rebooted, now from hard disk, and when tried to launch Server 2003, no more black screen, but the following:

http://www.technoish.com/wp-content/uploads/2008/08/winload_exe_vista_missing_or_corrupt.jpg

Only difference was File: NTS\ntldr

STEP 3
I again booted from CD, and executed chkdsk d: /f/r
Same error message when tried to boot Windows Server 2003

STEP 4
From CD booting, tried to execute command bootrec.exe /RebuildBcd
No result, returned message:
Total identified Windows installation: 0
I guess this is happening because of Ubuntu and grub


Up to now, that was all

Let me know paste my current boot situation and values

RESULT OF BCDEDIT COMMAND

Code:
C:\Windows\system32>bcdedit

Administrador de arranque de Windows
----------------------------------
Identificador           {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder            {current}
                        {e6888177-7f00-11e0-92e2-002215182db7}
toolsdisplayorder       {memdiag}
timeout                 10

Cargador de arranque de Windows
-----------------------------
Identificador           {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Microsoft Windows 7
locale                  es-ES
osdevice                partition=C:
systemroot              \Windows
resumeobject            {a5607d6c-7efe-11e0-a5f9-806e6f6e6963}
sos                     No
debug                   No

Sector de arranque del modo real
------------------------------
Identificador           {e6888177-7f00-11e0-92e2-002215182db7}
device                  partition=C:
path                    \NST\ntldr
description             Win Server 2003

RESULT OF DISKPART

Code:
C:\Windows\system32>diskpart

Microsoft DiskPart versión 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
En el equipo: WIN7MANOLAIN

DISKPART> list disk

  Núm Disco  Estado      Tamaño   Disp     Din  Gpt
  ---------- ----------  -------  -------  ---  ---
  Disco 0    En línea     465 GB      0 B
  Disco 1    En línea     298 GB     9 MB
  Disco 2    No hay med      0 B      0 B
  Disco 3    No hay med      0 B      0 B
  Disco 4    No hay med      0 B      0 B
  Disco 5    No hay med      0 B      0 B

DISKPART> sel disk 0

El disco 0 es ahora el disco seleccionado.

DISKPART> list part

  Núm Partición  Tipo              Tamaño   Desplazamiento
  -------------  ----------------  -------  ---------------
  Partición 1    Principal           39 GB    31 KB
  Partición 2    Principal           50 GB    39 GB
  Partición 0    Extendido          376 GB    89 GB
  Partición 4    Lógico              14 GB    89 GB
  Partición 5    Lógico               9 GB   103 GB
  Partición 3    Lógico             352 GB   113 GB

EASYBCD CURRENT SETTINGS


Code:
There are a total of 2 entries listed in the bootloader.

Default: Microsoft Windows 7
Timeout: 10 seconds
Boot Drive: C:\

Entry #1
Name: Microsoft Windows 7
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe

Entry #2
Name: Win Server 2003
BCD ID: {e6888177-7f00-11e0-92e2-002215182db7}
Drive: C:\
Bootloader Path: \NST\ntldr

Any more ideas guys?
 

mqudsi

Mostly Harmless
Staff member
#9
Please. You're going about this all wrong.

Don't overcomplicate things. The Windows repair will not fix your Windows 2003 boot.

Let's just do this a step at a time... Don't show me the EasyBCD basic mode — show me the detailed mode output.
 
#10
OK then, lets start from the beginning

EasbyBCD in detailed mode:

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {0ba78536-7efe-11e0-a44d-002215182db7}
resumeobject {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder {0ba78536-7efe-11e0-a44d-002215182db7}
{e6888177-7f00-11e0-92e2-002215182db7}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 10

Windows Boot Loader
-------------------
identifier {0ba78536-7efe-11e0-a44d-002215182db7}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows 7
locale es-ES
osdevice partition=C:
systemroot \Windows
resumeobject {a5607d6c-7efe-11e0-a5f9-806e6f6e6963}
sos No
debug No

Real-mode Boot Sector
---------------------
identifier {e6888177-7f00-11e0-92e2-002215182db7}
device partition=C:
path \NST\ntldr
description Win Server 2003
 
#12
OK. Thank you.

Can you post the output of EasyBCD | Useful Utilities | Power Console
bootgrabber.exe /tlist

And, just to double-check, this is all with EasyBCD 2.1 beta from EasyBCD 2.1 Beta Builds - The NeoSmart Forums, right?
I am using EasyBCD 2.0.2.117

Here we go with the bootgrabber command

Code:
c:\program files\neosmart technologies\EasyBCD\bin>bootgrabber.exe /tlist

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2010 <http://neosmart.net/>

Unable to get volume information for \\?\Volume{29267cdd-7e92-11e0-882d-806e6f6e
6963}\
Unable to get volume information for \\?\Volume{29267cde-7e92-11e0-882d-806e6f6e
6963}\
Unable to get volume information for \\?\Volume{29267cdf-7e92-11e0-882d-806e6f6e
6963}\
Unable to get volume information for \\?\Volume{29267ce0-7e92-11e0-882d-806e6f6e
6963}\
Unable to get volume information for \\?\Volume{29267cc9-7e92-11e0-882d-806e6f6e
6963}\
Error issuing IOCTL_DISK_GET_LENGTH_INFO on disk 1. Last error: 0x15
Error issuing IOCTL_DISK_GET_LENGTH_INFO on disk 2. Last error: 0x15
Error issuing IOCTL_DISK_GET_LENGTH_INFO on disk 3. Last error: 0x15
Error issuing IOCTL_DISK_GET_LENGTH_INFO on disk 4. Last error: 0x15
D0,5,4,2,500107862016,0
P1,C:\,7,41940670464,3273629696,Yes,multi(0)disk(0)rdisk(0)partition(1),Yes,NTFS

P2,D:\,7,53694627840,31232659456,Yes,multi(0)disk(0)rdisk(0)partition(2),No,NTFS

P0,,5,404469918720,0,Yes,,No,
P3,E:\,7,378469776384,47396761600,Yes,multi(0)disk(0)rdisk(0)partition(3),No,NTF
S
P0,,5,15998169088,0,No,,No,
P4,,130,15998105088,15998105088,No,multi(0)disk(0)rdisk(0)partition(5),No,
P0,,5,10001940480,0,No,,No,
P5,,131,10001908224,10001908224,No,multi(0)disk(0)rdisk(0)partition(5),No,
 

Terry60

Knows where his towel is.
Staff member
#13
Try the latest build from CG's link.