Re: Making mirror disk bootable

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


"DanaK" <DanaK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1F229F98-0019-4308-9A59-E97F42446936@xxxxxxxxxxxxxxxx
I'm trying to preform an upgrade from W2K Server, sp4 to W2K3 Server.
Currently I'm booting to the mirrored disk of my server as the primary
disk
developed bad spots and has been replaced by a new one. I've been told
that
all I need to do in order to make the mirror disk bootable is copy the
files
from the boot disk to the root of the "new" C: drive but this doesn't
work.
When I'm running the upgrade wizard for W2K3 server it trys to reboot but
can't. I see that the boot.ini file on the root of my C: drive has been
altered by the wizard to access the setup files the upgrade wizard put on
my
hard drive but when I put the boot.ini file on my boot floppy disk I get
the
notice that W2K can't boot as it can't find the file ntoskrnl.exe in the
\system32 folder. I've looked and the file is, indeed, there and doesn't
appear to be damaged.

What do I need to get the ball rolling on this upgrade and get back to a
bootable C: drive?

Thanks to anyone's answer in advance.
Dana

fixboot and fixmbr will not work because a mirror disk uses a
disk partition type that is not bootable. You can do it like so:

1. Connect the mirror (=source) and the replacement disk (=target)
to the secondary IDE controller of some Win2000/XP PC.
2. Format the target.
3. Use xcopy.exe to copy the source to the target. Select the
appropriate switches so that hidden files, system files,
attributes and permissions are copied too.
4. Make sure the target disk contains ntdetec.com, ntldr and
boot.ini.
5. Boot the server with only the target connected.
6. If all is well, restore the mirror.

This is a completely safe method because it does not alter
the mirror disk in any way until Step 6.


.

Relevant Pages

  • Re: informix and SAN snapshot
    ... If you are doing a Symmetrix sync you are pushing bits from prod to the other servers' disks, thusly you will need to shut down your target db or there will be corruption. ... You just the leave the disk copy intact, maybe refreshing it nightly, for years on end without ever pointing a server at it *except* when you need to use it. ...
    (comp.databases.informix)
  • 2.6 to 8 upgrade, copy boot disk, device issues
    ... I'm attempting to upgrade a couple of servers from 2.6 to 8, ... The Solaris 8 disk image on the source server is not the active boot device, ... path_to_inst was restored to the target disk. ...
    (comp.unix.solaris)
  • Re: Mirroring Boot disk problems using VxVM
    ... The best way for start point of root slice in a encaspulated volume like a rootvol, is start from cylinder 2 because with cyl 0 and 1 VxVM can protect the block zero. ... Private region must to be start at start of the disk, vxvm when have a root slice that don't start from cyl 2, create a little volume called rootdiskPriv and a subdisk called "rootdisk-B0". ... I see that the disk 2 is a mirror disk because after encapsulation veritas can't modify the partition table, but can when you mirror a disk with vxdiskadm command. ...
    (comp.sys.sun.admin)
  • SUMMARY: Replacing disks in DiskSuite
    ... As we use ufsdump to back up the disk I decided the quickest and easiest way ... Brought the primary disk partitions into SDS and then created the mirrors. ... > Subject: Replacing disks in DiskSuite ... > Remove and replace the mirror disk ...
    (SunManagers)
  • Registry File Failure BSOD after RAID repair
    ... SBS2K with Adaptec 1200A IDE RAID 1 ... After replacing a failed disk, the RAID 1 duplicated the info to the new ... mirror disk from the existing survivor. ...
    (microsoft.public.backoffice.smallbiz2000)