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.
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
>
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
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.