Really Need Help With Inaccessable_Boot_Device Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi Guys,

I've posted before but never received a reply. I'm sure this is a simple
fix for someone more familiar with Windows boot-up issues.

My goal is to install my current version of Win2k server on a larger hard
drive. My current setup is a SCSI RAID-1. I'm moving to a SATA RAID-1 in
the same PC. I have Ghosted (2003) all partitions from the old to the new
drive. It looks like that all went well.

I do need to somehow get the SATA RAID driver loaded on my NEW drive so it
will boot. I can boot to the recovery console and that works but when I
re-boot it does not keep the drivers loaded.

What do I need to do to get the new SATA drivers loaded? Can I copy them
directly from the driver floppy?

If I run setup, I would have to remove the old windows installation to
install the new one that would include the drivers. Is there any way to do
this without installing the server OS from scratch?

I had loaded a new Win2k server setup on a spare set of SATA disks.
Could/should I copy anything from that setup to the Ghost'ed setup I have to
get the needed SATA drivers loaded?

You help/suggestions would be appreciated!
 
You might have to run a repair. Another option to try;

You might 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 will load a boot
device driver and use that driver to access the boot partition. Then also
copy the correct manufacturer raid controller 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)\winnt
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\winnt="Windows 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\winnt="Windows 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\winnt="Windows 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\winnt="Windows 1,2"


--

Regards,

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

:
| Hi Guys,
|
| I've posted before but never received a reply. I'm sure this is a simple
| fix for someone more familiar with Windows boot-up issues.
|
| My goal is to install my current version of Win2k server on a larger hard
| drive. My current setup is a SCSI RAID-1. I'm moving to a SATA RAID-1 in
| the same PC. I have Ghosted (2003) all partitions from the old to the new
| drive. It looks like that all went well.
|
| I do need to somehow get the SATA RAID driver loaded on my NEW drive so it
| will boot. I can boot to the recovery console and that works but when I
| re-boot it does not keep the drivers loaded.
|
| What do I need to do to get the new SATA drivers loaded? Can I copy them
| directly from the driver floppy?
|
| If I run setup, I would have to remove the old windows installation to
| install the new one that would include the drivers. Is there any way to
do
| this without installing the server OS from scratch?
|
| I had loaded a new Win2k server setup on a spare set of SATA disks.
| Could/should I copy anything from that setup to the Ghost'ed setup I have
to
| get the needed SATA drivers loaded?
|
| You help/suggestions would be appreciated!
|
 
Hi Dave,

Thank you for the quick response!

I tried your advice and am still having a problem booting the PC.

I modified the boot.ini to read:
[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="Microsoft Windows 2000 Server"

I also copied the SATA RAID driver to ntbootdd.sys and copied it to the root
of the primary partition.

I now get the error message:
Windows 2000 could not start because of a computer disk hardware problem.
Could not read from the selected boot disk. Check boot path and disk
hardware.

If I boot the PC from an IDE drive, that worked fine and I could also see
the SATA drives. The problem is just when I try to boot to the SATA devices.

THANKS again for any advice/suggestions!!!!



Dave Patrick said:
You might have to run a repair. Another option to try;

You might 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 will load a boot
device driver and use that driver to access the boot partition. Then also
copy the correct manufacturer raid controller 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)\winnt
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\winnt="Windows 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\winnt="Windows 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\winnt="Windows 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\winnt="Windows 1,2"


--

Regards,

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

:
| Hi Guys,
|
| I've posted before but never received a reply. I'm sure this is a simple
| fix for someone more familiar with Windows boot-up issues.
|
| My goal is to install my current version of Win2k server on a larger hard
| drive. My current setup is a SCSI RAID-1. I'm moving to a SATA RAID-1 in
| the same PC. I have Ghosted (2003) all partitions from the old to the new
| drive. It looks like that all went well.
|
| I do need to somehow get the SATA RAID driver loaded on my NEW drive so it
| will boot. I can boot to the recovery console and that works but when I
| re-boot it does not keep the drivers loaded.
|
| What do I need to do to get the new SATA drivers loaded? Can I copy them
| directly from the driver floppy?
|
| If I run setup, I would have to remove the old windows installation to
| install the new one that would include the drivers. Is there any way to
do
| this without installing the server OS from scratch?
|
| I had loaded a new Win2k server setup on a spare set of SATA disks.
| Could/should I copy anything from that setup to the Ghost'ed setup I have
to
| get the needed SATA drivers loaded?
|
| You help/suggestions would be appreciated!
|
Click to expand...
 
Try creating a boot floppy. If you receive the same error then the driver in
ntbootdd.sys may be incorrect.

--

Regards,

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

:
| Hi Dave,
|
| Thank you for the quick response!
|
| I tried your advice and am still having a problem booting the PC.
|
| I modified the boot.ini to read:
| [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="Microsoft Windows 2000 Server"
|
| I also copied the SATA RAID driver to ntbootdd.sys and copied it to the
root
| of the primary partition.
|
| I now get the error message:
| Windows 2000 could not start because of a computer disk hardware problem.
| Could not read from the selected boot disk. Check boot path and disk
| hardware.
|
| If I boot the PC from an IDE drive, that worked fine and I could also see
| the SATA drives. The problem is just when I try to boot to the SATA
devices.
|
| THANKS again for any advice/suggestions!!!!
 
Hi Dave,

I did make the floppy with the ntldr, netdetect.com, & boot.ini. I copied
them from a working (bootable) Win2k drive. I still get the same message:

Windows 2000 could not start because of a computer disk hardware problem.
Could not read from the selected boot disk. Check boot path and disk
hardware.

This time I copied the driver from a new Win2k install that runs on the same
SATA controller using the same driver floppy. I copied the viasraid.sys to
a:\ntbootdd.ini from the C:\winnt\system32\drivers.

I even tried using the floppy to boot the fresh Win2k install, same message
as with the Ghost'ed drives.

Any other thought as to what else may need changed or what I'm missing here?

Thanks again!!!

------------------------------------
 
Maybe a typo but ntbootdd.sys not ntbootdd.ini

--

Regards,

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

:
| Hi Dave,
|
| I did make the floppy with the ntldr, netdetect.com, & boot.ini. I copied
| them from a working (bootable) Win2k drive. I still get the same message:
|
| Windows 2000 could not start because of a computer disk hardware problem.
| Could not read from the selected boot disk. Check boot path and disk
| hardware.
|
| This time I copied the driver from a new Win2k install that runs on the
same
| SATA controller using the same driver floppy. I copied the viasraid.sys
to
| a:\ntbootdd.ini from the C:\winnt\system32\drivers.
|
| I even tried using the floppy to boot the fresh Win2k install, same
message
| as with the Ghost'ed drives.
|
| Any other thought as to what else may need changed or what I'm missing
here?
|
| Thanks again!!!
|
| ------------------------------------
 
My Bad, was a typo in the reply only, was really correct on the floppy as
a:\ntbootdd.sys

Really scratching my head on this one!
 
Afraid I've run out of ideas.

--

Regards,

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

:
| My Bad, was a typo in the reply only, was really correct on the floppy as
| a:\ntbootdd.sys
|
| Really scratching my head on this one!
 
Thanks for trying!

I think this is one of those things that are hard to find but easy to solve.

Anyone else maybe have any ideas?
 
Server Guy said:
Thanks for trying!

I think this is one of those things that are hard to find but easy to solve.

Anyone else maybe have any ideas?




Dave Patrick said:
Afraid I've run out of ideas.

--

Regards,

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

:
| My Bad, was a typo in the reply only, was really correct on the floppy as
| a:\ntbootdd.sys
|
| Really scratching my head on this one!
Click to expand...
Click to expand...

Dave Patrick knows a lot more about SCSI boots than
I do, hence my contribution may be of limited value.
Seeing that between the two of you you have looked
at this from just about every angle, I wonder if the problem
does not lie elsewhere, e.g. in the disk/partition numbers
you specify:
default=scsi(0)disk(0)rdisk(x)partition(y)\WINNT

Have you tried different partition and/or disk numbers?
Using Dave's Win2000 boot disk, it should be fairly
easy to go through a few permutations. Note that
x must be 0 or greater whereas y must be 1 or greater.

I assume that the directory c:\WinNT is correct - is it?
 
Thanks for the response,

I verified the C:\Winnt directory and also tried the additional boot.ini
permutations on the boot disk. Same results, still can't boot with the
Ghost'ed drives.

Just to verify I made the boot disk correctly, this is what I did:

1) format a: (from a Win2k server)
2) Copied/created boot.ini A:\
3) Copied ntdetect.com to A:\
4) Copied NTLDR.sys to A:\
5) Copied viasraid.sys as ntbootdd.sys and put ntbootdd.sys on A:\

I pasted the boot.ini permutations I tried at the bottom of this post

I'm willing to try anything you think may help!

Thanks again!!!!





Pegasus said:
Server Guy said:
Thanks for trying!

I think this is one of those things that are hard to find but easy to solve.

Anyone else maybe have any ideas?




Dave Patrick said:
Afraid I've run out of ideas.

--

Regards,

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

:
| My Bad, was a typo in the reply only, was really correct on the floppy as
| a:\ntbootdd.sys
|
| Really scratching my head on this one!
Click to expand...
Click to expand...

Dave Patrick knows a lot more about SCSI boots than
I do, hence my contribution may be of limited value.
Seeing that between the two of you you have looked
at this from just about every angle, I wonder if the problem
does not lie elsewhere, e.g. in the disk/partition numbers
you specify:
default=scsi(0)disk(0)rdisk(x)partition(y)\WINNT

Have you tried different partition and/or disk numbers?
Using Dave's Win2000 boot disk, it should be fairly
easy to go through a few permutations. Note that
x must be 0 or greater whereas y must be 1 or greater.
Click to expand...

I tried every combination I could think of here just to eliminate that as a
possibility.

[boot loader]
timeout=30
default=scsi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\WINNT="0-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(0)partition(2)\WINNT="0-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(0)partition(3)\WINNT="0-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(0)partition(4)\WINNT="0-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(1)\WINNT="1-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(2)\WINNT="1-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(3)\WINNT="1-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(4)\WINNT="1-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(1)\WINNT="2-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(2)\WINNT="2-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(3)\WINNT="2-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(4)\WINNT="2-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(1)\WINNT="3-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(2)\WINNT="3-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(3)\WINNT="3-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(4)\WINNT="3-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(1)\WINNT="4-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(2)\WINNT="4-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(3)\WINNT="4-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(4)\WINNT="4-4 Microsoft Windows 2000 Server"
/fastdetect


I assume that the directory c:\WinNT is correct - is it?
Click to expand...
Yep, C:\WINNT is it.
 
Your Step 4 actually deals with a file called NTLDR, not
NTLDR.sys, but then I think this is just a typographical
error.

Here is a long shot: You could do a new installation (or
at least the first stage), pressing F6 when prompted so
that Windows loads your driver. You could then examine
boot.ini and also check what files were copied to the root
directory of your boot drive.

How confident are you that the ghosting process worked
as it should? Did you try ghosting to an IDE disk in
order to verify the process?


Server Guy said:
Thanks for the response,

I verified the C:\Winnt directory and also tried the additional boot.ini
permutations on the boot disk. Same results, still can't boot with the
Ghost'ed drives.

Just to verify I made the boot disk correctly, this is what I did:

1) format a: (from a Win2k server)
2) Copied/created boot.ini A:\
3) Copied ntdetect.com to A:\
4) Copied NTLDR.sys to A:\
5) Copied viasraid.sys as ntbootdd.sys and put ntbootdd.sys on A:\

I pasted the boot.ini permutations I tried at the bottom of this post

I'm willing to try anything you think may help!

Thanks again!!!!





Pegasus said:
Server Guy said:
Thanks for trying!

I think this is one of those things that are hard to find but easy to solve.

Anyone else maybe have any ideas?




:

Afraid I've run out of ideas.

--

Regards,

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

:
| My Bad, was a typo in the reply only, was really correct on the
Click to expand...
floppy
as
| a:\ntbootdd.sys
|
| Really scratching my head on this one!
Click to expand...

Dave Patrick knows a lot more about SCSI boots than
I do, hence my contribution may be of limited value.
Seeing that between the two of you you have looked
at this from just about every angle, I wonder if the problem
does not lie elsewhere, e.g. in the disk/partition numbers
you specify:
default=scsi(0)disk(0)rdisk(x)partition(y)\WINNT

Have you tried different partition and/or disk numbers?
Using Dave's Win2000 boot disk, it should be fairly
easy to go through a few permutations. Note that
x must be 0 or greater whereas y must be 1 or greater.
Click to expand...

I tried every combination I could think of here just to eliminate that as a
possibility.

[boot loader]
timeout=30
default=scsi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\WINNT="0-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(0)partition(2)\WINNT="0-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(0)partition(3)\WINNT="0-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(0)partition(4)\WINNT="0-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(1)\WINNT="1-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(2)\WINNT="1-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(3)\WINNT="1-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(4)\WINNT="1-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(1)\WINNT="2-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(2)\WINNT="2-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(3)\WINNT="2-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(4)\WINNT="2-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(1)\WINNT="3-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(2)\WINNT="3-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(3)\WINNT="3-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(4)\WINNT="3-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(1)\WINNT="4-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(2)\WINNT="4-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(3)\WINNT="4-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(4)\WINNT="4-4 Microsoft Windows 2000 Server"
/fastdetect




I assume that the directory c:\WinNT is correct - is it?
Click to expand...
Yep, C:\WINNT is it.
Click to expand...
 
I have a copy of what's on my boot-floppy:

A-Dir.txt:
A A:\boot.ini
A SHR A:\ntldr
A SHR A:\NTDETECT.COM
A A:\ntbootdd.sys
A A:\boot-SCSI.ini
A SHR A:\arcsetup.exe
A SHR A:\arcldr.exe
A H A:\CONFIG.SYS
A SHR A:\IO.SYS
A SHR A:\MSDOS.SYS
A A:\Ghosted-Dir.txt
A A:\Loaded-Dir.txt
A A:\A-Dir.txt

Root of newly loaded SATA - Works fine:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:C\CONFIG.SYS
A SHR C:\IO.SYS
A C:\Loaded-Dir
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A SH C:\pagefile.sys
A H C:\_NavCClt.Log

Root of newly Ghost'ed SATA - Inaccessable_Boot_Device:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:\CONFIG.SYS
A C:\Ghosted-Dir
A SHR C:\IO.SYS
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A C:\VIRTPART.DAT



I copied any remaining files from the root of the SATA drives to the boot
floppy. The same info is on both the Ghost'ed drive as from the other pair
of SATA drives I did a new install on.

The boot.ini on both sets of SATA drives use the following:
[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

The interesting thing is the I can't boot from the floppy with either the
Ghost'ed drives or the newly installed Win2000 server. The newly installed
Win2000 works fine when I boot to them thru the RAID.

I would guess that this either means something is wrong with my boot floppy
or something is wrong with the viasraid.sys. I think I eliminated the driver
being bad because I copied it directly from the \Winnt\System32\Drivers as
NTBootDD.sys to my boot floppy.


Still scratching my head!!!




Pegasus said:
Your Step 4 actually deals with a file called NTLDR, not
NTLDR.sys, but then I think this is just a typographical
error.

Here is a long shot: You could do a new installation (or
at least the first stage), pressing F6 when prompted so
that Windows loads your driver. You could then examine
boot.ini and also check what files were copied to the root
directory of your boot drive.

How confident are you that the ghosting process worked
as it should? Did you try ghosting to an IDE disk in
order to verify the process?


Server Guy said:
Thanks for the response,

I verified the C:\Winnt directory and also tried the additional boot.ini
permutations on the boot disk. Same results, still can't boot with the
Ghost'ed drives.

Just to verify I made the boot disk correctly, this is what I did:

1) format a: (from a Win2k server)
2) Copied/created boot.ini A:\
3) Copied ntdetect.com to A:\
4) Copied NTLDR.sys to A:\
5) Copied viasraid.sys as ntbootdd.sys and put ntbootdd.sys on A:\

I pasted the boot.ini permutations I tried at the bottom of this post

I'm willing to try anything you think may help!

Thanks again!!!!





Pegasus said:
Thanks for trying!

I think this is one of those things that are hard to find but easy to
solve.

Anyone else maybe have any ideas?




:

Afraid I've run out of ideas.

--

Regards,

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

:
| My Bad, was a typo in the reply only, was really correct on the floppy
as
| a:\ntbootdd.sys
|
| Really scratching my head on this one!

Dave Patrick knows a lot more about SCSI boots than
I do, hence my contribution may be of limited value.
Seeing that between the two of you you have looked
at this from just about every angle, I wonder if the problem
does not lie elsewhere, e.g. in the disk/partition numbers
you specify:
default=scsi(0)disk(0)rdisk(x)partition(y)\WINNT

Have you tried different partition and/or disk numbers?
Using Dave's Win2000 boot disk, it should be fairly
easy to go through a few permutations. Note that
x must be 0 or greater whereas y must be 1 or greater.
Click to expand...

I tried every combination I could think of here just to eliminate that as a
possibility.

[boot loader]
timeout=30
default=scsi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\WINNT="0-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(0)partition(2)\WINNT="0-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(0)partition(3)\WINNT="0-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(0)partition(4)\WINNT="0-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(1)\WINNT="1-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(2)\WINNT="1-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(3)\WINNT="1-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(1)partition(4)\WINNT="1-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(1)\WINNT="2-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(2)\WINNT="2-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(3)\WINNT="2-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(2)partition(4)\WINNT="2-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(1)\WINNT="3-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(2)\WINNT="3-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(3)\WINNT="3-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(3)partition(4)\WINNT="3-4 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(1)\WINNT="4-1 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(2)\WINNT="4-2 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(3)\WINNT="4-3 Microsoft Windows 2000 Server"
/fastdetect
scsi(0)disk(0)rdisk(4)partition(4)\WINNT="4-4 Microsoft Windows 2000 Server"
/fastdetect




I assume that the directory c:\WinNT is correct - is it?
Click to expand...
Yep, C:\WINNT is it.
Click to expand...
Click to expand...
 
Server Guy said:
I have a copy of what's on my boot-floppy:

A-Dir.txt:
A A:\boot.ini
A SHR A:\ntldr
A SHR A:\NTDETECT.COM
A A:\ntbootdd.sys
A A:\boot-SCSI.ini
A SHR A:\arcsetup.exe
A SHR A:\arcldr.exe
A H A:\CONFIG.SYS
A SHR A:\IO.SYS
A SHR A:\MSDOS.SYS
A A:\Ghosted-Dir.txt
A A:\Loaded-Dir.txt
A A:\A-Dir.txt

Root of newly loaded SATA - Works fine:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:C\CONFIG.SYS
A SHR C:\IO.SYS
A C:\Loaded-Dir
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A SH C:\pagefile.sys
A H C:\_NavCClt.Log

Root of newly Ghost'ed SATA - Inaccessable_Boot_Device:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:\CONFIG.SYS
A C:\Ghosted-Dir
A SHR C:\IO.SYS
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A C:\VIRTPART.DAT



I copied any remaining files from the root of the SATA drives to the boot
floppy. The same info is on both the Ghost'ed drive as from the other pair
of SATA drives I did a new install on.

The boot.ini on both sets of SATA drives use the following:
[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

The interesting thing is the I can't boot from the floppy with either the
Ghost'ed drives or the newly installed Win2000 server. The newly installed
Win2000 works fine when I boot to them thru the RAID.

I would guess that this either means something is wrong with my boot floppy
or something is wrong with the viasraid.sys. I think I eliminated the driver
being bad because I copied it directly from the \Winnt\System32\Drivers as
NTBootDD.sys to my boot floppy.


Still scratching my head!!!
Click to expand...

Me too!
 
Pegasus said:
Server Guy said:
I have a copy of what's on my boot-floppy:

A-Dir.txt:
A A:\boot.ini
A SHR A:\ntldr
A SHR A:\NTDETECT.COM
A A:\ntbootdd.sys
A A:\boot-SCSI.ini
A SHR A:\arcsetup.exe
A SHR A:\arcldr.exe
A H A:\CONFIG.SYS
A SHR A:\IO.SYS
A SHR A:\MSDOS.SYS
A A:\Ghosted-Dir.txt
A A:\Loaded-Dir.txt
A A:\A-Dir.txt

Root of newly loaded SATA - Works fine:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:C\CONFIG.SYS
A SHR C:\IO.SYS
A C:\Loaded-Dir
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A SH C:\pagefile.sys
A H C:\_NavCClt.Log

Root of newly Ghost'ed SATA - Inaccessable_Boot_Device:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:\CONFIG.SYS
A C:\Ghosted-Dir
A SHR C:\IO.SYS
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A C:\VIRTPART.DAT



I copied any remaining files from the root of the SATA drives to the boot
floppy. The same info is on both the Ghost'ed drive as from the other pair
of SATA drives I did a new install on.

The boot.ini on both sets of SATA drives use the following:
[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

The interesting thing is the I can't boot from the floppy with either the
Ghost'ed drives or the newly installed Win2000 server. The newly installed
Win2000 works fine when I boot to them thru the RAID.

I would guess that this either means something is wrong with my boot floppy
or something is wrong with the viasraid.sys. I think I eliminated the driver
being bad because I copied it directly from the \Winnt\System32\Drivers as
NTBootDD.sys to my boot floppy.


Still scratching my head!!!
Click to expand...

Me too!
Click to expand...

How's this for a thought...

I still have the production W2k server up and in production. This is the
machine I made the ghost image FROM. Is there a way to load the new drivers
to get them into the registry on the production server, so they will be there
when I Ghost that server partition and load on to the new set of SATA disks
when I restore that partition? The old server has an Adaptec SCSI RAID.

The test server is identical to the production server. Same MB, cards,
memory, etc. The only diff between the 2 servers is I'll use the built-in
SATA RAID on the test unit.

My plan is to get the test server operational then either just swap complet
box'es or just move the SATA drives from the test unit back to the prod
server and remove the SCSI unit from there.

Just thinking out loud here. Not sure if it sounds good to you guys or not.
 
Server Guy said:
Pegasus said:
Server Guy said:
I have a copy of what's on my boot-floppy:

A-Dir.txt:
A A:\boot.ini
A SHR A:\ntldr
A SHR A:\NTDETECT.COM
A A:\ntbootdd.sys
A A:\boot-SCSI.ini
A SHR A:\arcsetup.exe
A SHR A:\arcldr.exe
A H A:\CONFIG.SYS
A SHR A:\IO.SYS
A SHR A:\MSDOS.SYS
A A:\Ghosted-Dir.txt
A A:\Loaded-Dir.txt
A A:\A-Dir.txt

Root of newly loaded SATA - Works fine:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:C\CONFIG.SYS
A SHR C:\IO.SYS
A C:\Loaded-Dir
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A SH C:\pagefile.sys
A H C:\_NavCClt.Log

Root of newly Ghost'ed SATA - Inaccessable_Boot_Device:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:\CONFIG.SYS
A C:\Ghosted-Dir
A SHR C:\IO.SYS
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A C:\VIRTPART.DAT



I copied any remaining files from the root of the SATA drives to the boot
floppy. The same info is on both the Ghost'ed drive as from the other pair
of SATA drives I did a new install on.

The boot.ini on both sets of SATA drives use the following:
[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

The interesting thing is the I can't boot from the floppy with either the
Ghost'ed drives or the newly installed Win2000 server. The newly installed
Win2000 works fine when I boot to them thru the RAID.

I would guess that this either means something is wrong with my boot floppy
or something is wrong with the viasraid.sys. I think I eliminated the driver
being bad because I copied it directly from the \Winnt\System32\Drivers as
NTBootDD.sys to my boot floppy.


Still scratching my head!!!
Click to expand...

Me too!
Click to expand...

How's this for a thought...

I still have the production W2k server up and in production. This is the
machine I made the ghost image FROM. Is there a way to load the new drivers
to get them into the registry on the production server, so they will be there
when I Ghost that server partition and load on to the new set of SATA disks
when I restore that partition? The old server has an Adaptec SCSI RAID.

The test server is identical to the production server. Same MB, cards,
memory, etc. The only diff between the 2 servers is I'll use the built-in
SATA RAID on the test unit.

My plan is to get the test server operational then either just swap complet
box'es or just move the SATA drives from the test unit back to the prod
server and remove the SCSI unit from there.

Just thinking out loud here. Not sure if it sounds good to you guys or
Click to expand...
not.

This sounds like a good idea to me. So far you appear to have
maintained an enviable record of not jeopardizing your original
server in any way. To maintain this record, I would make sure
to create a ghost file and store it in a safe place ***before***
loading the SATA drivers.
 
Maybe it's because Ghost is not really compatible with RAID?

(Excerpt)

"Symantec does not provide technical support for imaging RAID drives,
regardless of whether the drive uses software level RAID or hardware
level RAID. Successfully imaging a RAID drive is dependent on the
specific computer model, driver controller, hard drive, and RAID
implementation. Symantec provides the following information only as an
aid to cloning RAID drives. This information is a suggestion only. It is
likely to work only in limited circumstances. Symantec does not provide
support for the following information."

Ghost compatibility with RAID
http://service1.symantec.com/SUPPOR...&dtype=corp&prod=Symantec Ghost&ver=8.0&tpre=

John

Server said:
:

I have a copy of what's on my boot-floppy:

A-Dir.txt:
A A:\boot.ini
A SHR A:\ntldr
A SHR A:\NTDETECT.COM
A A:\ntbootdd.sys
A A:\boot-SCSI.ini
A SHR A:\arcsetup.exe
A SHR A:\arcldr.exe
A H A:\CONFIG.SYS
A SHR A:\IO.SYS
A SHR A:\MSDOS.SYS
A A:\Ghosted-Dir.txt
A A:\Loaded-Dir.txt
A A:\A-Dir.txt

Root of newly loaded SATA - Works fine:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:C\CONFIG.SYS
A SHR C:\IO.SYS
A C:\Loaded-Dir
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A SH C:\pagefile.sys
A H C:\_NavCClt.Log

Root of newly Ghost'ed SATA - Inaccessable_Boot_Device:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:\CONFIG.SYS
A C:\Ghosted-Dir
A SHR C:\IO.SYS
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A C:\VIRTPART.DAT



I copied any remaining files from the root of the SATA drives to the boot
floppy. The same info is on both the Ghost'ed drive as from the other
pair

of SATA drives I did a new install on.

The boot.ini on both sets of SATA drives use the following:
[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

The interesting thing is the I can't boot from the floppy with either the
Ghost'ed drives or the newly installed Win2000 server. The newly
installed

Win2000 works fine when I boot to them thru the RAID.

I would guess that this either means something is wrong with my boot
floppy

or something is wrong with the viasraid.sys. I think I eliminated the
driver

being bad because I copied it directly from the \Winnt\System32\Drivers as
NTBootDD.sys to my boot floppy.


Still scratching my head!!!
Click to expand...

Me too!
Click to expand...


How's this for a thought...

I still have the production W2k server up and in production. This is the
machine I made the ghost image FROM. Is there a way to load the new drivers
to get them into the registry on the production server, so they will be there
when I Ghost that server partition and load on to the new set of SATA disks
when I restore that partition? The old server has an Adaptec SCSI RAID.

The test server is identical to the production server. Same MB, cards,
memory, etc. The only diff between the 2 servers is I'll use the built-in
SATA RAID on the test unit.

My plan is to get the test server operational then either just swap complet
box'es or just move the SATA drives from the test unit back to the prod
server and remove the SCSI unit from there.

Just thinking out loud here. Not sure if it sounds good to you guys or not.
Click to expand...
 
If so then perhaps a cloning operation with xcopy.exe under
a Bart PE boot CD boot might work. You can download the
tool to make one from www.bootdisk.com.


John John said:
Maybe it's because Ghost is not really compatible with RAID?

(Excerpt)

"Symantec does not provide technical support for imaging RAID drives,
regardless of whether the drive uses software level RAID or hardware
level RAID. Successfully imaging a RAID drive is dependent on the
specific computer model, driver controller, hard drive, and RAID
implementation. Symantec provides the following information only as an
aid to cloning RAID drives. This information is a suggestion only. It is
likely to work only in limited circumstances. Symantec does not provide
support for the following information."

Ghost compatibility with RAID
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999010613522725?OpenDo
cument&src=ent_hot&dtype=corp&prod=Symantec%20Ghost&ver=8.0&tpre=

John

Server said:
:

I have a copy of what's on my boot-floppy:

A-Dir.txt:
A A:\boot.ini
A SHR A:\ntldr
A SHR A:\NTDETECT.COM
A A:\ntbootdd.sys
A A:\boot-SCSI.ini
A SHR A:\arcsetup.exe
A SHR A:\arcldr.exe
A H A:\CONFIG.SYS
A SHR A:\IO.SYS
A SHR A:\MSDOS.SYS
A A:\Ghosted-Dir.txt
A A:\Loaded-Dir.txt
A A:\A-Dir.txt

Root of newly loaded SATA - Works fine:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:C\CONFIG.SYS
A SHR C:\IO.SYS
A C:\Loaded-Dir
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A SH C:\pagefile.sys
A H C:\_NavCClt.Log

Root of newly Ghost'ed SATA - Inaccessable_Boot_Device:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:\CONFIG.SYS
A C:\Ghosted-Dir
A SHR C:\IO.SYS
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A C:\VIRTPART.DAT



I copied any remaining files from the root of the SATA drives to the boot
floppy. The same info is on both the Ghost'ed drive as from the other

pair

of SATA drives I did a new install on.

The boot.ini on both sets of SATA drives use the following:
[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

The interesting thing is the I can't boot from the floppy with either the
Ghost'ed drives or the newly installed Win2000 server. The newly

installed

Win2000 works fine when I boot to them thru the RAID.

I would guess that this either means something is wrong with my boot

floppy

or something is wrong with the viasraid.sys. I think I eliminated the

driver

being bad because I copied it directly from the \Winnt\System32\Drivers as
NTBootDD.sys to my boot floppy.


Still scratching my head!!!

Me too!
Click to expand...


How's this for a thought...

I still have the production W2k server up and in production. This is the
machine I made the ghost image FROM. Is there a way to load the new drivers
to get them into the registry on the production server, so they will be there
when I Ghost that server partition and load on to the new set of SATA disks
when I restore that partition? The old server has an Adaptec SCSI RAID.

The test server is identical to the production server. Same MB, cards,
memory, etc. The only diff between the 2 servers is I'll use the built-in
SATA RAID on the test unit.

My plan is to get the test server operational then either just swap complet
box'es or just move the SATA drives from the test unit back to the prod
server and remove the SCSI unit from there.

Just thinking out loud here. Not sure if it sounds good to you guys or not.
Click to expand...
Click to expand...
 
hmm, another thing that I'm not sure of is whether or not the OP had
loaded the new SATA RAID drivers onto the installation he was trying to
clone. The new SATA drivers should have been loaded even if the
hardware wasn't yet present. That might make a difference and maybe the
the Ghost operation would work if the drivers were preloaded. But then
maybe not...

John
If so then perhaps a cloning operation with xcopy.exe under
a Bart PE boot CD boot might work. You can download the
tool to make one from www.bootdisk.com.


Maybe it's because Ghost is not really compatible with RAID?

(Excerpt)

"Symantec does not provide technical support for imaging RAID drives,
regardless of whether the drive uses software level RAID or hardware
level RAID. Successfully imaging a RAID drive is dependent on the
specific computer model, driver controller, hard drive, and RAID
implementation. Symantec provides the following information only as an
aid to cloning RAID drives. This information is a suggestion only. It is
likely to work only in limited circumstances. Symantec does not provide
support for the following information."

Ghost compatibility with RAID

http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999010613522725?OpenDo
cument&src=ent_hot&dtype=corp&prod=Symantec%20Ghost&ver=8.0&tpre=

John

Server said:
:





I have a copy of what's on my boot-floppy:

A-Dir.txt:
A A:\boot.ini
A SHR A:\ntldr
A SHR A:\NTDETECT.COM
A A:\ntbootdd.sys
A A:\boot-SCSI.ini
A SHR A:\arcsetup.exe
A SHR A:\arcldr.exe
A H A:\CONFIG.SYS
A SHR A:\IO.SYS
A SHR A:\MSDOS.SYS
A A:\Ghosted-Dir.txt
A A:\Loaded-Dir.txt
A A:\A-Dir.txt

Root of newly loaded SATA - Works fine:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:C\CONFIG.SYS
A SHR C:\IO.SYS
A C:\Loaded-Dir
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A SH C:\pagefile.sys
A H C:\_NavCClt.Log

Root of newly Ghost'ed SATA - Inaccessable_Boot_Device:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:\CONFIG.SYS
A C:\Ghosted-Dir
A SHR C:\IO.SYS
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A C:\VIRTPART.DAT



I copied any remaining files from the root of the SATA drives to the
Click to expand...
boot
floppy. The same info is on both the Ghost'ed drive as from the other

pair


of SATA drives I did a new install on.

The boot.ini on both sets of SATA drives use the following:
[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
Click to expand...
Server"
/fastdetect

The interesting thing is the I can't boot from the floppy with either
Click to expand...
the
Ghost'ed drives or the newly installed Win2000 server. The newly

installed


Win2000 works fine when I boot to them thru the RAID.

I would guess that this either means something is wrong with my boot

floppy


or something is wrong with the viasraid.sys. I think I eliminated the

driver


being bad because I copied it directly from the \Winnt\System32\Drivers
Click to expand...
as
NTBootDD.sys to my boot floppy.


Still scratching my head!!!

Me too!





How's this for a thought...

I still have the production W2k server up and in production. This is
Click to expand...
the
machine I made the ghost image FROM. Is there a way to load the new
Click to expand...
drivers
to get them into the registry on the production server, so they will be
Click to expand...
there
when I Ghost that server partition and load on to the new set of SATA
Click to expand...
disks
when I restore that partition? The old server has an Adaptec SCSI RAID.

The test server is identical to the production server. Same MB, cards,
memory, etc. The only diff between the 2 servers is I'll use the
Click to expand...
built-in
SATA RAID on the test unit.

My plan is to get the test server operational then either just swap
Click to expand...
complet
box'es or just move the SATA drives from the test unit back to the prod
server and remove the SCSI unit from there.

Just thinking out loud here. Not sure if it sounds good to you guys or
Click to expand...
Click to expand...

not.
Click to expand...
 
Pegasus said:
Server Guy said:
Pegasus said:
I have a copy of what's on my boot-floppy:

A-Dir.txt:
A A:\boot.ini
A SHR A:\ntldr
A SHR A:\NTDETECT.COM
A A:\ntbootdd.sys
A A:\boot-SCSI.ini
A SHR A:\arcsetup.exe
A SHR A:\arcldr.exe
A H A:\CONFIG.SYS
A SHR A:\IO.SYS
A SHR A:\MSDOS.SYS
A A:\Ghosted-Dir.txt
A A:\Loaded-Dir.txt
A A:\A-Dir.txt

Root of newly loaded SATA - Works fine:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:C\CONFIG.SYS
A SHR C:\IO.SYS
A C:\Loaded-Dir
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A SH C:\pagefile.sys
A H C:\_NavCClt.Log

Root of newly Ghost'ed SATA - Inaccessable_Boot_Device:
A SHR C:\arcldr.exe
A SHR C:\arcsetup.exe
A H C:\AUTOEXEC.BAT
A SH C:\boot.ini
A H C:\CONFIG.SYS
A C:\Ghosted-Dir
A SHR C:\IO.SYS
A SHR C:\MSDOS.SYS
A SHR C:\NTDETECT.COM
A SHR C:\ntldr
A C:\VIRTPART.DAT



I copied any remaining files from the root of the SATA drives to the boot
floppy. The same info is on both the Ghost'ed drive as from the other
pair
of SATA drives I did a new install on.

The boot.ini on both sets of SATA drives use the following:
[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

The interesting thing is the I can't boot from the floppy with either the
Ghost'ed drives or the newly installed Win2000 server. The newly
installed
Win2000 works fine when I boot to them thru the RAID.

I would guess that this either means something is wrong with my boot
floppy
or something is wrong with the viasraid.sys. I think I eliminated the
driver
being bad because I copied it directly from the \Winnt\System32\Drivers as
NTBootDD.sys to my boot floppy.


Still scratching my head!!!

Me too!
Click to expand...

How's this for a thought...

I still have the production W2k server up and in production. This is the
machine I made the ghost image FROM. Is there a way to load the new drivers
to get them into the registry on the production server, so they will be there
when I Ghost that server partition and load on to the new set of SATA disks
when I restore that partition? The old server has an Adaptec SCSI RAID.

The test server is identical to the production server. Same MB, cards,
memory, etc. The only diff between the 2 servers is I'll use the built-in
SATA RAID on the test unit.

My plan is to get the test server operational then either just swap complet
box'es or just move the SATA drives from the test unit back to the prod
server and remove the SCSI unit from there.

Just thinking out loud here. Not sure if it sounds good to you guys or
Click to expand...
not.

This sounds like a good idea to me. So far you appear to have
maintained an enviable record of not jeopardizing your original
server in any way. To maintain this record, I would make sure
to create a ghost file and store it in a safe place ***before***
loading the SATA drivers.
Click to expand...
I plan on KEEPING that record in-tact! I've been in the business for a long
time and that's the one thing to never forget! I've moved over from mainly
Novell and UNIX to Win servers. I'm still learning all the "tricks", at
least I'm working on it anyway!

Thanks for the reminder! I will be making a Ghost image of all 4 partitions
on the server BEFORE the upgrade. I'm sure glad I have the test server to
try this out on.
I'll probably also do a NTBackup as well. Can't have too many backups from
BEFORE an upgrade!
 
Back
Top