Re: can't boot from mirrored boot drive

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)\WINDOWS
[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




.

Relevant Pages

  • Re: New to XP and confused
    ... Boot order should be floppy, cd, hdd. ... What is in the D: and E: partitions? ... To determine if the OEM cd will ignore what you have done so far (I hope so, ... >>> sequence goes C - E - F drives skipping the D drive that used to be ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: cant boot from mirrored boot drive
    ... To me it sounds like the ARC path is wrong, you should be able to see the drives' ARC paths with WinObj. ... I'd like to know how to approch this disk. ... Do I break the mirror, shutdown and remove the good boot disk rdiskand just leave the disk that doesn't want to boot in and boot to the recovery conole to check it out? ...
    (microsoft.public.windows.server.general)
  • Re: Desperate help needed! MBR problem
    ... I recently installed suse 10.1 on my machine to dual boot with windows xp ... both installed on the same hard drive on separate partitions. ... I see new 80 gig drives for CDN$50 or less. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: RAID 1
    ... >> at boot to know if it is a raid device or not. ... but a general decision that people take to mirror ... partitions and not whole drives. ... > still have a copy of everything, but because grub didn't make the ...
    (comp.os.linux.networking)
  • Re: SBS 2003 + SATA + failing software mirror
    ... IF the MBR boot sector is created properly before the RAID is established it's a simple matter of removing the failed drive and booting off the mirror, else you end up where you're at. ... When you start the system you need to check that partitions are correctly assigned to the right drives. ... On my SCSI test rig everything works as you would expect..with SATA I'm getting conflicting issues. ...
    (microsoft.public.windows.server.sbs)