Re: Windows 2000 server, booting from mirror, boot.ini

Tech-Archive recommends: Fix windows errors by optimizing your registry

Try setting your Disk 1 as a slave on channel 2, with your CD being the
master. Then unplug your drive 0 and reboot. The OS should load from the
mirrored image on Disk 1.
I've set up several RAID 1 configurations like this and have never had a
problem booting from the mirrored drive when it needed to.

"hh" wrote:

> The way I understood it,aslong as the boot ini was copied across you should
> be able to uplug the master and it should boot of the mirror,I have also
> setup the same raid on a lot of servers but have never tried it out,I think
> if the master died you could remove the master and boot of the CD and run
> the repair over the slave to make it boot if necessary.
> Its a mirror you would think like ghost it should boot!!
> Martin
>
>
> "Phil_Certain" <c9groups@xxxxxxxxxxxxxx> wrote in message
> news:1132307427.743407.37980@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > ...is there no one out there who holds the key to this?....
> >
> > Phil_Certain wrote:
> >
> >> Hi,
> >>
> >> Can anyone help is advising how I can boot from a mirrored drive?
> >>
> >> I have Windows 2000 server installed on a single disk. I have recently
> >> added an identical disk in order to set up a RAID 1 mirror.
> >>
> >> Disk 0 is connected to IDE channel 1 as Master
> >> Disk 1 is connected to IDE channel 2 as master (CDROM is slave on IDE
> >> channel 2)
> >>
> >> I followed the process of converting disk 0 to a dynamic disk and then
> >> connecting the second disk, disk 1. I then mirrored the volumes to the
> >> new drive. All went well and a small (6MB) 'partion' of unallocated
> >> space was created on the second disk during the mirroring process.
> >>
> >>
> >> I created a boot floppy (as described in ms kb article 119467) that
> >> contained the files:
> >>
> >> boot.ini
> >> ntldr
> >> ntdetect.com
> >>
> >>
> >> [boot loader]
> >> timeout=30
> >> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> >> [operating systems]
> >> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
> >> Server" /fastdetect
> >>
> >>
> >> Following the mirroring, I added a line to boot.ini so that it now
> >> reads:
> >>
> >> [boot loader]
> >> timeout=30
> >> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> >> [operating systems]
> >> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
> >> Server" /fastdetect
> >> multi(0)disk(0)rdisk(1)partition(1)\WINNT="Microsoft Windows 2000
> >> Server" /fastdetect
> >>
> >> (ref
> >> http://support.microsoft.com/kb/102873/EN-US/#XSLTH3189121121120121120120)
> >>
> >>
> >> With both disks connected, the system will boot from the floppy with
> >> the boot.ini as shown imediately above, but guess what?...with disk0
> >> disconnected, the system will not boot to Windows. During the boot
> >> process, the system detects that disk0 is missing, requests f1 to
> >> continue and then delivers the message:
> >>
> >> Windows 2000 could not be started because of a hardware problem.
> >> Could not read from selected boot disk.
> >>
> >>
> >> I tried the following variations ot the 'mirro' entry in the boot.ini,
> >> but it made no difference:
> >>
> >> multi(0)disk(1)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
> >> Server" /fastdetect
> >> and
> >> multi(0)disk(0)rdisk(1)partition(2)\WINNT="Microsoft Windows 2000
> >> Server" /fastdetect
> >>
> >> Have also changes disk jumpers to set drives to 'cable selct', but this
> >> alos makes no difference
> >>
> >>
> >> So, I must be doing domething wrong somewhere. I've found conflicting
> >> advice on this subject, can anybody help ?
> >>
> >> Should both drives be connected to the same IDE channel?
> >>
> >> Is there a trick related to creating a MBR on the mirror disk prior to
> >> the mirroring process? If so, how is this done reliably?
> >>
> >> Any help greatly appreciated.
> >
>
>
>
.

Relevant Pages

  • slackware 9.1 software raid problem
    ... Setting up a RAID system with Slackware 8 is not extremely difficult once ... mirroring the root partition and booting from that mirror was not possible. ... Each disk is attached to a different IDE chain on the motherboard. ... The ability to boot from the Slackware 8 install CD. ...
    (alt.os.linux)
  • Re: RAID Problem after restore
    ... I understand that your SBS Adaptec RAID ... the Adaptec RAID (mirror) configuration information ... disk 1 is the disk on which the image of disk 0 will be ...
    (microsoft.public.windows.server.sbs)
  • [HPADM] Summary MirrorDisk/UX 11.00
    ... disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE HP 73.4GMAN3735MC ... Use mkboot to place the boot utilities in the boot area and add the AUTO file. ... LVM will resynchronize the new mirror copies. ... All you need to do is ftp it to your server, chmod 700 on the file then run the command with the cxtxdx name ...
    (HP-UX-Admin)
  • RE: RAID Problem after restore
    ... I understand that your SBS Adaptec RAID ... the Adaptec RAID (mirror) configuration information ... disk 1 is the disk on which the image of disk 0 will be ...
    (microsoft.public.windows.server.sbs)
  • Re: cant boot from mirrored boot drive
    ... If the disk containing the primary partition fails you will have to create a fault tolerant boot floppy to recover the installation. ... 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? ... They are sata drives, drive 0 and drive 1 on the main system board's controller. ...
    (microsoft.public.windows.server.general)