<div>
I have removed the faulty drive, and even swapped over the Sata cables, but we still get the operating system missing error. <br />
<br />
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.<br />
<br />
Any ideas?
</div>


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?

<div>
So what device is drive C:?<br />
<br />
Can you access the RAID utility during the POST? What does it tell you about the status of the remaining drive?<br />
<br />
What server and RAID controller do you have?
</div>


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?

<div>
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!
</div>


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!

<div>
<div class="content wysiwyg-content">
We have a single sbs2003 server with has a simple raid1 mirror and one of the drives has burnt out.<br />
<br />
Unfortunately the remaining drive fails to boot so I presume we have to do something to it to configure it.<br />
<br />
When we log in using the recovery console, the drive shows as drive d:<br />
<br />
Can anyone advise on what we need to do? <br />
<br />
As you can imagine we are desperate to get this operational. <br />
<br />
Any help gratefully accepted<br />
<br />
Thanks
</div>
</div>


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

Thanks

windows sbs2003 server fails to boot

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).