System disk on RAID - moving to IDE

  • Thread starter Thread starter BertieBigBollox
  • Start date Start date
B

BertieBigBollox

Can use Ghost to from one physical disk (RAID array) to internal IDE
but I get the STOP error with UNBOOTABLE DEVICE.

Checked Boot.ini and it seems to point to correct disk. Booted from CD
into Recovery mode and ran FIXMBR and FIXBOOT but no difference.

I'm guessing that something is telling windows that its boot disk is a
RAID disk, rather than IDE internal disk. How do I change this? Any
ideas?
 
Is it 0x7b ? These articles may help.

How to Move a Windows Installation to Different Hardwarehttp://support.microsoft.com/?id=249694

HOW TO: Replace the Motherboard on a Computer That Is Running Windowshttp://support.microsoft.com/?id=824125

--

Regards,

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



Can use Ghost to from one physical disk (RAID array) to internal IDE
but I get the STOP error with UNBOOTABLE DEVICE.
Checked Boot.ini and it seems to point to correct disk. Booted from CD
into Recovery mode and ran FIXMBR and FIXBOOT but no difference.
I'm guessing that something is telling windows that its boot disk is a
RAID disk, rather than IDE internal disk. How do I change this? Any
ideas?- Hide quoted text -

- Show quoted text -

Yeh. Thats the one. Thanks I'll take a look at those links.
 
Is it 0x7b ? These articles may help.
How to Move a Windows Installation to Different Hardwarehttp://support.microsoft.com/?id=249694
HOW TO: Replace the Motherboard on a Computer That Is Running Windowshttp://support.microsoft.com/?id=824125

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

Yeh. Thats the one. Thanks I'll take a look at those links.- Hide quoted text -

- Show quoted text -

Tries Windows repair from CD but it made no difference. Any other
ideas?
 
Changing controllers is tricky at best. You can try loading the controller
driver from floppy. For the floppy to successfully boot Windows 2000 the
disk must contain the "NT" boot sector. Format a diskette (on a Windows 2000
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 2000 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 (in your case use atapi.sys for IDE disk controller)


Something like this below;


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



Also note hardware limitation for the Windows NT *system partition* was 7.8
gB because NTLDR would use the INT13 interface when using multi syntax in
boot.ini

Windows 2000/XP/2003/etc. supports large system partitions because it has
the ability to use BIOS INT-13 extensions to boot the operating system on
partitions with more than 1,024 cylinders, or 7.8 GB in size. So check that
the function is enabled in cmos setup.



Failing this you'll probably need to clean install and restore from backup.




--

Regards,

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


:
Tries Windows repair from CD but it made no difference. Any other
ideas?
 
Back
Top