Win 2003 Dynamic Disk Issue

We are trying to setup a test server matching a clients existing
configuration but are having problems. The client has Windows 2003 Server Std
on IDE Dynamic disks with Windows Software mirror.

The problem is that after installing the operating system onto a newly
created partition on Disk0 we convert to dynamic disk and re boot.

System fails to boot with the message "NTLDR is missing"

Running recovery consol and using the map command would seem to indicate the
reason for this issue as it shows no drive letter assigned to the boot drive,
there is just a question mark.

Any help appreciated.

Geoff

You might also try creating a boot disk. For the floppy to successfully boot
Windows 2003 the disk must contain the "NT" boot sector. Format a diskette
(on a Windows 2003 machine, not a DOS/Win9x, so the NT boot sector gets
written to the floppy), and copy Windows 2003 versions of ntldr,
ntdetect.com, and boot.ini to it. Edit the boot.ini to give it a correct ARC
path for the machine you wish to boot. Below is an example of boot.ini. The
default is to start the operating system located on the first partition of
the primary or first drive (drive0). Then drive0 partition 2 and so on.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\Window s
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\Windows="Windo ws 2003 0,1"
multi(0)disk(0)rdisk(0)partition(2)\Windows="Windo ws 2003 0,2"
multi(0)disk(0)rdisk(1)partition(1)\Windows="Windo ws 2003 1,1"
multi(0)disk(0)rdisk(1)partition(2)\Windows="Windo ws 2003 1,2"


Another possibility is to try loading the controller driver also from
floppy. For the floppy to successfully boot Windows 2003 the disk must
contain the "NT" boot sector. Format a diskette (on a Windows 2003 machine,
not a DOS/Win9x, so the "NT" boot sector gets written to the floppy), then
copy ntldr, ntdetect.com, and boot.ini to it. Edit the boot.ini to give it a
correct ARC path for the machine you wish to boot.

In order for this to work you'll want to change the arc path in boot.ini
from multi syntax to scsi syntax to indicate that Windows 2003 will load a
boot device driver and use that driver to access the boot partition. Then
also copy the correct manufacturer scsi driver to the floppy but renamed to
ntbootdd.sys

Something like this below;

[boot loader]
timeout=10
default=scsi(0)disk(0)rdisk(0)partition(1)\Windows
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\Windows="Window s 2003 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\Windows="Window s 2003 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\Windows="Window s 2003 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\Windows="Window s 2003 1,2"


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"Geoff" wrote:
> We are trying to setup a test server matching a clients existing
> configuration but are having problems. The client has Windows 2003 Server
> Std
> on IDE Dynamic disks with Windows Software mirror.
>
> The problem is that after installing the operating system onto a newly
> created partition on Disk0 we convert to dynamic disk and re boot.
>
> System fails to boot with the message "NTLDR is missing"
>
> Running recovery consol and using the map command would seem to indicate
> the
> reason for this issue as it shows no drive letter assigned to the boot
> drive,
> there is just a question mark.
>
> Any help appreciated.
>
> Geoff
>

Dave,

Thanks for the input but I was looking for a reason rather than a
workaround. Although we would not run software raid in real world I have used
it before and have not had this issue.

I have rebiult the server a couple of times since the orginal failure trying
different things and have noticed that after conversion we get a message
Windows is dismounting, dos that sound correct?

It looks to me as though windows dismounts the volume and then fails to
remount causing the boot failure and lcak of drive letter.

Geoff

"Dave Patrick" wrote:

> You might also try creating a boot disk. For the floppy to successfully boot
> Windows 2003 the disk must contain the "NT" boot sector. Format a diskette
> (on a Windows 2003 machine, not a DOS/Win9x, so the NT boot sector gets
> written to the floppy), and copy Windows 2003 versions of ntldr,
> ntdetect.com, and boot.ini to it. Edit the boot.ini to give it a correct ARC
> path for the machine you wish to boot. Below is an example of boot.ini. The
> default is to start the operating system located on the first partition of
> the primary or first drive (drive0). Then drive0 partition 2 and so on.
>
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\Window s
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\Windows="Windo ws 2003 0,1"
> multi(0)disk(0)rdisk(0)partition(2)\Windows="Windo ws 2003 0,2"
> multi(0)disk(0)rdisk(1)partition(1)\Windows="Windo ws 2003 1,1"
> multi(0)disk(0)rdisk(1)partition(2)\Windows="Windo ws 2003 1,2"
>
>
> Another possibility is to try loading the controller driver also from
> floppy. For the floppy to successfully boot Windows 2003 the disk must
> contain the "NT" boot sector. Format a diskette (on a Windows 2003 machine,
> not a DOS/Win9x, so the "NT" boot sector gets written to the floppy), then
> copy ntldr, ntdetect.com, and boot.ini to it. Edit the boot.ini to give it a
> correct ARC path for the machine you wish to boot.
>
> In order for this to work you'll want to change the arc path in boot.ini
> from multi syntax to scsi syntax to indicate that Windows 2003 will load a
> boot device driver and use that driver to access the boot partition. Then
> also copy the correct manufacturer scsi driver to the floppy but renamed to
> ntbootdd.sys
>
> Something like this below;
>
> [boot loader]
> timeout=10
> default=scsi(0)disk(0)rdisk(0)partition(1)\Windows
> [operating systems]
> scsi(0)disk(0)rdisk(0)partition(1)\Windows="Window s 2003 0,1"
> scsi(0)disk(0)rdisk(0)partition(2)\Windows="Window s 2003 0,2"
> scsi(0)disk(1)rdisk(0)partition(1)\Windows="Window s 2003 1,1"
> scsi(0)disk(1)rdisk(0)partition(2)\Windows="Window s 2003 1,2"
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "Geoff" wrote:
> > We are trying to setup a test server matching a clients existing
> > configuration but are having problems. The client has Windows 2003 Server
> > Std
> > on IDE Dynamic disks with Windows Software mirror.
> >
> > The problem is that after installing the operating system onto a newly
> > created partition on Disk0 we convert to dynamic disk and re boot.
> >
> > System fails to boot with the message "NTLDR is missing"
> >
> > Running recovery consol and using the map command would seem to indicate
> > the
> > reason for this issue as it shows no drive letter assigned to the boot
> > drive,
> > there is just a question mark.
> >
> > Any help appreciated.
> >
> > Geoff
> >
>
>

I just wouldn't get hung up on the question mark. I've seen that as a
placeholder elsewhere and in the registry. If the boot disk worked then the
issue may simply be an incorrect default= line in boot.ini


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"Geoff" wrote:
> Dave,
>
> Thanks for the input but I was looking for a reason rather than a
> workaround. Although we would not run software raid in real world I have
> used
> it before and have not had this issue.
>
> I have rebiult the server a couple of times since the orginal failure
> trying
> different things and have noticed that after conversion we get a message
> Windows is dismounting, dos that sound correct?
>
> It looks to me as though windows dismounts the volume and then fails to
> remount causing the boot failure and lcak of drive letter.
>
> Geoff

Dave,

Clean build, before conversion to dynamic disk I copied ntldr, ntdetect.com
and boot.ini to a floppy.

Coverted to dynamic disk, failed to boot with missing ntldr message.

Added USB floopy and re booted, system came up and looked normal. Checked
boot.ini on floppy against hard disk, identical?

Geoff


"Dave Patrick" wrote:

> I just wouldn't get hung up on the question mark. I've seen that as a
> placeholder elsewhere and in the registry. If the boot disk worked then the
> issue may simply be an incorrect default= line in boot.ini
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "Geoff" wrote:
> > Dave,
> >
> > Thanks for the input but I was looking for a reason rather than a
> > workaround. Although we would not run software raid in real world I have
> > used
> > it before and have not had this issue.
> >
> > I have rebiult the server a couple of times since the orginal failure
> > trying
> > different things and have noticed that after conversion we get a message
> > Windows is dismounting, dos that sound correct?
> >
> > It looks to me as though windows dismounts the volume and then fails to
> > remount causing the boot failure and lcak of drive letter.
> >
> > Geoff
>
>

What do you get from the RC if you;

bootcfg /scan

bootcfg /list

bootcfg /rebuild

http://support.microsoft.com/kb/317521

I believe the conversion needs to make it a simple active volume. I wonder
if this isn't happening for some reason. I cross posted to
microsoft.public.storage to get their input as well.
http://www.microsoft.com/communities...&lang=en&cr=US




--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"Geoff" wrote:
> Dave,
>
> Clean build, before conversion to dynamic disk I copied ntldr,
> ntdetect.com
> and boot.ini to a floppy.
>
> Coverted to dynamic disk, failed to boot with missing ntldr message.
>
> Added USB floopy and re booted, system came up and looked normal. Checked
> boot.ini on floppy against hard disk, identical?
>
> Geoff
>
>
> "Dave Patrick" wrote:
>
>> I just wouldn't get hung up on the question mark. I've seen that as a
>> placeholder elsewhere and in the registry. If the boot disk worked then
>> the
>> issue may simply be an incorrect default= line in boot.ini
>>
>>
>> --
>>
>> Regards,
>>
>> Dave Patrick ....Please no email replies - reply in newsgroup.
>> Microsoft Certified Professional
>> Microsoft MVP [Windows]
>> http://www.microsoft.com/protect
>>
>>
>> "Geoff" wrote:
>> > Dave,
>> >
>> > Thanks for the input but I was looking for a reason rather than a
>> > workaround. Although we would not run software raid in real world I
>> > have
>> > used
>> > it before and have not had this issue.
>> >
>> > I have rebiult the server a couple of times since the orginal failure
>> > trying
>> > different things and have noticed that after conversion we get a
>> > message
>> > Windows is dismounting, dos that sound correct?
>> >
>> > It looks to me as though windows dismounts the volume and then fails to
>> > remount causing the boot failure and lcak of drive letter.
>> >
>> > Geoff
>>
>>

Dave,

bootcfg reports all is normal, have run rebuild but system will not boot. No
longer reciving ntldr message just hangs at Press any key to boot from CD,
its like the disk is not there although boot from floppy still works
perfectly?

Geoff


"Dave Patrick" wrote:

> What do you get from the RC if you;
>
> bootcfg /scan
>
> bootcfg /list
>
> bootcfg /rebuild
>
> http://support.microsoft.com/kb/317521
>
> I believe the conversion needs to make it a simple active volume. I wonder
> if this isn't happening for some reason. I cross posted to
> microsoft.public.storage to get their input as well.
> http://www.microsoft.com/communities...&lang=en&cr=US
>
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "Geoff" wrote:
> > Dave,
> >
> > Clean build, before conversion to dynamic disk I copied ntldr,
> > ntdetect.com
> > and boot.ini to a floppy.
> >
> > Coverted to dynamic disk, failed to boot with missing ntldr message.
> >
> > Added USB floopy and re booted, system came up and looked normal. Checked
> > boot.ini on floppy against hard disk, identical?
> >
> > Geoff
> >
> >
> > "Dave Patrick" wrote:
> >
> >> I just wouldn't get hung up on the question mark. I've seen that as a
> >> placeholder elsewhere and in the registry. If the boot disk worked then
> >> the
> >> issue may simply be an incorrect default= line in boot.ini
> >>
> >>
> >> --
> >>
> >> Regards,
> >>
> >> Dave Patrick ....Please no email replies - reply in newsgroup.
> >> Microsoft Certified Professional
> >> Microsoft MVP [Windows]
> >> http://www.microsoft.com/protect
> >>
> >>
> >> "Geoff" wrote:
> >> > Dave,
> >> >
> >> > Thanks for the input but I was looking for a reason rather than a
> >> > workaround. Although we would not run software raid in real world I
> >> > have
> >> > used
> >> > it before and have not had this issue.
> >> >
> >> > I have rebiult the server a couple of times since the orginal failure
> >> > trying
> >> > different things and have noticed that after conversion we get a
> >> > message
> >> > Windows is dismounting, dos that sound correct?
> >> >
> >> > It looks to me as though windows dismounts the volume and then fails to
> >> > remount causing the boot failure and lcak of drive letter.
> >> >
> >> > Geoff
> >>
> >>
>
>

Dave,

Found out that it was something to do with Disk0. Fitted another disk and
was able to convert to Dynamic without issue.

Although the orginal disk would work as a basic disk it would not support
becoming a dynaic disk?

Thanks for your help.

Geoff

"Geoff" wrote:

> We are trying to setup a test server matching a clients existing
> configuration but are having problems. The client has Windows 2003 Server Std
> on IDE Dynamic disks with Windows Software mirror.
>
> The problem is that after installing the operating system onto a newly
> created partition on Disk0 we convert to dynamic disk and re boot.
>
> System fails to boot with the message "NTLDR is missing"
>
> Running recovery consol and using the map command would seem to indicate the
> reason for this issue as it shows no drive letter assigned to the boot drive,
> there is just a question mark.
>
> Any help appreciated.
>
> Geoff
>

You're welcome. Yes, that's a strange one. Thanks very much for posting what
you found.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"Geoff" wrote:
> Dave,
>
> Found out that it was something to do with Disk0. Fitted another disk and
> was able to convert to Dynamic without issue.
>
> Although the orginal disk would work as a basic disk it would not support
> becoming a dynaic disk?
>
> Thanks for your help.
>
> Geoff

"Dave Patrick" wrote:

> You're welcome. Yes, that's a strange one. Thanks very much for posting what
> you found.
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "Geoff" wrote:
> > Dave,
> >
> > Found out that it was something to do with Disk0. Fitted another disk and
> > was able to convert to Dynamic without issue.
> >
> > Although the orginal disk would work as a basic disk it would not support
> > becoming a dynaic disk?
> >
> > Thanks for your help.
> >
> > Geoff
>
>