+ Post New Thread
Results 1 to 6 of 6
Windows Server 2000/2003 Thread, Windows Server 2003 - Domain Controller - Invalid boot.ini in Technical; Hi All, This morning I have shut down our domain controller / file server to install an additional NIC. When ...
  1. #1
    mee
    mee is offline

    Join Date
    Oct 2008
    Posts
    17
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Windows Server 2003 - Domain Controller - Invalid boot.ini

    Hi All,

    This morning I have shut down our domain controller / file server to install an additional NIC. When I shut down, Windows installed some windows updates.

    Installed NIC - booted up - Windows won't boot. First it says invalid boot.ini, trying to boot from c:\windows

    It then comes up to say that ntoskrnl.exe is corrupt or invalid.

    I have tried safe mode etc and all the same. I have checked all SCSI connections in the server and all OK - BIOS RAID software is reporting that it can see all disks OK and that all virtual drives are normal.

    Any ideas?

    Thanks,
    Mee.

  2. #2

    Dos_Box's Avatar
    Join Date
    Jun 2005
    Location
    Preston, Lancashire
    Posts
    9,787
    Thank Post
    572
    Thanked 2,154 Times in 982 Posts
    Blog Entries
    23
    Rep Power
    626
    Hmmm. That may be a sign of a corrupt disk. Does it give any other file errors on reboots? If it does then I suggest that you look at your other domain controller to seize roles before you have to either re-install or replace disks.

  3. #3
    mee
    mee is offline

    Join Date
    Oct 2008
    Posts
    17
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Hi, thanks for the reply. They are the only two files it mentions, however at present I can't get it to go any further than that.

    I am trying to get into the recovery console on the Server 2003 CD, however I can't get it to go any further than where it asks for which windows installation to look at (default c:\windows) at that point the server reboots!

    Mee.

  4. #4

    Dos_Box's Avatar
    Join Date
    Jun 2005
    Location
    Preston, Lancashire
    Posts
    9,787
    Thank Post
    572
    Thanked 2,154 Times in 982 Posts
    Blog Entries
    23
    Rep Power
    626
    There are some leads for you here: Microsoft: Windows Server 2003 - ntoskrnl.exe missing or corrupt
    But it may be worth your while to run chkdsk /r from the recovery console first.
    Last edited by Dos_Box; 4th January 2011 at 01:14 PM.

  5. #5
    mee
    mee is offline

    Join Date
    Oct 2008
    Posts
    17
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Managed to get into recovery console now - dodgy RAID driver floppy.

    Am currently running chkdsk /r.

    Hope I don't have to rebuild the domain controller - luckily the FSMO roles are held by the other (currently healthy) DC so it shouldn't be too bad - but could do without the hassle really :-(

    Mee

  6. #6
    mee
    mee is offline

    Join Date
    Oct 2008
    Posts
    17
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Hi All,

    Just to let you know that I think this issue is now resolved.

    Running a chkdsk /r found and fixed some errors, however the DC would still not boot, reporting the same error.

    I went back into recovery console and noticed that the boot.ini was actually missing. Hence the message 'trying c:\windows' and then subsequent ntoskrnl.exe error.

    I copied the boot.ini from another Dell server with the same partition configuration. To be on the safe side, I also replaced the ntoskrnl.exe with a fresh copy expanded from the Windows Server 2003 CD. Server has now booted and so far appears OK. Fingers crossed!

    I'm sure it was the missing boot.ini rather than the ntoskrnl.exe being corrupt - as it assumes Windows is installed at Disk 0 Partition 1 - where in our case it is Disk 0 Partition 2.

    Thanks for the replies and hope this helps someone else in the future. Now need to investigate why the boot.ini disappeared and check the c: drive for consistency.

    Thanks,
    Mee.

SHARE:
+ Post New Thread

Similar Threads

  1. Windows 7 clients on Server 2003 domain
    By Earthling in forum Windows 7
    Replies: 3
    Last Post: 9th September 2010, 01:00 AM
  2. tapi3 message when removing last 2003 domain controller
    By sacrej in forum Windows Server 2000/2003
    Replies: 1
    Last Post: 24th August 2010, 07:35 PM
  3. First 2008 R2 Domain controller in a 2003 domain
    By zag in forum Windows Server 2008 R2
    Replies: 6
    Last Post: 9th June 2010, 02:26 PM
  4. Invalid boot.ini on Server after restart....
    By mullet_man in forum Windows
    Replies: 4
    Last Post: 16th July 2007, 03:16 PM
  5. Upgrading 2003 SP1 domain controller to 2003 R2
    By Andi in forum Wireless Networks
    Replies: 4
    Last Post: 27th June 2007, 01:22 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •