Why is my server stuck in a consistency check loop?

[Guest]

I was trying to set up some networking stuff, and got a particular
error. I looked up that error, and found that I might need an update to SQL
Server. I tried to download that update, but had to get the 2000 Server SP4
before it would work. After installing the service pack, I restarted to
finish installation.

At this point, I got the consistency check problem. The biggest problem was
that after the consistency check was done, it was in a loop of trying to
startup Windows, but having to check the consistency. If I stopped the
consistency check, I got a blue screen of death, telling me to uninstall any
new software, run chkdsk /f, and to start in safe mode.

I tried to start in all three different safe modes, in the last known good
configuration, and another of the startup options. None of them worked. Next
I went into the BIOS, and tried to load the original Fail-Safe config., but
that did not work either. I also did a scandisk from the BIOS setup screen. I
changed the BIOS to allow Boot from CD, and did so from my Norton AV. The
virus check was negative.

At one point in this process, the blue screen also said something about a
bad driver.

The next thing I tried, was to boot from an old NT CD. It was version 4 if
that matters. It would not let me install because it could not locate a Hard
Disk. The guy who works on our MAC's thought it might be that the old NT
could not communicate with an IDE Hard Disk. I was under the impression, that
the OS does not need to have any inherrent ability to communicate with a
certain type of hard drive, but that the motherboard determines what type of
drive may be used.

So, it comes down to the final question. Is our hard drive corrupt? Is there
some driver stored in Cache that is bad? Is there something wrong with our
motherboard, or a cable in-between it and the hard disk? I am really in over
my head on this one. Thanks for any help.

James

 

[Dave Patrick]

Download and run a diagnostic utility from the drive manufacturer's web
site.

After backup you can also run;
chkdsk /r
from the recovery console command line. (/r implies /f )

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%

What are you wanting to do with the Windows NT setup disk?

You didn't mention the drive controller (possibly SCSI, or ultra DMA, or
ATA100, or raid, or serial ATA), but you may need to boot the Windows NT
setup disks or CD-Rom and *F6* very early and very important (at setup is
inspecting your system) in the setup to prevent drive controller detection,
and select S to specify additional drivers. Then later you'll be prompted to
insert the manufacturer supplied Windows NT driver for your drive's
controller in drive "A"

If you wait and then S to specify additional drivers, then it may be too
late as Windows NT Setup at this point may have already assigned the
resources your drive's controller is wanting to use.

--
Regards,

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

:
|I was trying to set up some networking stuff, and got a particular
| error. I looked up that error, and found that I might need an update to
SQL
| Server. I tried to download that update, but had to get the 2000 Server
SP4
| before it would work. After installing the service pack, I restarted to
| finish installation.
|
| At this point, I got the consistency check problem. The biggest problem
was
| that after the consistency check was done, it was in a loop of trying to
| startup Windows, but having to check the consistency. If I stopped the
| consistency check, I got a blue screen of death, telling me to uninstall
any
| new software, run chkdsk /f, and to start in safe mode.
|
| I tried to start in all three different safe modes, in the last known good
| configuration, and another of the startup options. None of them worked.
Next
| I went into the BIOS, and tried to load the original Fail-Safe config.,
but
| that did not work either. I also did a scandisk from the BIOS setup
screen. I
| changed the BIOS to allow Boot from CD, and did so from my Norton AV. The
| virus check was negative.
|
| At one point in this process, the blue screen also said something about a
| bad driver.
|
| The next thing I tried, was to boot from an old NT CD. It was version 4 if
| that matters. It would not let me install because it could not locate a
Hard
| Disk. The guy who works on our MAC's thought it might be that the old NT
| could not communicate with an IDE Hard Disk. I was under the impression,
that
| the OS does not need to have any inherrent ability to communicate with a
| certain type of hard drive, but that the motherboard determines what type
of
| drive may be used.
|
| So, it comes down to the final question. Is our hard drive corrupt? Is
there
| some driver stored in Cache that is bad? Is there something wrong with our
| motherboard, or a cable in-between it and the hard disk? I am really in
over
| my head on this one. Thanks for any help.
|
| James