can't boot from mirrored boot drive

billd

Hi,

Recently, my mirrored drive in my 2K3 server died. I took the drive out,
removed the mirror, but new drive in, replaced the mirror. It says it is
healthing and the mirror is fine. However, if I try to boot from the
mirrored drive, it fails with the error:

windows could not start because the following file is missing or corrupt:
<windows root>\system32ntoskrnl.exe

please reinstall a copy of the above file.

Now that would normally say to me that the boot.ini is incorrect, but it
looks right to me:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003 for Small
Business Server" /noexecute=optout /fastdetect

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

the disks are mirrored, so the path to windows should be correct yes? They
are sata drives, drive 0 and drive 1 on the main system board's controller.
I was able to format the drive correctly etc before I made the mirror> I can
look at properties of the disk in disk manager - everything seems sweet until
I try and boot the secondary. There are three partitions on rdisk(0) 102MB
EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
Healthy

rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
healthy. When I set up the mirror, it did not give me the opportunity to
mirror the EISA Configuration.

Anyway, it would appear that I am running on empty to coin a phrase because
if my first drive fails, it looks as though I would not be able to boot the
mirror drive. How can I see what the state of that drive is? Do I need to
break the mirror and unplug the rdsk(0) and see if it will boot? What is the
best procedure for this.

Thanks

John John

You are trying to boot on the second partition on the first hard disk,
is that where the installation resides?

multi(0)disk(0)rdisk(0)partition(2)
^^^^^^^^

John

billd wrote:

> Hi,
>
> Recently, my mirrored drive in my 2K3 server died. I took the drive out,
> removed the mirror, but new drive in, replaced the mirror. It says it is
> healthing and the mirror is fine. However, if I try to boot from the
> mirrored drive, it fails with the error:
>
> windows could not start because the following file is missing or corrupt:
> <windows root>\system32ntoskrnl.exe
>
> please reinstall a copy of the above file.
>
> Now that would normally say to me that the boot.ini is incorrect, but it
> looks right to me:
>
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003 for Small
> Business Server" /noexecute=optout /fastdetect
>
> multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Boot Mirror C: - secondary
> plex" /noexecute=optout /fastdetect
>
> the disks are mirrored, so the path to windows should be correct yes? They
> are sata drives, drive 0 and drive 1 on the main system board's controller.
> I was able to format the drive correctly etc before I made the mirror> I can
> look at properties of the disk in disk manager - everything seems sweet until
> I try and boot the secondary. There are three partitions on rdisk(0) 102MB
> EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
> Healthy
>
> rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
> healthy. When I set up the mirror, it did not give me the opportunity to
> mirror the EISA Configuration.
>
> Anyway, it would appear that I am running on empty to coin a phrase because
> if my first drive fails, it looks as though I would not be able to boot the
> mirror drive. How can I see what the state of that drive is? Do I need to
> break the mirror and unplug the rdsk(0) and see if it will boot? What is the
> best procedure for this.
>
> Thanks
>
>

John John

You are trying to boot on the second partition on the first hard disk,
is that where the installation resides?

multi(0)disk(0)rdisk(0)partition(2)
^^^^^^^^

John

billd wrote:

> Hi,
>
> Recently, my mirrored drive in my 2K3 server died. I took the drive out,
> removed the mirror, but new drive in, replaced the mirror. It says it is
> healthing and the mirror is fine. However, if I try to boot from the
> mirrored drive, it fails with the error:
>
> windows could not start because the following file is missing or corrupt:
> <windows root>\system32ntoskrnl.exe
>
> please reinstall a copy of the above file.
>
> Now that would normally say to me that the boot.ini is incorrect, but it
> looks right to me:
>
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003 for Small
> Business Server" /noexecute=optout /fastdetect
>
> multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Boot Mirror C: - secondary
> plex" /noexecute=optout /fastdetect
>
> the disks are mirrored, so the path to windows should be correct yes? They
> are sata drives, drive 0 and drive 1 on the main system board's controller.
> I was able to format the drive correctly etc before I made the mirror> I can
> look at properties of the disk in disk manager - everything seems sweet until
> I try and boot the secondary. There are three partitions on rdisk(0) 102MB
> EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
> Healthy
>
> rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
> healthy. When I set up the mirror, it did not give me the opportunity to
> mirror the EISA Configuration.
>
> Anyway, it would appear that I am running on empty to coin a phrase because
> if my first drive fails, it looks as though I would not be able to boot the
> mirror drive. How can I see what the state of that drive is? Do I need to
> break the mirror and unplug the rdsk(0) and see if it will boot? What is the
> best procedure for this.
>
> Thanks
>
>

billd

Yes, I am... The first disk boots ok. There is an EISA partition that is the
first partition on the first rdisk(0). So I boot from the second. On the
second harddisk rdisk(1) there are only two partitions, the first is the
boot, but it will not boot.

Thanks for your response..

Bill

"John John" wrote:

> You are trying to boot on the second partition on the first hard disk,
> is that where the installation resides?
>
> multi(0)disk(0)rdisk(0)partition(2)
> ^^^^^^^^
>
> John
>
> billd wrote:
>
> > Hi,
> >
> > Recently, my mirrored drive in my 2K3 server died. I took the drive out,
> > removed the mirror, but new drive in, replaced the mirror. It says it is
> > healthing and the mirror is fine. However, if I try to boot from the
> > mirrored drive, it fails with the error:
> >
> > windows could not start because the following file is missing or corrupt:
> > <windows root>\system32ntoskrnl.exe
> >
> > please reinstall a copy of the above file.
> >
> > Now that would normally say to me that the boot.ini is incorrect, but it
> > looks right to me:
> >
> > [boot loader]
> > timeout=30
> > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003 for Small
> > Business Server" /noexecute=optout /fastdetect
> >
> > multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Boot Mirror C: - secondary
> > plex" /noexecute=optout /fastdetect
> >
> > the disks are mirrored, so the path to windows should be correct yes? They
> > are sata drives, drive 0 and drive 1 on the main system board's controller.
> > I was able to format the drive correctly etc before I made the mirror> I can
> > look at properties of the disk in disk manager - everything seems sweet until
> > I try and boot the secondary. There are three partitions on rdisk(0) 102MB
> > EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
> > Healthy
> >
> > rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
> > healthy. When I set up the mirror, it did not give me the opportunity to
> > mirror the EISA Configuration.
> >
> > Anyway, it would appear that I am running on empty to coin a phrase because
> > if my first drive fails, it looks as though I would not be able to boot the
> > mirror drive. How can I see what the state of that drive is? Do I need to
> > break the mirror and unplug the rdsk(0) and see if it will boot? What is the
> > best procedure for this.
> >
> > Thanks
> >
> >
>
>

billd

Yes, I am... The first disk boots ok. There is an EISA partition that is the
first partition on the first rdisk(0). So I boot from the second. On the
second harddisk rdisk(1) there are only two partitions, the first is the
boot, but it will not boot.

Thanks for your response..

Bill

"John John" wrote:

> You are trying to boot on the second partition on the first hard disk,
> is that where the installation resides?
>
> multi(0)disk(0)rdisk(0)partition(2)
> ^^^^^^^^
>
> John
>
> billd wrote:
>
> > Hi,
> >
> > Recently, my mirrored drive in my 2K3 server died. I took the drive out,
> > removed the mirror, but new drive in, replaced the mirror. It says it is
> > healthing and the mirror is fine. However, if I try to boot from the
> > mirrored drive, it fails with the error:
> >
> > windows could not start because the following file is missing or corrupt:
> > <windows root>\system32ntoskrnl.exe
> >
> > please reinstall a copy of the above file.
> >
> > Now that would normally say to me that the boot.ini is incorrect, but it
> > looks right to me:
> >
> > [boot loader]
> > timeout=30
> > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOW S
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003 for Small
> > Business Server" /noexecute=optout /fastdetect
> >
> > multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Boot Mirror C: - secondary
> > plex" /noexecute=optout /fastdetect
> >
> > the disks are mirrored, so the path to windows should be correct yes? They
> > are sata drives, drive 0 and drive 1 on the main system board's controller.
> > I was able to format the drive correctly etc before I made the mirror> I can
> > look at properties of the disk in disk manager - everything seems sweet until
> > I try and boot the secondary. There are three partitions on rdisk(0) 102MB
> > EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
> > Healthy
> >
> > rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
> > healthy. When I set up the mirror, it did not give me the opportunity to
> > mirror the EISA Configuration.
> >
> > Anyway, it would appear that I am running on empty to coin a phrase because
> > if my first drive fails, it looks as though I would not be able to boot the
> > mirror drive. How can I see what the state of that drive is? Do I need to
> > break the mirror and unplug the rdsk(0) and see if it will boot? What is the
> > best procedure for this.
> >
> > Thanks
> >
> >
>
>

John John

The Recovery Console's bootcfg or map commands or using Sysinternal's
WinObj tool in the up and running installation may shed some light on
the situation.

John

billd wrote:
> Yes, I am... The first disk boots ok. There is an EISA partition that is the
> first partition on the first rdisk(0). So I boot from the second. On the
> second harddisk rdisk(1) there are only two partitions, the first is the
> boot, but it will not boot.
>
> Thanks for your response..
>
> Bill
>
> "John John" wrote:
>
>
>>You are trying to boot on the second partition on the first hard disk,
>>is that where the installation resides?
>>
>>multi(0)disk(0)rdisk(0)partition(2)
>> ^^^^^^^^
>>
>>John
>>
>>billd wrote:
>>
>>
>>>Hi,
>>>
>>>Recently, my mirrored drive in my 2K3 server died. I took the drive out,
>>>removed the mirror, but new drive in, replaced the mirror. It says it is
>>>healthing and the mirror is fine. However, if I try to boot from the
>>>mirrored drive, it fails with the error:
>>>
>>>windows could not start because the following file is missing or corrupt:
>>><windows root>\system32ntoskrnl.exe
>>>
>>>please reinstall a copy of the above file.
>>>
>>>Now that would normally say to me that the boot.ini is incorrect, but it
>>>looks right to me:
>>>
>>>[boot loader]
>>>timeout=30
>>>default=multi(0)disk(0)rdisk(0)partition(2)\WIN DOWS
>>>[operating systems]
>>>multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Wi ndows Server 2003 for Small
>>>Business Server" /noexecute=optout /fastdetect
>>>
>>>multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Bo ot Mirror C: - secondary
>>>plex" /noexecute=optout /fastdetect
>>>
>>>the disks are mirrored, so the path to windows should be correct yes? They
>>>are sata drives, drive 0 and drive 1 on the main system board's controller.
>>>I was able to format the drive correctly etc before I made the mirror> I can
>>>look at properties of the disk in disk manager - everything seems sweet until
>>>I try and boot the secondary. There are three partitions on rdisk(0) 102MB
>>>EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
>>>Healthy
>>>
>>>rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
>>>healthy. When I set up the mirror, it did not give me the opportunity to
>>>mirror the EISA Configuration.
>>>
>>>Anyway, it would appear that I am running on empty to coin a phrase because
>>>if my first drive fails, it looks as though I would not be able to boot the
>>>mirror drive. How can I see what the state of that drive is? Do I need to
>>>break the mirror and unplug the rdsk(0) and see if it will boot? What is the
>>>best procedure for this.
>>>
>>>Thanks
>>>
>>>
>>
>>

John John

The Recovery Console's bootcfg or map commands or using Sysinternal's
WinObj tool in the up and running installation may shed some light on
the situation.

John

billd wrote:
> Yes, I am... The first disk boots ok. There is an EISA partition that is the
> first partition on the first rdisk(0). So I boot from the second. On the
> second harddisk rdisk(1) there are only two partitions, the first is the
> boot, but it will not boot.
>
> Thanks for your response..
>
> Bill
>
> "John John" wrote:
>
>
>>You are trying to boot on the second partition on the first hard disk,
>>is that where the installation resides?
>>
>>multi(0)disk(0)rdisk(0)partition(2)
>> ^^^^^^^^
>>
>>John
>>
>>billd wrote:
>>
>>
>>>Hi,
>>>
>>>Recently, my mirrored drive in my 2K3 server died. I took the drive out,
>>>removed the mirror, but new drive in, replaced the mirror. It says it is
>>>healthing and the mirror is fine. However, if I try to boot from the
>>>mirrored drive, it fails with the error:
>>>
>>>windows could not start because the following file is missing or corrupt:
>>><windows root>\system32ntoskrnl.exe
>>>
>>>please reinstall a copy of the above file.
>>>
>>>Now that would normally say to me that the boot.ini is incorrect, but it
>>>looks right to me:
>>>
>>>[boot loader]
>>>timeout=30
>>>default=multi(0)disk(0)rdisk(0)partition(2)\WIN DOWS
>>>[operating systems]
>>>multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Wi ndows Server 2003 for Small
>>>Business Server" /noexecute=optout /fastdetect
>>>
>>>multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Bo ot Mirror C: - secondary
>>>plex" /noexecute=optout /fastdetect
>>>
>>>the disks are mirrored, so the path to windows should be correct yes? They
>>>are sata drives, drive 0 and drive 1 on the main system board's controller.
>>>I was able to format the drive correctly etc before I made the mirror> I can
>>>look at properties of the disk in disk manager - everything seems sweet until
>>>I try and boot the secondary. There are three partitions on rdisk(0) 102MB
>>>EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
>>>Healthy
>>>
>>>rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
>>>healthy. When I set up the mirror, it did not give me the opportunity to
>>>mirror the EISA Configuration.
>>>
>>>Anyway, it would appear that I am running on empty to coin a phrase because
>>>if my first drive fails, it looks as though I would not be able to boot the
>>>mirror drive. How can I see what the state of that drive is? Do I need to
>>>break the mirror and unplug the rdsk(0) and see if it will boot? What is the
>>>best procedure for this.
>>>
>>>Thanks
>>>
>>>
>>
>>

billd

Well, I used bootcfg after I created the mirror and it looked fine. I've
just installed WinObj, but I can't seem to see anything there that helps me
identify what is the problem on this disk.

Basically, I'd like to know how to approch this disk. Do I break the
mirror, shutdown and remove the good boot disk rdisk(0) and just leave the
disk that doesn't want to boot in and boot to the recovery conole to check it
out?

Then if I can see the problem and take whatever steps, how do I put a mirror
back in place, without removing the mirror and putting the mirror back? I
haven't done this before... well, not in windows, only in PERC and other
hardware raid controllers and while I have googled this extensively, I get
conflicting information as to if I need a floppy boot disk with boot.ini on
it or not, which I don't currently have (I assume as the disks are mirrored,
they each have a copy of boot.ini right?)

Was there a step I missed in mirroring the disk, do I have to do anything
besides install it, go to disk manager and make it dynamic and then add
mirror to it? Do I have to make it bootable somehow first?

I've worked hardware RAIDs and even Linux S/W RAID without incident, but
this one has got me befuddled.

Thanks


"John John" wrote:

> The Recovery Console's bootcfg or map commands or using Sysinternal's
> WinObj tool in the up and running installation may shed some light on
> the situation.
>
> John
>
> billd wrote:
> > Yes, I am... The first disk boots ok. There is an EISA partition that is the
> > first partition on the first rdisk(0). So I boot from the second. On the
> > second harddisk rdisk(1) there are only two partitions, the first is the
> > boot, but it will not boot.
> >
> > Thanks for your response..
> >
> > Bill
> >
> > "John John" wrote:
> >
> >
> >>You are trying to boot on the second partition on the first hard disk,
> >>is that where the installation resides?
> >>
> >>multi(0)disk(0)rdisk(0)partition(2)
> >> ^^^^^^^^
> >>
> >>John
> >>
> >>billd wrote:
> >>
> >>
> >>>Hi,
> >>>
> >>>Recently, my mirrored drive in my 2K3 server died. I took the drive out,
> >>>removed the mirror, but new drive in, replaced the mirror. It says it is
> >>>healthing and the mirror is fine. However, if I try to boot from the
> >>>mirrored drive, it fails with the error:
> >>>
> >>>windows could not start because the following file is missing or corrupt:
> >>><windows root>\system32ntoskrnl.exe
> >>>
> >>>please reinstall a copy of the above file.
> >>>
> >>>Now that would normally say to me that the boot.ini is incorrect, but it
> >>>looks right to me:
> >>>
> >>>[boot loader]
> >>>timeout=30
> >>>default=multi(0)disk(0)rdisk(0)partition(2)\WIN DOWS
> >>>[operating systems]
> >>>multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Wi ndows Server 2003 for Small
> >>>Business Server" /noexecute=optout /fastdetect
> >>>
> >>>multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Bo ot Mirror C: - secondary
> >>>plex" /noexecute=optout /fastdetect
> >>>
> >>>the disks are mirrored, so the path to windows should be correct yes? They
> >>>are sata drives, drive 0 and drive 1 on the main system board's controller.
> >>>I was able to format the drive correctly etc before I made the mirror> I can
> >>>look at properties of the disk in disk manager - everything seems sweet until
> >>>I try and boot the secondary. There are three partitions on rdisk(0) 102MB
> >>>EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
> >>>Healthy
> >>>
> >>>rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
> >>>healthy. When I set up the mirror, it did not give me the opportunity to
> >>>mirror the EISA Configuration.
> >>>
> >>>Anyway, it would appear that I am running on empty to coin a phrase because
> >>>if my first drive fails, it looks as though I would not be able to boot the
> >>>mirror drive. How can I see what the state of that drive is? Do I need to
> >>>break the mirror and unplug the rdsk(0) and see if it will boot? What is the
> >>>best procedure for this.
> >>>
> >>>Thanks
> >>>
> >>>
> >>
> >>
>
>

billd

Well, I used bootcfg after I created the mirror and it looked fine. I've
just installed WinObj, but I can't seem to see anything there that helps me
identify what is the problem on this disk.

Basically, I'd like to know how to approch this disk. Do I break the
mirror, shutdown and remove the good boot disk rdisk(0) and just leave the
disk that doesn't want to boot in and boot to the recovery conole to check it
out?

Then if I can see the problem and take whatever steps, how do I put a mirror
back in place, without removing the mirror and putting the mirror back? I
haven't done this before... well, not in windows, only in PERC and other
hardware raid controllers and while I have googled this extensively, I get
conflicting information as to if I need a floppy boot disk with boot.ini on
it or not, which I don't currently have (I assume as the disks are mirrored,
they each have a copy of boot.ini right?)

Was there a step I missed in mirroring the disk, do I have to do anything
besides install it, go to disk manager and make it dynamic and then add
mirror to it? Do I have to make it bootable somehow first?

I've worked hardware RAIDs and even Linux S/W RAID without incident, but
this one has got me befuddled.

Thanks


"John John" wrote:

> The Recovery Console's bootcfg or map commands or using Sysinternal's
> WinObj tool in the up and running installation may shed some light on
> the situation.
>
> John
>
> billd wrote:
> > Yes, I am... The first disk boots ok. There is an EISA partition that is the
> > first partition on the first rdisk(0). So I boot from the second. On the
> > second harddisk rdisk(1) there are only two partitions, the first is the
> > boot, but it will not boot.
> >
> > Thanks for your response..
> >
> > Bill
> >
> > "John John" wrote:
> >
> >
> >>You are trying to boot on the second partition on the first hard disk,
> >>is that where the installation resides?
> >>
> >>multi(0)disk(0)rdisk(0)partition(2)
> >> ^^^^^^^^
> >>
> >>John
> >>
> >>billd wrote:
> >>
> >>
> >>>Hi,
> >>>
> >>>Recently, my mirrored drive in my 2K3 server died. I took the drive out,
> >>>removed the mirror, but new drive in, replaced the mirror. It says it is
> >>>healthing and the mirror is fine. However, if I try to boot from the
> >>>mirrored drive, it fails with the error:
> >>>
> >>>windows could not start because the following file is missing or corrupt:
> >>><windows root>\system32ntoskrnl.exe
> >>>
> >>>please reinstall a copy of the above file.
> >>>
> >>>Now that would normally say to me that the boot.ini is incorrect, but it
> >>>looks right to me:
> >>>
> >>>[boot loader]
> >>>timeout=30
> >>>default=multi(0)disk(0)rdisk(0)partition(2)\WIN DOWS
> >>>[operating systems]
> >>>multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Wi ndows Server 2003 for Small
> >>>Business Server" /noexecute=optout /fastdetect
> >>>
> >>>multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Bo ot Mirror C: - secondary
> >>>plex" /noexecute=optout /fastdetect
> >>>
> >>>the disks are mirrored, so the path to windows should be correct yes? They
> >>>are sata drives, drive 0 and drive 1 on the main system board's controller.
> >>>I was able to format the drive correctly etc before I made the mirror> I can
> >>>look at properties of the disk in disk manager - everything seems sweet until
> >>>I try and boot the secondary. There are three partitions on rdisk(0) 102MB
> >>>EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
> >>>Healthy
> >>>
> >>>rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
> >>>healthy. When I set up the mirror, it did not give me the opportunity to
> >>>mirror the EISA Configuration.
> >>>
> >>>Anyway, it would appear that I am running on empty to coin a phrase because
> >>>if my first drive fails, it looks as though I would not be able to boot the
> >>>mirror drive. How can I see what the state of that drive is? Do I need to
> >>>break the mirror and unplug the rdsk(0) and see if it will boot? What is the
> >>>best procedure for this.
> >>>
> >>>Thanks
> >>>
> >>>
> >>
> >>
>
>

John John

To me it sounds like the ARC path is wrong, you should be able to see
the drives' ARC paths with WinObj. Does it match the ARC path in your
boot.ini file?

John

billd wrote:

> Well, I used bootcfg after I created the mirror and it looked fine. I've
> just installed WinObj, but I can't seem to see anything there that helps me
> identify what is the problem on this disk.
>
> Basically, I'd like to know how to approch this disk. Do I break the
> mirror, shutdown and remove the good boot disk rdisk(0) and just leave the
> disk that doesn't want to boot in and boot to the recovery conole to check it
> out?
>
> Then if I can see the problem and take whatever steps, how do I put a mirror
> back in place, without removing the mirror and putting the mirror back? I
> haven't done this before... well, not in windows, only in PERC and other
> hardware raid controllers and while I have googled this extensively, I get
> conflicting information as to if I need a floppy boot disk with boot.ini on
> it or not, which I don't currently have (I assume as the disks are mirrored,
> they each have a copy of boot.ini right?)
>
> Was there a step I missed in mirroring the disk, do I have to do anything
> besides install it, go to disk manager and make it dynamic and then add
> mirror to it? Do I have to make it bootable somehow first?
>
> I've worked hardware RAIDs and even Linux S/W RAID without incident, but
> this one has got me befuddled.
>
> Thanks
>
>
> "John John" wrote:
>
>
>>The Recovery Console's bootcfg or map commands or using Sysinternal's
>>WinObj tool in the up and running installation may shed some light on
>>the situation.
>>
>>John
>>
>>billd wrote:
>>
>>>Yes, I am... The first disk boots ok. There is an EISA partition that is the
>>>first partition on the first rdisk(0). So I boot from the second. On the
>>>second harddisk rdisk(1) there are only two partitions, the first is the
>>>boot, but it will not boot.
>>>
>>>Thanks for your response..
>>>
>>>Bill
>>>
>>>"John John" wrote:
>>>
>>>
>>>
>>>>You are trying to boot on the second partition on the first hard disk,
>>>>is that where the installation resides?
>>>>
>>>>multi(0)disk(0)rdisk(0)partition(2)
>>>> ^^^^^^^^
>>>>
>>>>John
>>>>
>>>>billd wrote:
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>Recently, my mirrored drive in my 2K3 server died. I took the drive out,
>>>>>removed the mirror, but new drive in, replaced the mirror. It says it is
>>>>>healthing and the mirror is fine. However, if I try to boot from the
>>>>>mirrored drive, it fails with the error:
>>>>>
>>>>>windows could not start because the following file is missing or corrupt:
>>>>><windows root>\system32ntoskrnl.exe
>>>>>
>>>>>please reinstall a copy of the above file.
>>>>>
>>>>>Now that would normally say to me that the boot.ini is incorrect, but it
>>>>>looks right to me:
>>>>>
>>>>>[boot loader]
>>>>>timeout=30
>>>>>default=multi(0)disk(0)rdisk(0)partition(2)\W INDOWS
>>>>>[operating systems]
>>>>>multi(0)disk(0)rdisk(0)partition(2)\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" /noexecute=optout /fastdetect
>>>>>
>>>>>the disks are mirrored, so the path to windows should be correct yes? They
>>>>>are sata drives, drive 0 and drive 1 on the main system board's controller.
>>>>>I was able to format the drive correctly etc before I made the mirror> I can
>>>>>look at properties of the disk in disk manager - everything seems sweet until
>>>>>I try and boot the secondary. There are three partitions on rdisk(0) 102MB
>>>>>EISA Configuration) C: 12GB NTFS (Healthy System) and Logs (G 62.40 GB NTFS
>>>>>Healthy
>>>>>
>>>>>rdisk(1) only has 2 partitions, the C: and G: which are mirrored and
>>>>>healthy. When I set up the mirror, it did not give me the opportunity to
>>>>>mirror the EISA Configuration.
>>>>>
>>>>>Anyway, it would appear that I am running on empty to coin a phrase because
>>>>>if my first drive fails, it looks as though I would not be able to boot the
>>>>>mirror drive. How can I see what the state of that drive is? Do I need to
>>>>>break the mirror and unplug the rdsk(0) and see if it will boot? What is the
>>>>>best procedure for this.
>>>>>
>>>>>Thanks
>>>>>
>>>>>
>>>>
>>>>
>>