Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / Setup / December 2004

Tip: Looking for answers? Try searching our database.

INACCESSIBLE_BOOT_DEVICE

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
matrix - 14 Nov 2004 09:57 GMT
Hi,
i have an hold proliant 800 (ppro 200) with Win NT Server 4.0 SP1.
Yesterday I wanted to upgrade it to the sp6. After upgrade and the reboot
blue window with many esadecimali characters has appeared one and the
written INACCESSIBLE_BOOT_DEVICE.
I have read on the situated one of the microsoft to replace the file
aic8xx.sys contained in winnt/system32/drivers with that present in sp6. The
problem is that in winnt/system32/drivers these file there is not ....
Therefore to that what I replace it?

Sorry for my bad english but i have used altavista traduction! :-)

Bye
Dave Patrick - 14 Nov 2004 15:02 GMT
You might try a boot floppy so you can add the driver. For a floppy to
successfully boot Windows NT the disk must contain the "NT" boot sector.
Format a diskette (on an NT machine, not a DOS/Win9x, so the NT boot sector
gets written to the floppy), and 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 your case you'll want to change the arc path in boot.ini from multi
syntax to scsi syntax to indicate that Windows NT will load a boot device
driver and use that driver to access the boot partition. Then also copy the
drive 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"

Signature

Regards,

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

| Hi,
| i have an hold proliant 800 (ppro 200) with Win NT Server 4.0 SP1.
[quoted text clipped - 9 lines]
|
| Bye
matrix - 17 Nov 2004 16:51 GMT
> You might try a boot floppy so you can add the driver. For a floppy to
> successfully boot Windows NT the disk must contain the "NT" boot sector.
[quoted text clipped - 21 lines]
> scsi(0)disk(1)rdisk(0)partition(1)\winnt="Windows 1,1"
> scsi(0)disk(1)rdisk(0)partition(2)\winnt="Windows 1,2"

Hi,
thank's for reply.
I have:

1. format a floppy disk under WIn NT
2. Copy ntldr, ntdetect.com, and boot.ini  in a floppy
3 . Copy a driver scsi in floppy and rename it in NTBOOTDD.SYS

At the boot the result is same....blue screen: INACCESSIBLE_BOOT_DEVICE

Please help me...and sorry for my english!

bye
Dave Patrick - 17 Nov 2004 17:22 GMT
Remember that you'll want to change the arc path in boot.ini from multi
syntax to scsi syntax to indicate that Windows NT will load a boot device
driver and use that driver to access the boot partition.

Another option to get access to the file system to replace your file is to
use a parallel install.

How and Why to Perform a Parallel Installation of Windows NT 4.0
http://support.microsoft.com/default.aspx?scid=KB;en-us;q259003

System Cleanup After a Parallel Installation of Windows NT 4.0

http://support.microsoft.com/default.aspx?scid=KB;en-us;q244378

Signature

Regards,

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

| Hi,
| thank's for reply.
[quoted text clipped - 9 lines]
|
| bye
matrix - 17 Nov 2004 19:43 GMT
> Remember that you'll want to change the arc path in boot.ini from multi
> syntax to scsi syntax to indicate that Windows NT will load a boot device
[quoted text clipped - 9 lines]
>
> http://support.microsoft.com/default.aspx?scid=KB;en-us;q244378

Ah, yes... i have changed a boot.ini in:
[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"

Is correct?
Dave Patrick - 17 Nov 2004 19:52 GMT
Yes

Signature

Regards,

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

| Ah, yes... i have changed a boot.ini in:
| [boot loader]
[quoted text clipped - 7 lines]
|
| Is correct?
matrix - 18 Nov 2004 14:38 GMT
> Yes

But don't work...
Dave Patrick - 18 Nov 2004 15:10 GMT
Then you'll probably want to try the other option to get access to the file
system to replace your file. Use a parallel install.

How and Why to Perform a Parallel Installation of Windows NT 4.0
http://support.microsoft.com/default.aspx?scid=KB;en-us;q259003

System Cleanup After a Parallel Installation of Windows NT 4.0
http://support.microsoft.com/default.aspx?scid=KB;en-us;q244378

Signature

Regards,

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

| But don't work...
Jiri Tuma - 22 Nov 2004 10:41 GMT
hmm, Now it is the time for next question, I think.

There are two possible module sources of IBD error - NT loader  and NT
kernel. In 95 percent of cases this error is coming from NTLDR, but can you
check, when you try to start machine from disk (not this floppy) what module
name is here as source of error? Solutions differ if source is NTKRNL
instead of NTLDR.

> > Yes
> >
> > --
> > Regards,
> >
> But don't work...
Karl-Stephan Werkmeister - 18 Nov 2004 22:04 GMT
> Hi,
> i have an hold proliant 800 (ppro 200) with Win NT Server 4.0 SP1.
> Yesterday I wanted to upgrade it to the sp6. After upgrade and the reboot
> blue window with many esadecimali characters has appeared one and the
> written INACCESSIBLE_BOOT_DEVICE.
[...]

a) It may have been helpful I you had given more infos about your
configuration.
SCSI, IDE, RAID, size of your HDD and system partition

b) Besides a 2nd (parallel) installation of NT4 you can access your NTFS
volumes also by 3rd party software like
    http://www.sysinternals.com/ntw2k/freeware/ntfsdos.shtml (but no write
access)
  or
    http://www.datapol.de/dpd/freeware/index.html (but only German and for
private use only)

This will at least help to read your original boot.ini on HDD if it is
located on an NTFS-partition (otherwise you can read it anyway)

c) If you really did nothing but applying SP6a your troubles might have
something to do with the updated ATAPI.SYS. This applies e.g. for some
DELL-Systems, see
http://forums.us.dell.com/supportforums/board/message?board.id=pes_wnts&message.
id=1985&view=by_date_ascending&page=1

(just an idea)

Stephan
Roger Hunt - 21 Nov 2004 13:39 GMT
>> Hi,
>> i have an hold proliant 800 (ppro 200) with Win NT Server 4.0 SP1.
[quoted text clipped - 14 lines]
>       http://www.datapol.de/dpd/freeware/index.html (but only German and for
>private use only)
(snip)

NTFS4DOS, from Datapol above, very handy, and thanks for the link.
I have discovered that the setup lets me choose between English and
German.

Regards
Signature

Roger Hunt

MasterK - 27 Dec 2004 15:46 GMT
I also receive a stop on Windows load. I suspect it is a virus though. I
can't load the Windows CD without removing power from the HDD - even if I
remove the HDD from the bios boot sequence. Any thoughts on where to
begin?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.