Jump to content

Windows 2003 Mirror and Boot Partition

Guest Smurfman

By Guest Smurfman
in Windows 2003 Server

 Share

Recommended Posts

Guest Smurfman

Guest Smurfman

Posted
Posted

I created a mess for myself by doing the following:

 

On a system with 2 18GB mirrored drives there was a windows 2000 server

install.

SCSI ID 0

SCSI ID 1

 

I wanted to install windows 2003 on a fresh pair of SCSI Drives

SCSI ID 4

SCSI ID 5

 

So I booted to my windows 2003 server, standard CD rom and proceeded to

perform a fresh install of W2K3 on SCSI ID 4 a new 73 GB drive.

 

The install went great, created my mirror set (soft mirror)

 

*** I went wrong by leaving the original SCSI drives in place, since the

boot info was written there (boot.ini) ntldr, and ntdetect.com

 

So I thought, hey no problem, copy the files, modify the boot.ini to include

my drives at SCSI ID 0 adn SCSI ID 1 and reboot.

 

Can't reboot - figured I must be missing a partition table entry MBR or

something.

 

I read a KB article to use Recovery Console and the fixboot tool.

 

I did this, it created a boot ini for the locaiton etc etc.

 

Rebooted - still can't boot.

 

I put all the drives back to where they below, now the primary mirror can't

boot, but the "secondary plex" as was in the boot.ini

 

I rebooted also tried the recovery console and the fixmbr

 

This did not make a difference...

 

-- So the long and short of things is that I have a machine that has all the

boot info on the SCSI ID 0 (drive letter g:) and a boot.ini that points SCSI

ID 4 and SCSI ID 5

 

-- SCSI ID 4 - can't boot - I figure it is still missing a partition table

entry for the OS

-- SCSI ID 5 - boots just fine

 

??? - How can I remove the old 18GB drive from the system, move the drive

pair at SCSI ID 4 adn SCSI ID 5 to slots 0 and 1 and rebuild the boot info to

boot to the drives with out needing the old drive for booting?

 

Thanks

J

  • Replies 5
  • Created
  • Last Reply

Popular Days

Popular Days

Guest Smurfman

Guest Smurfman

Posted
Posted

RE: Windows 2003 Mirror and Boot Partition

 

I have managed to get rid of the old 18GB drives and have the system booting

on the two new drives. I found a tool to re-create the boot partition table

so SCSI ID 0 is now able to boot on its own. SCSI ID 1 was the mirror but is

now broken.

 

I can boot to either disk using the boot ini that was created with bootcfg

 

However, Disk Admin reports the disk as follows:

 

Disk0 (SCSI ID 0) F: (System) rest of the disk is unformated.

 

Disk1 (SCSI ID 1) C: (Boot) D: (Paging File)

 

Since F is assigned to this system drive I can't delete it, or change the

drive letter which hoses up a network drive.

 

At this point my mirror does not exist.

 

I read in a KB that I could move the mirror drive to SCSI ID 0 and boot with

a FT Disk pinting to that drive - then delete the other partition (F:) and

recreate my mirror set. Along the way I could active the moved mirrored

drive to allow it boot with out a FT disk.

 

Well, I can't delete the F drive - all that happens is that the Disk0 shows

as C: (Boot) D: (Paging File) and then Disk1 is F: (System)

 

I can't activate the moved drive to be the boot device, and thus am required

to keep the FT Disk in the floppy drive to boot to my SCSI ID 0 drive - disk0.

 

I can remove the the drive reporting as F: and boot from the floppy and

everthing works just like it is supposed to even the F drive is mapped the

proper network drive that would not connect earlier.

 

So...

1) I have a disk in SCSI ID 0 now that Ideally I would like to make bootable

instead of using a FT Boot Disk.

 

2) I would also like to delete any reference to this other system disk.

 

Even booting without the disk physically present in the server, Disk Admin

still shows that the missing volume is (system) - attempting to delete it

generates an error telling me I can't delete the system disk.

 

Please help...!

 

My thought process was - why not just make the disk I booted to bootable on

its own, delete the other disk and recreate the whole mirror set and

everything.

 

J

 

 

 

 

"Smurfman" wrote:

> I created a mess for myself by doing the following:

>

> On a system with 2 18GB mirrored drives there was a windows 2000 server

> install.

> SCSI ID 0

> SCSI ID 1

>

> I wanted to install windows 2003 on a fresh pair of SCSI Drives

> SCSI ID 4

> SCSI ID 5

>

> So I booted to my windows 2003 server, standard CD rom and proceeded to

> perform a fresh install of W2K3 on SCSI ID 4 a new 73 GB drive.

>

> The install went great, created my mirror set (soft mirror)

>

> *** I went wrong by leaving the original SCSI drives in place, since the

> boot info was written there (boot.ini) ntldr, and ntdetect.com

>

> So I thought, hey no problem, copy the files, modify the boot.ini to include

> my drives at SCSI ID 0 adn SCSI ID 1 and reboot.

>

> Can't reboot - figured I must be missing a partition table entry MBR or

> something.

>

> I read a KB article to use Recovery Console and the fixboot tool.

>

> I did this, it created a boot ini for the locaiton etc etc.

>

> Rebooted - still can't boot.

>

> I put all the drives back to where they below, now the primary mirror can't

> boot, but the "secondary plex" as was in the boot.ini

>

> I rebooted also tried the recovery console and the fixmbr

>

> This did not make a difference...

>

> -- So the long and short of things is that I have a machine that has all the

> boot info on the SCSI ID 0 (drive letter g:) and a boot.ini that points SCSI

> ID 4 and SCSI ID 5

>

> -- SCSI ID 4 - can't boot - I figure it is still missing a partition table

> entry for the OS

> -- SCSI ID 5 - boots just fine

>

> ??? - How can I remove the old 18GB drive from the system, move the drive

> pair at SCSI ID 4 adn SCSI ID 5 to slots 0 and 1 and rebuild the boot info to

> boot to the drives with out needing the old drive for booting?

>

> Thanks

> J

Guest Ken Zhao [MSFT]

Guest Ken Zhao [MSFT]

Posted
Posted

RE: Windows 2003 Mirror and Boot Partition

 

Hello,

 

Thank you for using newsgroup!

 

For your complex hardware disk situation, I cannot reproduce your scenario.

I am not sure if the following article might be helpful:

323432: How to mirror the system and boot partition (RAID1) in Windows

Server 2003

http://support.microsoft.com/kb/323432/en-us

 

Thanks & Regards,

 

Ken Zhao

 

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://www.microsoft.com/security <http://www.microsoft.com/security>

====================================================

When responding to posts, please "Reply to Group" via your newsreader so

that others may learn and benefit from your issue.

====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

 

 

 

--------------------

| Thread-Topic: Windows 2003 Mirror and Boot Partition

| thread-index: AcfwwRQARfootbaOTVSPiW3V+rt7fQ==

| X-WBNR-Posting-Host: 207.46.192.207

| From: =?Utf-8?B?U211cmZtYW4=?= <smurfman@news.postalias>

| References: <C73E7C0C-74F6-44E5-B91C-E7C5E787C76F@microsoft.com>

| Subject: RE: Windows 2003 Mirror and Boot Partition

| Date: Thu, 6 Sep 2007 13:04:05 -0700

| Lines: 108

| Message-ID: <877C56CF-390E-4983-B228-4A321C94017B@microsoft.com>

| MIME-Version: 1.0

| Content-Type: text/plain;

| charset="Utf-8"

| Content-Transfer-Encoding: 7bit

| X-Newsreader: Microsoft CDO for Windows 2000

| Content-Class: urn:content-classes:message

| Importance: normal

| Priority: normal

| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826

| Newsgroups: microsoft.public.windows.server.general

| Path: TK2MSFTNGHUB02.phx.gbl

| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.general:21580

| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148

| X-Tomcat-NG: microsoft.public.windows.server.general

|

| I have managed to get rid of the old 18GB drives and have the system

booting

| on the two new drives. I found a tool to re-create the boot partition

table

| so SCSI ID 0 is now able to boot on its own. SCSI ID 1 was the mirror

but is

| now broken.

|

| I can boot to either disk using the boot ini that was created with bootcfg

|

| However, Disk Admin reports the disk as follows:

|

| Disk0 (SCSI ID 0) F: (System) rest of the disk is unformated.

|

| Disk1 (SCSI ID 1) C: (Boot) D: (Paging File)

|

| Since F is assigned to this system drive I can't delete it, or change the

| drive letter which hoses up a network drive.

|

| At this point my mirror does not exist.

|

| I read in a KB that I could move the mirror drive to SCSI ID 0 and boot

with

| a FT Disk pinting to that drive - then delete the other partition (F:)

and

| recreate my mirror set. Along the way I could active the moved mirrored

| drive to allow it boot with out a FT disk.

|

| Well, I can't delete the F drive - all that happens is that the Disk0

shows

| as C: (Boot) D: (Paging File) and then Disk1 is F: (System)

|

| I can't activate the moved drive to be the boot device, and thus am

required

| to keep the FT Disk in the floppy drive to boot to my SCSI ID 0 drive -

disk0.

|

| I can remove the the drive reporting as F: and boot from the floppy and

| everthing works just like it is supposed to even the F drive is mapped

the

| proper network drive that would not connect earlier.

|

| So...

| 1) I have a disk in SCSI ID 0 now that Ideally I would like to make

bootable

| instead of using a FT Boot Disk.

|

| 2) I would also like to delete any reference to this other system disk.

|

| Even booting without the disk physically present in the server, Disk

Admin

| still shows that the missing volume is (system) - attempting to delete it

| generates an error telling me I can't delete the system disk.

|

| Please help...!

|

| My thought process was - why not just make the disk I booted to bootable

on

| its own, delete the other disk and recreate the whole mirror set and

| everything.

|

| J

|

|

|

|

| "Smurfman" wrote:

|

| > I created a mess for myself by doing the following:

| >

| > On a system with 2 18GB mirrored drives there was a windows 2000 server

| > install.

| > SCSI ID 0

| > SCSI ID 1

| >

| > I wanted to install windows 2003 on a fresh pair of SCSI Drives

| > SCSI ID 4

| > SCSI ID 5

| >

| > So I booted to my windows 2003 server, standard CD rom and proceeded to

| > perform a fresh install of W2K3 on SCSI ID 4 a new 73 GB drive.

| >

| > The install went great, created my mirror set (soft mirror)

| >

| > *** I went wrong by leaving the original SCSI drives in place, since

the

| > boot info was written there (boot.ini) ntldr, and ntdetect.com

| >

| > So I thought, hey no problem, copy the files, modify the boot.ini to

include

| > my drives at SCSI ID 0 adn SCSI ID 1 and reboot.

| >

| > Can't reboot - figured I must be missing a partition table entry MBR or

| > something.

| >

| > I read a KB article to use Recovery Console and the fixboot tool.

| >

| > I did this, it created a boot ini for the locaiton etc etc.

| >

| > Rebooted - still can't boot.

| >

| > I put all the drives back to where they below, now the primary mirror

can't

| > boot, but the "secondary plex" as was in the boot.ini

| >

| > I rebooted also tried the recovery console and the fixmbr

| >

| > This did not make a difference...

| >

| > -- So the long and short of things is that I have a machine that has

all the

| > boot info on the SCSI ID 0 (drive letter g:) and a boot.ini that points

SCSI

| > ID 4 and SCSI ID 5

| >

| > -- SCSI ID 4 - can't boot - I figure it is still missing a partition

table

| > entry for the OS

| > -- SCSI ID 5 - boots just fine

| >

| > ??? - How can I remove the old 18GB drive from the system, move the

drive

| > pair at SCSI ID 4 adn SCSI ID 5 to slots 0 and 1 and rebuild the boot

info to

| > boot to the drives with out needing the old drive for booting?

| >

| > Thanks

| > J

|

Guest John John

Guest John John

Posted
Posted

Re: Windows 2003 Mirror and Boot Partition

 

The best thing to do with that mess is blow everything off of it and

start again from scratch. Being that it is a new installation there is

nothing lost other than the time that was spent setting up what turned

to be a less than perfect installation.

 

John

 

Smurfman wrote:

> I have managed to get rid of the old 18GB drives and have the system booting

> on the two new drives. I found a tool to re-create the boot partition table

> so SCSI ID 0 is now able to boot on its own. SCSI ID 1 was the mirror but is

> now broken.

>

> I can boot to either disk using the boot ini that was created with bootcfg

>

> However, Disk Admin reports the disk as follows:

>

> Disk0 (SCSI ID 0) F: (System) rest of the disk is unformated.

>

> Disk1 (SCSI ID 1) C: (Boot) D: (Paging File)

>

> Since F is assigned to this system drive I can't delete it, or change the

> drive letter which hoses up a network drive.

>

> At this point my mirror does not exist.

>

> I read in a KB that I could move the mirror drive to SCSI ID 0 and boot with

> a FT Disk pinting to that drive - then delete the other partition (F:) and

> recreate my mirror set. Along the way I could active the moved mirrored

> drive to allow it boot with out a FT disk.

>

> Well, I can't delete the F drive - all that happens is that the Disk0 shows

> as C: (Boot) D: (Paging File) and then Disk1 is F: (System)

>

> I can't activate the moved drive to be the boot device, and thus am required

> to keep the FT Disk in the floppy drive to boot to my SCSI ID 0 drive - disk0.

>

> I can remove the the drive reporting as F: and boot from the floppy and

> everthing works just like it is supposed to even the F drive is mapped the

> proper network drive that would not connect earlier.

>

> So...

> 1) I have a disk in SCSI ID 0 now that Ideally I would like to make bootable

> instead of using a FT Boot Disk.

>

> 2) I would also like to delete any reference to this other system disk.

>

> Even booting without the disk physically present in the server, Disk Admin

> still shows that the missing volume is (system) - attempting to delete it

> generates an error telling me I can't delete the system disk.

>

> Please help...!

>

> My thought process was - why not just make the disk I booted to bootable on

> its own, delete the other disk and recreate the whole mirror set and

> everything.

>

> J

>

>

>

>

> "Smurfman" wrote:

>

>

>>I created a mess for myself by doing the following:

>>

>>On a system with 2 18GB mirrored drives there was a windows 2000 server

>>install.

>>SCSI ID 0

>>SCSI ID 1

>>

>>I wanted to install windows 2003 on a fresh pair of SCSI Drives

>>SCSI ID 4

>>SCSI ID 5

>>

>>So I booted to my windows 2003 server, standard CD rom and proceeded to

>>perform a fresh install of W2K3 on SCSI ID 4 a new 73 GB drive.

>>

>>The install went great, created my mirror set (soft mirror)

>>

>>*** I went wrong by leaving the original SCSI drives in place, since the

>>boot info was written there (boot.ini) ntldr, and ntdetect.com

>>

>>So I thought, hey no problem, copy the files, modify the boot.ini to include

>>my drives at SCSI ID 0 adn SCSI ID 1 and reboot.

>>

>>Can't reboot - figured I must be missing a partition table entry MBR or

>>something.

>>

>>I read a KB article to use Recovery Console and the fixboot tool.

>>

>>I did this, it created a boot ini for the locaiton etc etc.

>>

>>Rebooted - still can't boot.

>>

>>I put all the drives back to where they below, now the primary mirror can't

>>boot, but the "secondary plex" as was in the boot.ini

>>

>>I rebooted also tried the recovery console and the fixmbr

>>

>>This did not make a difference...

>>

>>-- So the long and short of things is that I have a machine that has all the

>>boot info on the SCSI ID 0 (drive letter g:) and a boot.ini that points SCSI

>>ID 4 and SCSI ID 5

>>

>>-- SCSI ID 4 - can't boot - I figure it is still missing a partition table

>>entry for the OS

>>-- SCSI ID 5 - boots just fine

>>

>>??? - How can I remove the old 18GB drive from the system, move the drive

>>pair at SCSI ID 4 adn SCSI ID 5 to slots 0 and 1 and rebuild the boot info to

>>boot to the drives with out needing the old drive for booting?

>>

>>Thanks

>>J

Guest Smurfman

Guest Smurfman

Posted
Posted

Re: Windows 2003 Mirror and Boot Partition

 

I think I got it...

 

I used a tool called TestDisk that searched the mirror drive and created the

partition table entries I needed and set the drive to the active boot drive.

 

I read on another KB that I might have been able to use FDisk to set the

drive as active. This was my issue.

 

Once I was able to set the drive as active, I could boot without the FT

disk, and the drive letters we correct.

 

The one thing I noted was that the disk was reverted back to basic from

dynamic, so it appears that I am back to a single disk and ready to recreate

my mirrors.

 

Believe me for the time I thought of just starting over, but I was still

using the system for current daily work, as this was not a test machine that

broke but a production machine and also did not want to lose my days work...

that was most important.

 

THanks guys.

 

J

 

"John John" wrote:

> The best thing to do with that mess is blow everything off of it and

> start again from scratch. Being that it is a new installation there is

> nothing lost other than the time that was spent setting up what turned

> to be a less than perfect installation.

>

> John

>

> Smurfman wrote:

> > I have managed to get rid of the old 18GB drives and have the system booting

> > on the two new drives. I found a tool to re-create the boot partition table

> > so SCSI ID 0 is now able to boot on its own. SCSI ID 1 was the mirror but is

> > now broken.

> >

> > I can boot to either disk using the boot ini that was created with bootcfg

> >

> > However, Disk Admin reports the disk as follows:

> >

> > Disk0 (SCSI ID 0) F: (System) rest of the disk is unformated.

> >

> > Disk1 (SCSI ID 1) C: (Boot) D: (Paging File)

> >

> > Since F is assigned to this system drive I can't delete it, or change the

> > drive letter which hoses up a network drive.

> >

> > At this point my mirror does not exist.

> >

> > I read in a KB that I could move the mirror drive to SCSI ID 0 and boot with

> > a FT Disk pinting to that drive - then delete the other partition (F:) and

> > recreate my mirror set. Along the way I could active the moved mirrored

> > drive to allow it boot with out a FT disk.

> >

> > Well, I can't delete the F drive - all that happens is that the Disk0 shows

> > as C: (Boot) D: (Paging File) and then Disk1 is F: (System)

> >

> > I can't activate the moved drive to be the boot device, and thus am required

> > to keep the FT Disk in the floppy drive to boot to my SCSI ID 0 drive - disk0.

> >

> > I can remove the the drive reporting as F: and boot from the floppy and

> > everthing works just like it is supposed to even the F drive is mapped the

> > proper network drive that would not connect earlier.

> >

> > So...

> > 1) I have a disk in SCSI ID 0 now that Ideally I would like to make bootable

> > instead of using a FT Boot Disk.

> >

> > 2) I would also like to delete any reference to this other system disk.

> >

> > Even booting without the disk physically present in the server, Disk Admin

> > still shows that the missing volume is (system) - attempting to delete it

> > generates an error telling me I can't delete the system disk.

> >

> > Please help...!

> >

> > My thought process was - why not just make the disk I booted to bootable on

> > its own, delete the other disk and recreate the whole mirror set and

> > everything.

> >

> > J

> >

> >

> >

> >

> > "Smurfman" wrote:

> >

> >

> >>I created a mess for myself by doing the following:

> >>

> >>On a system with 2 18GB mirrored drives there was a windows 2000 server

> >>install.

> >>SCSI ID 0

> >>SCSI ID 1

> >>

> >>I wanted to install windows 2003 on a fresh pair of SCSI Drives

> >>SCSI ID 4

> >>SCSI ID 5

> >>

> >>So I booted to my windows 2003 server, standard CD rom and proceeded to

> >>perform a fresh install of W2K3 on SCSI ID 4 a new 73 GB drive.

> >>

> >>The install went great, created my mirror set (soft mirror)

> >>

> >>*** I went wrong by leaving the original SCSI drives in place, since the

> >>boot info was written there (boot.ini) ntldr, and ntdetect.com

> >>

> >>So I thought, hey no problem, copy the files, modify the boot.ini to include

> >>my drives at SCSI ID 0 adn SCSI ID 1 and reboot.

> >>

> >>Can't reboot - figured I must be missing a partition table entry MBR or

> >>something.

> >>

> >>I read a KB article to use Recovery Console and the fixboot tool.

> >>

> >>I did this, it created a boot ini for the locaiton etc etc.

> >>

> >>Rebooted - still can't boot.

> >>

> >>I put all the drives back to where they below, now the primary mirror can't

> >>boot, but the "secondary plex" as was in the boot.ini

> >>

> >>I rebooted also tried the recovery console and the fixmbr

> >>

> >>This did not make a difference...

> >>

> >>-- So the long and short of things is that I have a machine that has all the

> >>boot info on the SCSI ID 0 (drive letter g:) and a boot.ini that points SCSI

> >>ID 4 and SCSI ID 5

> >>

> >>-- SCSI ID 4 - can't boot - I figure it is still missing a partition table

> >>entry for the OS

> >>-- SCSI ID 5 - boots just fine

> >>

> >>??? - How can I remove the old 18GB drive from the system, move the drive

> >>pair at SCSI ID 4 adn SCSI ID 5 to slots 0 and 1 and rebuild the boot info to

> >>boot to the drives with out needing the old drive for booting?

> >>

> >>Thanks

> >>J

>

Guest Ken Zhao [MSFT]

Guest Ken Zhao [MSFT]

Posted
Posted

Re: Windows 2003 Mirror and Boot Partition

 

Hello Jeff,

 

Thanks for your reply and let us know you have used a tool called TestDisk

to recreate the partition table. I believe this info will benefit other

customers who encounter this similar issue.

 

If you have any other questions, please feel free to contact us.

 

Thanks & Regards,

 

Ken Zhao

 

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://www.microsoft.com/security <http://www.microsoft.com/security>

====================================================

When responding to posts, please "Reply to Group" via your newsreader so

that others may learn and benefit from your issue.

====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

 

 

 

--------------------

| Thread-Topic: Windows 2003 Mirror and Boot Partition

| thread-index: AcfxT5Eo8pYJct30SP221b6++d3xGw==

| X-WBNR-Posting-Host: 207.46.19.168

| From: =?Utf-8?B?U211cmZtYW4=?= <smurfman@news.postalias>

| References: <C73E7C0C-74F6-44E5-B91C-E7C5E787C76F@microsoft.com>

<877C56CF-390E-4983-B228-4A321C94017B@microsoft.com>

<#zlF#pU8HHA.5752@TK2MSFTNGP04.phx.gbl>

| Subject: Re: Windows 2003 Mirror and Boot Partition

| Date: Fri, 7 Sep 2007 06:04:04 -0700

| Lines: 144

| Message-ID: <0A60BC92-998F-41A8-B24E-C89C0EC4E5C1@microsoft.com>

| MIME-Version: 1.0

| Content-Type: text/plain;

| charset="Utf-8"

| Content-Transfer-Encoding: 7bit

| X-Newsreader: Microsoft CDO for Windows 2000

| Content-Class: urn:content-classes:message

| Importance: normal

| Priority: normal

| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826

| Newsgroups: microsoft.public.windows.server.general

| Path: TK2MSFTNGHUB02.phx.gbl

| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.general:21622

| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148

| X-Tomcat-NG: microsoft.public.windows.server.general

|

| I think I got it...

|

| I used a tool called TestDisk that searched the mirror drive and created

the

| partition table entries I needed and set the drive to the active boot

drive.

|

| I read on another KB that I might have been able to use FDisk to set the

| drive as active. This was my issue.

|

| Once I was able to set the drive as active, I could boot without the FT

| disk, and the drive letters we correct.

|

| The one thing I noted was that the disk was reverted back to basic from

| dynamic, so it appears that I am back to a single disk and ready to

recreate

| my mirrors.

|

| Believe me for the time I thought of just starting over, but I was still

| using the system for current daily work, as this was not a test machine

that

| broke but a production machine and also did not want to lose my days

work...

| that was most important.

|

| THanks guys.

|

| J

|

| "John John" wrote:

|

| > The best thing to do with that mess is blow everything off of it and

| > start again from scratch. Being that it is a new installation there is

| > nothing lost other than the time that was spent setting up what turned

| > to be a less than perfect installation.

| >

| > John

| >

| > Smurfman wrote:

| > > I have managed to get rid of the old 18GB drives and have the system

booting

| > > on the two new drives. I found a tool to re-create the boot

partition table

| > > so SCSI ID 0 is now able to boot on its own. SCSI ID 1 was the

mirror but is

| > > now broken.

| > >

| > > I can boot to either disk using the boot ini that was created with

bootcfg

| > >

| > > However, Disk Admin reports the disk as follows:

| > >

| > > Disk0 (SCSI ID 0) F: (System) rest of the disk is unformated.

| > >

| > > Disk1 (SCSI ID 1) C: (Boot) D: (Paging File)

| > >

| > > Since F is assigned to this system drive I can't delete it, or change

the

| > > drive letter which hoses up a network drive.

| > >

| > > At this point my mirror does not exist.

| > >

| > > I read in a KB that I could move the mirror drive to SCSI ID 0 and

boot with

| > > a FT Disk pinting to that drive - then delete the other partition

(F:) and

| > > recreate my mirror set. Along the way I could active the moved

mirrored

| > > drive to allow it boot with out a FT disk.

| > >

| > > Well, I can't delete the F drive - all that happens is that the Disk0

shows

| > > as C: (Boot) D: (Paging File) and then Disk1 is F: (System)

| > >

| > > I can't activate the moved drive to be the boot device, and thus am

required

| > > to keep the FT Disk in the floppy drive to boot to my SCSI ID 0 drive

- disk0.

| > >

| > > I can remove the the drive reporting as F: and boot from the floppy

and

| > > everthing works just like it is supposed to even the F drive is

mapped the

| > > proper network drive that would not connect earlier.

| > >

| > > So...

| > > 1) I have a disk in SCSI ID 0 now that Ideally I would like to make

bootable

| > > instead of using a FT Boot Disk.

| > >

| > > 2) I would also like to delete any reference to this other system

disk.

| > >

| > > Even booting without the disk physically present in the server, Disk

Admin

| > > still shows that the missing volume is (system) - attempting to

delete it

| > > generates an error telling me I can't delete the system disk.

| > >

| > > Please help...!

| > >

| > > My thought process was - why not just make the disk I booted to

bootable on

| > > its own, delete the other disk and recreate the whole mirror set and

| > > everything.

| > >

| > > J

| > >

| > >

| > >

| > >

| > > "Smurfman" wrote:

| > >

| > >

| > >>I created a mess for myself by doing the following:

| > >>

| > >>On a system with 2 18GB mirrored drives there was a windows 2000

server

| > >>install.

| > >>SCSI ID 0

| > >>SCSI ID 1

| > >>

| > >>I wanted to install windows 2003 on a fresh pair of SCSI Drives

| > >>SCSI ID 4

| > >>SCSI ID 5

| > >>

| > >>So I booted to my windows 2003 server, standard CD rom and proceeded

to

| > >>perform a fresh install of W2K3 on SCSI ID 4 a new 73 GB drive.

| > >>

| > >>The install went great, created my mirror set (soft mirror)

| > >>

| > >>*** I went wrong by leaving the original SCSI drives in place, since

the

| > >>boot info was written there (boot.ini) ntldr, and ntdetect.com

| > >>

| > >>So I thought, hey no problem, copy the files, modify the boot.ini to

include

| > >>my drives at SCSI ID 0 adn SCSI ID 1 and reboot.

| > >>

| > >>Can't reboot - figured I must be missing a partition table entry MBR

or

| > >>something.

| > >>

| > >>I read a KB article to use Recovery Console and the fixboot tool.

| > >>

| > >>I did this, it created a boot ini for the locaiton etc etc.

| > >>

| > >>Rebooted - still can't boot.

| > >>

| > >>I put all the drives back to where they below, now the primary mirror

can't

| > >>boot, but the "secondary plex" as was in the boot.ini

| > >>

| > >>I rebooted also tried the recovery console and the fixmbr

| > >>

| > >>This did not make a difference...

| > >>

| > >>-- So the long and short of things is that I have a machine that has

all the

| > >>boot info on the SCSI ID 0 (drive letter g:) and a boot.ini that

points SCSI

| > >>ID 4 and SCSI ID 5

| > >>

| > >>-- SCSI ID 4 - can't boot - I figure it is still missing a partition

table

| > >>entry for the OS

| > >>-- SCSI ID 5 - boots just fine

| > >>

| > >>??? - How can I remove the old 18GB drive from the system, move the

drive

| > >>pair at SCSI ID 4 adn SCSI ID 5 to slots 0 and 1 and rebuild the boot

info to

| > >>boot to the drives with out needing the old drive for booting?

| > >>

| > >>Thanks

| > >>J

| >

|

 Share
Go to topic listing
×
×
  • Create New...