WWW Server Won't Boot After Hard Power Failure

Discussion in 'Server Operation' started by giganet, May 14, 2008.

  1. giganet

    giganet New Member

    Hello group...

    We had a two hour power outage this morning which exceeded the time allotted by the UPS system and our backup generator was out of diesel fuel, so unfortunately before I could physically shut down the systems they were powered off hard by the UPS system.

    One of my WWW servers now has issues at boot;
    This server is running Ubunutu 6.06 with BIND9 and MySQL in addition to ISPConfig.

    The H/D is IDE Western Digital.

    The error I see when attempting to reboot the server:
    Searching for Boot Record From SCSI... Not found
    Boot Failure
    Insert BOOT diskette in A:
    Press any key when ready
    Once again this drive is not SCSI and why it is complaining of SCSI errors is puzzling.

    I do not have a boot disk on floppy and am unclear what would be the best measure to take to restore function of the server?

    Thanking you in advance for your help.

  2. thecaoticone

    thecaoticone New Member

    This may be a stupid question, but, have you checked the boot priorty and hard drive settings in the board bios?

    You may also want to use a modern live cd like gentoo to scan the drive for possible errors.
    Last edited: May 15, 2008
  3. giganet

    giganet New Member

    Thanks for the reply.

    Yep, I did that and all is in order it is set to boot first from IDE-0 and then CD-ROM then FLOPPY.

  4. falko

    falko Super Moderator ISPConfig Developer

    You could use a Live-CD such as Knoppix or Ubuntu and boot into the system to have a deeper look at what's happening.
  5. giganet

    giganet New Member

    Got It

    Thank you Falko

    It booted after I entered the BIOS and asked it to use default settings, which is weird because the settings didn't appear to change with respect to drives and such.

    Thanks for your help everyone.

  6. falko

    falko Super Moderator ISPConfig Developer

    Glad to hear the problem's gone! :)

Share This Page