none
Is there a Server 2008 startup failure error log?

    Question

  • I deleted a drive when I shouldn't have (How do I assign a drive letter to a partition from command prompt), so AD couldn't see the edb.log files, and with Oberwald's help I reckon I've nearly fixed my original problem by remapping a drive as the expected D:, but my server still won't start, and goes to the recovery screen. Obviously I've missed something, but what? Is there an error log that is accessible from the recovery command prompt that will help me find out what's wrong? I guess it can't find some files. I still have them, but they're probably not in the right place.

    Tuesday, April 09, 2013 10:24 PM

Answers

  • Hi

    Please press F8 during boot time and enable boot logging. It will write ntbtlog.txt in the Windows's directory.

    You can read it after from the recovery console, or if you boot with a bootable OS you can read it if it see your array controller.

    In the file you will see what it load line by line, assuming the last line wrote is the faulty's module is a good first step.

    Thanks


    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Twitter - @yagmoth555 ()
    Blog: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

    • Marked as answer by AntoDN Thursday, April 11, 2013 10:56 AM
    Wednesday, April 10, 2013 3:05 AM

All replies

  • Hi

    Please press F8 during boot time and enable boot logging. It will write ntbtlog.txt in the Windows's directory.

    You can read it after from the recovery console, or if you boot with a bootable OS you can read it if it see your array controller.

    In the file you will see what it load line by line, assuming the last line wrote is the faulty's module is a good first step.

    Thanks


    MCP | MCTS 70-236: Exchange Server 2007, Configuring

    Twitter - @yagmoth555 ()
    Blog: http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

    • Marked as answer by AntoDN Thursday, April 11, 2013 10:56 AM
    Wednesday, April 10, 2013 3:05 AM
  • Thanks for your help Yagmoth555 - that was kind of what I needed. Unfortunately it didn't tell me more than I already knew - that AD couldn't start, but I couldn't figure out why.

    Having spent two days on this, I decided to just reinstall the OS as it's only got five users. Maybe that wasn't such a good idea, but it is back in action now, all neat and new. Thanks for the answer :).

    • Proposed as answer by arnavsharmaMVP Thursday, April 11, 2013 10:55 AM
    Thursday, April 11, 2013 10:04 AM