Re: Really Need Help With Inaccessable_Boot_Device Problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




"Server Guy" <ServerGuy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A50744CE-DADE-4238-BCEC-2A36489A537B@xxxxxxxxxxxxxxxx
>
>
> "Pegasus" wrote:
>
> > "Server Guy" <ServerGuy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:9BBEFDB8-BBD6-486F-97E8-58530790EEF4@xxxxxxxxxxxxxxxx
> > > 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.

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.


.



Relevant Pages

  • Re: Unable to boot to existing 2003 server
    ... Formatted a floppy using 2003 server. ... Could not read from selected boot disk. ...
    (microsoft.public.windows.server.general)
  • Re: Rebuilt Mirror Wont Boot
    ... I would not be able to boot from the floppy since it is not on ... I am still at square one with a server that I can boot off a floppy ... I cannot boot the server using the same boot.ini file on the C drive. ... Since disk1 is the disk I used to create the new mirror with disk0, ...
    (microsoft.public.windows.server.general)
  • Re: Rebuilt Mirror Wont Boot
    ... I would not be able to boot from the floppy since it is not on ... I am still at square one with a server that I can boot off a floppy ... I cannot boot the server using the same boot.ini file on the C drive. ... Boot.ini should be the same on the floppy and on the hard disk. ...
    (microsoft.public.windows.server.general)
  • Re: Rebuilt Mirror Wont Boot
    ... Also, from what I have read, since I am using multiple SCSI drives, and the ... I would not be able to boot from the floppy since it is not on the ... I am still at square one with a server that I can boot off a floppy yet ... I cannot boot the server using the same boot.ini file on the C drive. ...
    (microsoft.public.windows.server.general)
  • Re: Unable to boot to existing 2003 server
    ... Format a floppy disk on some Win2000/XP/Server machine, ... Set the BIOS on the problem server so that the floppy drive ... is the primary boot device. ...
    (microsoft.public.windows.server.general)