Windows Server 2000 - Check Disk Error - Windows found problems with the file system

Issue - After running check disk with the /F paramter windows shows this error message on and off.

Server: HP Proliant DL 380
Array Controllers and host adapters detected no errors.
Latest Support Pack has been installed.

IE: Ran the F parameter, the error would go away, then after a reboot, the message comes back.

The type of the file system is NTFS.
Volume label is Local Disk.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Repairing Usn Journal file record segment.
Usn Journal verification completed.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

  35551813 KB total disk space.
  10332639 KB in 25523 files.
      8496 KB in 2496 indexes.
         0 KB in bad sectors.
     70559 KB in use by the system.
     23056 KB occupied by the log file.
  25140118 KB available on disk.

       512 bytes in each allocation unit.
  71103626 total allocation units on disk.
  50280236 allocation units available on disk.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

noxchoGlobal Support CoordinatorCommented:
I suspect that one of your HDDs are failing. Test the drives using HDD vendor made tools one by one. You will find which one is the problem. If CHKDSK fixed once the error and it reoccurred with next start of system then problem is on HDD level.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Brian PiercePhotographerCommented:
I agree with noxcho. If chkdsk reports errors that can be fixed but then re-occur its a sign of an underlying hardware issue. Make sure you have a valid backup and plan to replace the disk(s) as soon as possible.

The System volume can not be repaired while windows is running. Can you try to do an error test using the grafic menu (properties of disk-tools-chack for errors). That will schedule an test at the next restart an can correct the errors.
If after the correction you detect more errors, then change the disks (one at the time and wait until the replication is complete).

The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Assuming that the RAID contains parity, i.,e RAID1/10/5/6 instead of RAID0, then there is nothing here to indicate that the problem has anything to do with the RAID.  

If a disk picks up a bad block, then next time it is read, the RAID controller will automatically repair it, based on parity.   If for some reason block #x fails on 2 disks, then you will get an unrecoverable read error.

If you had RAID0, then you would also see unrecoverable read error.

What you have here is plain, old-fashioned filesystem corruption due to anything from a BSOD, to improper shutdown, to bugs.   Treat it that way.

Chkdsks are not RAID diagnostics,  a RAID data consistency check is the appropriate hardware diagnostic.
0) make sure you can restore backup. following paths are dark and dangerous and can kill more than one disk in a mirror, destroy licences in iLO, eat babys etc...

1) Apply firmware maintenance CD - namely RAID disks.
2) Run diagnostics
3) Clean IML
4) Run diagnostics again

To install driver pack you must make sure that you "force reinstall and downgrade"

I suspect single disk in RAID failing which new disk firmware will either fix or detect.
(36 and 72MB disks are notorious for dying quickly)

run >fsutil dirty set c:
before win shutdown - to force chkdsk on boot.

I have found those versions as latest for your system:
Software 7.90 (w2000 latest)
Firmware 8.70
occreditAuthor Commented:
Thank you everyone for your suggestions. It's a great start. I will keep you posted.
occreditAuthor Commented:
Thanks for all the suggestions, but we will have to repair the OS route.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.