Boot loop, and error "The volume appears to contain one or more unrecoverable...

Discussion in 'Windows Small Business Server' started by Keith, Aug 26, 2004.

  1. Keith

    Keith Guest

    I installed a server running SBS2003 about a month ago.
    Last night after a few simple changes I rebooted. Now
    the server boot loops a few seconds after showing the
    windows 2003 splash screen. I can hit F8 and get the
    boot menu, but none of the choices yields any positive
    results. The reboot happens shortly after the file
    drvmain.sdb begins to load.

    When I boot to CD and run recovery console, and am at the
    C prompt, and type in DIR, I get the error message "An
    error occured during directory enumeration" When I run
    CHKdSK /R I get the error message "the volume appears to
    contain one or more unrecoverable problems." The command
    FIXBOOT identified a problem with the boot sector and
    supposedly fixed it, same with FIXMBR. FIXBOOT does see
    the partition as a NTFS partition.

    If I slave the drive onto another PC, the OS partition on
    the "bad" drive shows as RAW, but healthy.

    A second partition on the drive where my data is is fine.

    My two questions are:
    1) Can I recover from this problem?
    2) Any idea how it happened in the first place so I can
    avoid it again. I don't believe that adding a user and
    adding FTP services would do this.

    The configuration is an Intel MOBO, Promise SATA RAID
    controller, Antec 380W power supply, twin Maxtor SATA
    80Gb drives (both drives exhibit the exact same behavior,
    as does the the mirroed array)

    Thanks, Keith
     
    Keith, Aug 26, 2004
    #1
    1. Advertisements

  2. well you don't tell us what the "few simple changes are"
    Some folks have experienced SATA drive issues but seems to me more with the
    promise controller than others.

    I doubt you can recover.
    The good news is your data is on another partition.
     
    CRIS HANNA \(SBS-MVP\), Aug 26, 2004
    #2
    1. Advertisements

  3. From what you describe, you have a complicates sequence of issues there.

    It's conceivable that you could recover the drive, but it's unlikely to be
    your most cost effective effort if you have a system state backup and copy
    of the relevant Exchange databases.

    It's unlikely you would be successful in getting the entire thing restored
    without a system state restore as well, so it's more likely to be your best
    course to do a bare metal restore, then restore System State to it.
     
    Jeff Middleton [SBS-MVP], Aug 26, 2004
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.