CHKDSK problems reported

I noticed that my computer recently on either bootup or reboot started running CHKDSK on it own at the beginning of the boot cycle. I went to a command prompt within windows and ran CHKDSK in read only and got a report of problems (appended to the bottom of this e-mail). I tried to run CHKDSK /f within windows and it wouldn't let me. So I booted to a BartPE disk, which dismounted C and allowed me to run CHKDSK /F. This morning, again FROM WITHIN WINDOWS, I ran CHKDSK in read only just to make sure I had indeed fixed the problem and I got the following report:

File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is recovering lost files.
Recovering orphaned file I2_LDVP.TMP (33699) into directory file 29862.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

  78116030 KB total disk space.
  14776388 KB in 42823 files.
     14092 KB in 3405 indexes.
         0 KB in bad sectors.
    365838 KB in use by the system.
     65536 KB occupied by the log file.
  62959712 KB available on disk.

      4096 bytes in each allocation unit.
  19529007 total allocation units on disk.
  15739928 allocation units available on disk.

What's my next step, please? Thanks.
normanmlAsked:
Who is Participating?
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.

Steve KnightIT ConsultancyCommented:
chkdsk /f should run (or give you the option to) after the next reboot if it can't dismount the disk (i.e. it is your system drive).  Is it not doing that?

Steve
0
Steve KnightIT ConsultancyCommented:
I wouldn't normally suggest running chkdsk from another OS on a disc, any difference in the way it treats the disk and who knows what it might do.  Run a chdksk /f from cmd.exe in Windows, accept that it will run after next reboot. shutdown and restart (not standby or hibernate etc.) and let it run to completion.  Do the same again to make sure it is OK.
0
normanmlAuthor Commented:
Thanks. I have repeatedly invoked chkdsk /f from the command prompt within XP and then have repeatedly rebooted and let chkdsk go through it's routines. (How do you pause the message that appears after it runs on bootup?) From what I can see of the message, chkdsk seems to have corrected the problems. But when I go back to the command prompt in windows and run chkdsk WITHOUT the /f switch, this just to get a report to see if the problem is fixed, I get the message I put in my initial post. In other words, the messege I get from chkdsk /f after it runs on bootup -- which seems to indicate everything is okay -- is different than the message I get when I think try to double check the disk from within windows by running chkdsk in read-only cmd.exe, a command prompt. What do I get two different messages? Is the message I get from running chkdsk in read-only from within WIN meaningless? Or is something continually corrupting the disk after bootup? Also is there a relationship between defragging and chkdsk? I defrag daily with Diskeeper 10. Last time I tried to run it, I got a message to chkdsk first, which I did, and have done again and again.
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

Steve KnightIT ConsultancyCommented:
I'd stop the defragging for a bit, yuo don't need to defrag that often.  Is it always certain files it reports, e.g. something that gets created that day, maybe a dodgy app?

Or it could just be your hard disc is on the way out... but I bet it stops if you stop the defragging?

Steve

0

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
normanmlAuthor Commented:
Thanks, Steve. I just ran chkdsk /f on two restarts. Then ran it from WIN in read only and got:

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.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

I'll knock off the degragging for a day or, see what happens, and report back here.
0
RGRodgersCommented:
I'd suggest running a deep disk diagnostic like Spinrite to see if your drive is failing.
0
normanmlAuthor Commented:
Hm Spinrite. I looked in Disk Management and it reported the disk healthy. Volume size is okay, no drop-off, and I hear NO clicking or grinding from the disk. I know Spinrite goes way beyond Disk Management in its report.
0
normanmlAuthor Commented:
I stopped defragging for two days. I ran chkdsk /f at restart four times in a row. Then I checked the four Winlog for each run. I either get "Cleaning up minor inconsistencies on the drive," or I get the following list each time I run it:

Cleaning up minor inconsistencies on the drive.
Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.

(When I run chkdsk from within windows I still get the message that it found errors on the drive and it tells me to run it at startup.) So, what do the messages above mean? Do that mean that my H-drive has problems and I need to invest in Spinrite, or do they meaning nothing.  

If you take a look at http://www.experts-exchange.com/Operating_Systems/WinXP/Q_20990069.html you'll see that one of the experts suggest going to the recovery console (booting from the original XP CD) and running chkdsk from that.

Suggestions, please. Thanks.
0
normanmlAuthor Commented:
Steve, I'm going to go ahead and award the points, close the thread, and open another one with a bit more information just to see if I can provoke more comment. Thanks and feel free to weigh in again.
0
Steve KnightIT ConsultancyCommented:
Thanks for the points, though not so keen on "B" grades..... you've knocked me over the 300,000 mark in MSDOS to make me a "Wizard", haha!

Good luck with getting more info, not sure there is a lot anyone can tell without being there but you never know.

Steve
0
normanmlAuthor Commented:
How so I change the grade immediately?
0
Steve KnightIT ConsultancyCommented:
Don't worry about it!
0
normanmlAuthor Commented:
Well, thanks for the help and sorry about the oversight. Should have known better -- I'm a college professor for holy sakes.
0
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 DOS

From novice to tech pro — start learning today.