chkdsk problems

markd60 · #1 03-30-2005, 03:11 AM

Hello, I am running windows xp home edition.
When I run CHKDSK, it finds errors. When I try to run CHKDSK /F it says it can't run because the volume is already in use, would I like to run it at the next startup. When it runs at startup, it runs CHKDSK, not CHKDSK /F and still doesn't fix the errors.
Very frustrated,
Please help
Thanks

markd60 · #2 03-30-2005, 09:59 AM

Let me add some more details:
The exact message when I run chkdsk is:

The type of the file system is NTFS.

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

78148160 KB total disk space.
7165184 KB in 39199 files.
11804 KB in 2771 indexes.
0 KB in bad sectors.
114652 KB in use by the system.
65536 KB occupied by the log file.
70856520 KB available on disk.

4096 bytes in each allocation unit.
19537040 total allocation units on disk.
17714130 allocation units available on disk.

Then, when I run chkdsk /f, it tells me that the the file system is NTFS and it can't lock the drive. can't run chkdsk because the volume is in use by another process. Would I like to this volume to be checked when the system restarts? I enter Y and restart the system, but it runs chkdsk, not chkdsk /f and does not fix the errors.
Is there a way to make chkdsk /f run or another program available that can fix my disk errors?
thanks

Ant · #3 03-31-2005, 12:25 AM

Voila!

http://www.softwaretipsandtricks.com...ad.php?t=19201

the answer to all your problems

Tooooo lazy to type it again.

bluecob · #4 03-31-2005, 02:13 AM

Hi Mark

After I ran the above I got the same messages but XP asked me if I wanted to run CHKDSK at startup. I pressed 'Y' and when I restarted the computer CHKDSK ran and fixed the errors. Hope this helps.

Ant · #5 04-01-2005, 01:29 AM

Ok Mark, just in case you haven't figured it out...

CHKDSK can check all drives during a windows session BUT NOT DRIVE C: for errors. Drive C: must be checked after reboot to allow CHKDSK access to the entire drive (which it can not whilst Windows is running).

So, if you want to check (and fix any errors found) a drive other than C: (F: for example), you can use Start -> Run and type "CHKDSK F: /f" (without quotes), which means:

CHECK DISK F: and FIX errors if found

You can change F: for another drive letter. If you wish to check drive C:, you can use the above, but you must reboot to allow the program to work. This is only true of drive C:.

(You can see from the above that you are confusing "F:" (the disk to be checked), with "/f" (the option to automatically fix any errors found).

markd60 · #6 04-01-2005, 11:24 PM

Well, I have read all the stuff on the microsoft website. I have run chkdsk from "My Computer", (drive letter, properties, tools) I have run it from a DOS prompt. I have tried everyone's suggestions.
I've run it at startup dozens of times, I purchased Norton Systemworks after spending hours on hold to ask if it could fix this problem and they said it could but it can't. It can't take over because the volume is in use and then runs the same 'ol microsoft chkdsk at startup.
I still get the same error message I posted previously. I don't know why it can be fixed for everybody but me.
I've had this problem on m 8088, my 386, my 486 my 100 mhz pentuim and now my 3.2 gig laptop. I've had this problem in DOS, windows 3.1, 95, 98 2000 and XP. XP is the only one I haven't been able to fix it on. It is the free space on the disk being misread. It has always been fixed in the past when it asks "convert lost chains to files? Y N". Then you find a folder on c: drive called "FOUND.000"
I think it can't be fixed because of NTFS.
performance-wise, it's a minor problem, but nevertheless, I'm considering starting over with a clean install. I don't have a Windows XP Home CD, just the disk that came with the laptop.
Sorry about my attitude but I'm disgusted, I've never been an XP fan.

Ant · #7 04-02-2005, 05:20 AM

I beg your pardon Mark, I misunderstood.

Try lower case parameters.

Also try chkdsk with the /r (recover) parameter to see if that recovers any data you may have lost.

markd60 · #8 04-02-2005, 08:45 AM

I ran CHKDSK /R and restarted the computer. CHKDSK /R ran OK but I don't think it even tries to fix errors.
Then after the computer restarted I ran CHKDSK and got this:
___
C:\>chkdsk
The type of the file system is NTFS.

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)...
Correcting error in index $I30 for file 35765.
Deleting index entry enaleful.134 in index $I30 of file 35765.
Deleting index entry ExItem4946_avenge$201.5$20microdefs25$20nav2005_mi crodefsb.
curdefs_symalllanguages in index $I30 of file 35765.
Deleting index entry ExItem5088_symantec$20trusted$20application$20list _1.1_engl
ish in index $I30 of file 35765.
Deleting index entry EXITEM~1.1_E in index $I30 of file 35765.
Deleting index entry EXITEM~1.CUR in index $I30 of file 35765.
Deleting index entry TriFile_norton$20utilities$20nt_18.0.0.62_english in index
$I30 of file 35765.
Deleting index entry TRIFIL~1.62_ in index $I30 of file 35765.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

C:\>chkdsk
The type of the file system is NTFS.

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.

78148160 KB total disk space.
7550440 KB in 41171 files.
12260 KB in 2918 indexes.
0 KB in bad sectors.
114656 KB in use by the system.
65536 KB occupied by the log file.
70470804 KB available on disk.

4096 bytes in each allocation unit.
19537040 total allocation units on disk.
17617701 allocation units available on disk.

C:\>chkdsk
The type of the file system is NTFS.

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

78148160 KB total disk space.
7551400 KB in 41171 files.
12260 KB in 2918 indexes.
0 KB in bad sectors.
114656 KB in use by the system.
65536 KB occupied by the log file.
70469844 KB available on disk.

4096 bytes in each allocation unit.
19537040 total allocation units on disk.
17617461 allocation units available on disk.

C:\>

C:\>chkdsk /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y

This volume will be checked the next time the system restarts.

C:\>

___

Notice that the first time I ran chkdsk, It looks like it tried to do something even though it was not in the /F mode, then the second time it didn't find errors, then the third time it did.
Now, I get the same errors when I run CHKDSK. In other words, nothing has changed. You see, on startup, I think it runs CHKDSK, not CHKDSK /F.
Shouldn't it ask me if I want to correct errors after it finds them? Even when I ran CHKDSK /R, I don't think it tried to corrrect anything.
I'm starting to think I have a hardware problem.

Ant · #9 04-02-2005, 09:39 AM

I'm sorry if I seem condescending, but I take it you are typing:

chkdsk /f /r when it doesn't work?

Try running it from My Computer -> C: (right-click) -> properties -> tools (tab) -> "Check Now" and enable both fix and recover options and reboot.

If it still won't work and if you can, remove your drive, attach it as a slave to another computer and run chkdsk from there.

markd60 · #10 04-03-2005, 09:49 PM

I ran it from My Computer, both fix and recover checked, and I still have the same error when I run chkdsk from the DOS prompt. I can tell my machine is slowed down by this. I guesss I can format or, like you said, put the drive in somewhere else as a slave.
Like I said before, I've never been a Windows XP fan, even less of one now. Maybe I'll put 2000 on it.....
I do appreciate the help.

Ant · #11 04-04-2005, 10:07 AM

It could be that the chkdsk program or one of its support files is damaged or corrupted. It seems a little drastic (not as drastic as a format) but you could try the recovery console on the cdrom, which should restore any damaged/corrupted or missing files.

markd60 · #12 04-04-2005, 08:55 PM

I haven't even unwrapped that disk, I don't even know what's on it!

Ant · #13 04-04-2005, 11:03 PM

Run setup off the xp cdrom and choose the Recovery option from the menu. This should restore your installation without effecting your settings/data.

markd60 · #14 04-06-2005, 08:01 PM

I removed my hard drive and ran chkdsk on it in another machine as a slave. I had no indication of errors being repaired. I ran chkdsk from a DOS prompt and got no errors found, I put the drve back in the laptop and got the same error.
"Correcting errors in the Volume Bitmap.
Windows found problems with the file system."

My recovery disk will format the hard drive. I don't have XP home on CD.

Ant · #15 04-08-2005, 10:35 AM

Anyone else have any ideas?