Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm trying to install Windows Server 2008 Small Business Edition using the following hardware:

  • Intel S3420GP Motherboard
  • 3400 socket XEON CPU
  • Samsung DVD Drive
  • 2x 250 GB Hard Drives in RAID 1

I booted to the DVD and went through the Windows installation product, entering my product key, choosing a partition, and all that stuff. Everything seemed to go smoothly until the first reboot.

When I rebooted the first time, it came back to the exact same installation screen as if the first installation attempt didn't even happen. I checked the files on the hard drive, and I can see several GB of standard Windows folders, indicating that something was copied over during the first installation attempt.

If I remove the Windows DVD from the drive and reboot, I'm brought to a screen that simply says:

NO BOOTABLE PARTITION FOUND IN TABLE

What might I try to do to resolve this problem?

share|improve this question
    
Can you add information on what is defining the RAID? 3rd party card or BIOS based SATA RAID? –  Wayne Jan 17 '10 at 4:03
    
it was SATA RAID running off of the embedded RAID controller on the Intel motherboard. I made some adjustments there at that seemed to fix it. –  Ben McCormack Jan 17 '10 at 17:42
add comment

2 Answers

up vote 1 down vote accepted

After the first reboot, you need to make sure that your BIOS doesn't default to booting from the disk drive, largely because it needs to boot from the hard disk. However, the disk does need to stay in the drive, because to finish the installation you need to have the disk.

share|improve this answer
    
I think you mean BIOS does not default to booting from the CD/DVD drive, because it needs to boot from the hard disk.... –  Wayne Jan 17 '10 at 4:02
    
you know, I think it was a mix of the RAID setup and my flash drive causing issues. –  Ben McCormack Jan 28 '10 at 14:04
add comment

Advised bmccormack to check the RAID information (17th Jan 2010) to see if that resolved the issue. Adding this here so that bmccormack can mark this as correct and update with the relevant information.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.