Problem with BOOT.INI after a restore.

I have a BOOT.INI that is rather squirrly....

If the OS boots on its own, using "Windows (Default)" it goes to a NTOS Kernel error and does not actually load.

IF, on the other hand, I choose "Windows Server 2003 for..." during boot options, everything is fine.

This happened after a HIR disaster recovery. The other boot choices there are residuals that I am not ready to delete until I have this system booting normally.  Seems like all the others will fail a boot.

[boot loader]
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003 for Small Business Server" /noexecute=optout /fastdetect
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003 for Small Business Server" /noexecute=optout /fastdetect

multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Boot Mirror C: - secondary plex" 

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Disk 0 Partition 1 Windows Installation"

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Disk 0 Partition 1 Windows Installation"

Open in new window

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mustafa L. McLinnSystems Engineer/Systems AdministratorCommented:
Have you tried safe mode with any of these other boot options?
Lukasz ChmielewskiCommented:
try without the = ...


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sounds like you possibly have an issue with one of the raid drives in the windows software mirror of C. Check to see if one of the drives has failed. If so replace the drive go into SCSI BIOS settings and change the boot disk from ID 0 to ID 1, and the system should boot up correctly and then you can rebuild your mirror. If it is Hardware Raid there is a somewhat different process there.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

TrialWorksAuthor Commented:
Rsoly777, thanks for the feed back but the machine is a VM.   No raid affecting the cirtual disk.

Roads Roads: I cannot test right now but I am certain you nailed it!
Lukasz ChmielewskiCommented:
Nah, it's just bolded text - may seem that way ! :D
TrialWorksAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.