Can't boot system

It will alway try to boot from disk 0, if you need to boot from the other disk just swap it to slot 0. I had a customer that used dynamic raid on their systems and when a disk failed they just moved the drive position and carried on.

Thank you for your reply,

It is at disk 0. Ive modified the boot.ini to reflect the proper order as well as trying the original but it changes nothing. Why am I getting an "Invalid system disk" error from the floppy when it appears to be formatted correctly? I was told it would boot from this disk in case the MBR was messed up but it just errors out.

If you're trying to recover the OS, boot from the (Windows) CD and select the recovery option and then the option to get to a recovery console (dos-window). Once here, issue a fixboot and fixmbr and exit/reboot to see if that helped.

I used the fixboot command and it told me there ware no partitions available as there is no C drive in dos mode. I then tried the fixmbr command and it also did nothing. This drive is a RAID1 software mirror of the original which crashed. The data and partitions are all there but on a Dynamic disk which had no prior partitions. My problem is there is no boot information written to this disk as it was all on the original disk. The Fault boot floppy was supposed to let me boot this thing up since the loader was on the floppy but it does not work. It simply reads invalid system disc, please remove.

put the disks as they were and try a boot.ini something like this:

[boot loader]
timeout=60
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=”DISK 0″ /noexecute=optout /fastdetect /3GB
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS=”DISK 1″ /noexecute=optout /fastdetect /3GB

also as it's scsi you may need another file on the floppy cdlled ntbootdd.sys according to various microsoft kb's

Thanks,

That doesn't seem to help either though. I also couldn't find the ntbootdd.sys file anywhere on the server.

Let's assume this is a lost cause and I'm not going to get this paticular disk to boot. Is there anywhere to find out how to setup the RAID 1 correctly so as to avoid this painful situation again? I mean, why does it give you a choice of drives to boot from if it will only boot from the primary drive? What good is the raid if the primary fails and you can't boot from the backup?
In our system we had the main system drive as C and it was originally setup as a basic drive. It was then converted to a dynamic drive so it could be mirrored. A new identical blank drive was added and setup also as dynammic but unlike the first drive, it had no preset partitions. If I did partition it, Windows would not let me mirror it unless it was unallocated space. What is the correct way to setup the duplicate drive so it can be mirrored and booted from if the primary fails again?

I finally got it to recognize C drive and got the recovery console to run both commands successfully however it still will not boot from that drive.