• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 428
  • Last Modified:

windows sbs2003 server fails to boot

We have a single sbs2003 server with has a simple raid1 mirror and one of the drives has burnt out.

Unfortunately the remaining drive fails to boot so I presume we have to do something to it to configure it.

When we log in using the recovery console, the drive shows as drive d:

Can anyone advise on what we need to do?

As you can imagine we are desperate to get this operational.

Any help gratefully accepted

  • 2
1 Solution
Miguel Angel Perez MuñozCommented:
Try removing damaged drive, sometimes boot fails because this drive is marked as D:. During boot, can you select from what drive want boot? try selecting secondary.
nigelbeatsonAuthor Commented:
I have removed the faulty drive, and even swapped over the Sata cables, but we still get the operating system missing error.

When boot with the system cd we can log in to the repair console, but it is identified as drive d: whichever cable is connected.

Any ideas?
So what device is drive C:?

Can you access the RAID utility during the POST? What does it tell you about the status of the remaining drive?

What server and RAID controller do you have?
nigelbeatsonAuthor Commented:
Thankyou. Your post helped me realise that the drive was not configured as the boot device in the bios, and as soon as I marked it so, the server sprang into life!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now