General discussion

Locked

NT 4.0 serve boot trouble

By cococs ·
I have recently physically moved an old server and now NT will not boot, even with the install disks, can't recover, the system blue screens with a message "inaccessible boot device" - checked the internal components - doesn't seem to be anything loose. Any suggestions?

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

NT 4.0 serve boot trouble

by C. Hilbrandt In reply to NT 4.0 serve boot trouble

Try to physically reseat all connections in the server particularly those dealing directly with the hardrives,(SCSI cards, controller cards, all cables) and hope for the best. Otherwise you may have lost a piece of hardware. Also, if you can, try to verify that your hard drives are spinning as sometimes old ones that have been running for a long time don't have enough gumption to spin back up again. Good luck..........

Collapse -

NT 4.0 serve boot trouble

by cococs In reply to NT 4.0 serve boot trouble

Poster rated this answer

Collapse -

NT 4.0 serve boot trouble

by DC1 In reply to NT 4.0 serve boot trouble

Sounds like a bad hard drive. If you have reseated the cables already try to go into the BIOS of the server and see if it recognizes the hardware.

Collapse -

NT 4.0 serve boot trouble

by cococs In reply to NT 4.0 serve boot trouble

Poster rated this answer

Collapse -

NT 4.0 serve boot trouble

by DS9 In reply to NT 4.0 serve boot trouble

Number 1 above is probably on the right track. I have an old 486 machine (that ran 24 hrs/day for three years) that I use from time to time now as a BDC. Whenever I want to do service on my Primary PDC, I fire that dude up and promote it to primary while I have my Main primary down for service.

However, sometimes when the machine has been off for several days, the Hard Drive won't spin up. So now, I leave the outcase off of that machine so that I can hear whether the drive spins up and the heads come off their landing zones.

If it does not start, I literally wack-it with the handle end of a screw driver, and hit the reset button a couple of times to break it loose. It always works fine after that cave man beating, I'll just have to get a new drive or machine one of these days to replace it. But hey, if yours is an old one also, what have you really got loose in the long run by trying it. If it works, you can get a new drive in the position, and transfer data to it and start fresh later.

Good-luck
George

Collapse -

NT 4.0 serve boot trouble

by cococs In reply to NT 4.0 serve boot trouble

Poster rated this answer

Collapse -

NT 4.0 serve boot trouble

by nrayburn In reply to NT 4.0 serve boot trouble

This problem may occur if one or more of the following conditions exists:

- Your computer is infected with a boot sector virus.

- A device driver required by your boot controller is not configured to start
at boot time or is corrupt. Ifduring a WINNT /B installation no mass storage
device was detected.

- A resource conflict exists between the boot controller and another controller
in the system or between SCSI devices.

- Drive translation is not being performed or was changed.

- The boot volume is corrupt and cannot be mounted by Windows NT.

- Information in the Windows NT registry about which device drivers load at
start up is corrupt.

- If this error occurred during Windows NT Setup while reading Windows NT Setup
floppy disk 2, you may have the Drive Swapping option enabled in your
computer BIOS.

- Using winnt /b as the installation method may present a timing issue for the
disk controller. The controller is not given enough time to respond and
identify itself and is therefore detected incorrectly or not at all.

- If you run Setup from a bootable SCSI CD-ROM drive, you receive a STOP 7B
error message because Setup does not allow you to add a third-party SCSI
driver when you boot from the SCSI CD-ROM.

RESOLUTION
==========

To resolve this problem, use the appropriate method:

Method 1
--------

Check any diskettes for viruses that may have been used in the computer since the
last time you were able to successfully restart Windows NT.

NOTE: You may need to use more than one brand of virus detection software to
detect and remove various viruses.

If a virus has infected the Windows NT computer and a virus detection program
cannot remove the virus and repair the system, you will have to reinstall
Windows NT.

Collapse -

NT 4.0 serve boot trouble

by cococs In reply to NT 4.0 serve boot trouble

Poster rated this answer

Collapse -

NT 4.0 serve boot trouble

by cococs In reply to NT 4.0 serve boot trouble

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums