Really Need Help With Inaccessable_Boot_Device Problem

[Guest]

Thanks for the link!

I never gave it a thought that mayby the RAID itself could be the issue. I
see Norton doesnt like to Ghost then restore on dis-similar RAID's or
controllers.

It does look to me like it's really the RAID drivers and not so much the
RAID itself. I broke the RAID on my SATA test server and Win2k still wants
the RAID driver in order to see the single drive.

It boils back to the problem of how to get the proper raid driver into the
partition before booting up with that configuration.

Not sure how to accomplish that one!

Looks like I'll also have to investigate on alternative methods to clone
this from one type of RAID to another.

:

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

:

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!

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.

 

[Guest]

Thanks! That www.bootdisk.com link looks like it has a wide variety of handy
utilities for those tough situations.

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

:



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!





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.

 

[Guest]

I agree, the key could be the presence of the correct drivers in the newly
created partition.

I will try loading that on my Test IDE drive then Ghost it to the SATA and
see what happens!



Just another thought guys, I have a set of freshly loaded SATA with Win2k
on it. Could I:

Export the reg from the prod server
Import it on the SATA on the test server

Would this retain the SATA drivers? If so I could copy the reg to the
Ghost'ed partition on te SATA drive on the test server then boot from it.

Just thinking out loud again!

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 Guy wrote:

:





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!





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.