Tom's Hardware > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > Inaccessible_boot_device after installing service pack 6a

Inaccessible_boot_device after installing service pack 6a

Forum Windows 2000/NT : Windows 2000/NT General Discussion - Inaccessible_boot_device after installing service pack 6a

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

Archived from groups: microsoft.public.windowsnt.setup (More info?)

 

Hello,
I have an IBM Netfinity 5000 with Windows NT 4.0 Server, Service pack 3.
I have upgraded it to Service pack 6a, but after restarting, the system
crash with an "Inaccesible_Boot_Device" error on blue screen.

What can I do?

Thanks

Sponsored Links
Register or log in to remove.

Archived from groups: microsoft.public.windowsnt.setup (More info?)

 

Jose

Probably, your disk controller driver has been overwritten with another
version. See if this MS Knowledge Base article can help you:

http://support.microsoft.com/?id=214810

Best regards

Bjorn
--
Bjorn Landemoo - mvp2@landemoo.com - http://landemoo.com/
Microsoft MVP (Windows Server - File System)

"Jose Luis" <aa@dwede.es> wrote:

>Hello,
>I have an IBM Netfinity 5000 with Windows NT 4.0 Server, Service pack 3.
>I have upgraded it to Service pack 6a, but after restarting, the system
>crash with an "Inaccesible_Boot_Device" error on blue screen.
>
>What can I do?
>
>Thanks
>

Reply to Anonymous

Archived from groups: microsoft.public.windowsnt.setup (More info?)

 

Did you perhaps make the boot partition larger than 8GB in some way?
If the update put any critical files beyond the first 8GB of the disk, they
may not be accessible during boot, since the driver needed for this has not
loaded yet.

If this is the case, you may have to reinstall your backup. If you do not
have a backup (why not?), you may be able to image the drive with something
like Ghost and then restore it back to a smaller partition. If it won't fit
into a smaller partition, you may get lucky and the imaging may still end up
putting the critical files back where they can be accessed. I have actually
seen this work.

Or, the problem may be a driver problem - especially if you have SCSI drives,
or some other non-standard drive controller. I don't really have any
suggestion for this.

In article <OnrUSBPhEHA.3944@tk2msftngp13.phx.gbl>, "Jose Luis" <aa@dwede.es>
wrote:
|Hello,
|I have an IBM Netfinity 5000 with Windows NT 4.0 Server, Service pack 3.
|I have upgraded it to Service pack 6a, but after restarting, the system
|crash with an "Inaccesible_Boot_Device" error on blue screen.
|
|What can I do?
|
|Thanks

Reply to Anonymous

Archived from groups: microsoft.public.windowsnt.setup (More info?)

 

It's possible to overcome 7.8 GB system/boot partition limit by replacing
NT4 loader files with its W2k and up versions.

Reply to Anonymous

Archived from groups: microsoft.public.windowsnt.setup (More info?)

 

Hey Jetro,

an interesting point - have you actually done this yourself, and does it work OK ??

Calvin.

Reply to Calvin

Archived from groups: microsoft.public.windowsnt.setup (More info?)

 

It works without a glitch indeed. All you need is the bootstrap loader,
ntldr, and ntdetect.com, rarely ntbootdd.sys.

Reply to Anonymous
Tom's Hardware > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > Inaccessible_boot_device after installing service pack 6a
Go to:

There are 1207 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them