04-08-2005, 11:43 AM
|
 |
Registered User
|
|
Join Date: Apr 2005
Posts: 162
|
|
|
Recovery Console
You can download Recovery Console from Microsoft's site which you need to put in 6 floppy disks, using that you can run CHKDSK /f
Windows XP HOME
http://www.microsoft.com/downloads/d...5-BD5AFEE126D8
Windows XP PRO
http://www.microsoft.com/downloads/d...7-4FED408EA73F
Instructions
Click the Download link to start the download, or choose a different language from the drop-down list and click Go.
Do one of the following:
To start the installation immediately, click Open or Run this program from its current location.
To copy the download to your computer for installation at a later time, click Save or Save this program to disk.
The file will extract to 6 floppy disks.
Now boot to Disk #1 and continue through #6 as prompted.
(Boot to the 1st disk by removing all disks from the CD or Floppy drive and then inserting the 1st floppy of the 6 disk set and turning on the computer).
Now select R for repair.
Now it will ask which Windows installation to log in to. Select 1.
It may ask for the Administrator password, if it does, hit enter. Then it should take you to an A:\> Prompt.
From A: Prompt type CHKDSK /R and press the Enter key. (make sure there is a space between CHKDSK and /R)
Now if it asks about missing AUTOCHK.EXE type in the path of C:\Windows\System32 or C:\Windows\I386 if the first path did not work.
After that completes, remove disk #6 and reboot.
(If you don't have a floppy, you can borrow any XP CD, make sure it's the sameas you have if it's Home or Pro, just use the Recovery Option there)
Hope this helps...
|
04-08-2005, 12:26 PM
|
|
Registered User
|
|
Join Date: Apr 2005
Posts: 2
|
|
Quote:
|
Originally Posted by Ant
Anyone else have any ideas?
|
Hi guys,
This one is actually pretty easy to fix. Getting the checkdisk stuck seems to be pretty common in XP. So lets fix it!
First, check to see if the disk/partition is actually DIRTY (IE broken/lost chains, bad cluster data etc), which it probably is. Open a command prompt. Type fsutil dirty query c: and replace the c: with whatever drive letter you wish to check. It will tell you if the disk is DIRTY or NOT.
Assuming that is is DIRTY, you will need to check it and repair damages. But, you will also need to reset your scheduled chkdsk that will forever try to run upon bootup (hence it being stuck).
Now use the chkntfs utility to reset this. From the command prompt, type chkntfs /d. This will reset the checkdisk but it will still have to run on the next boot up, but after that, it will no longer attempt to run every time and it removes it from the scheduler which will allow normal checkdisk access to the drive again. (You can also input chkntfs /? for a list of all the NTFS utility commands.)
Reboot and let the checkdisk run this last time.
Once you are back into the XP console, go to My Computer, right click the drive that you need to check, go to Tools and then go to Error-Checking and click the Check Now button. Select both options for automatically fix errors and scan disk for bad clusters. Depending on the size of the disk, this will take anywhere from a while to a very long while (6 Phases I think).
When that is finally done, the drive should be fixed of problems. Now it is highly recommended to do a defragmentation of the drive so everything gets moved and placed in proper order. Once the defrag is complete, check again for DIRTY drives using the fsutil dirty query c: command again. Your drive(s) should be NOT DIRTY now.
Reboot to make sure the scheduled checkdisk no longer launches on reboot (it should not) and then drink a beer or two and celebrate fixing this issue without the hassle of reloading the OS! 
MetalKnight
|
04-09-2005, 07:46 AM
|
|
Registered User
|
|
Join Date: Mar 2005
Location: Cayman Islands
Posts: 15
|
|
|
Ok, I typed "fsutil dirty query c:" at the command prompt; It was NOT dirty.
Just for the record, chkdsk does not run every time the machine boots up, only when I schedule it.
I typed "chkntfs /d" and it returned to the cursor without telling me anything.
I rebooted and it did not run chkdsk on boot-up.
From the "My Computer" C drive console, I ran error checking with both options checked.
I still have the same problem:
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
I did the whole thing again, adding a "chkdsk /f" after "chkntfs /d" so that it would run at startup and still, no changes.
|
04-09-2005, 07:59 AM
|
|
Registered User
|
|
Join Date: Mar 2005
Location: Cayman Islands
Posts: 15
|
|
|
I've ran this disk as a slave in another machine, it doesn't find any errors. Monday, I'll plug it in as the master and see if I have the problem on that machine too.
I can tell there's the problem by the performance of this machine. Slow refreshing the screen, when I open a program, it acts like it has to think about awhile before opening it...
this is a relative new machine, a Toshiba Satellite P35-S609. the problem started after I put in a data CD it couldn't read, said the files were corrupt on the CD. The file that I was trying to open was a plain text file.
|
04-13-2005, 05:12 AM
|
|
Registered User
|
|
Join Date: Apr 2005
Posts: 3
|
|
Quote:
|
Originally Posted by MetalKnight
Hi guys,
This one is actually pretty easy to fix. Getting the checkdisk stuck seems to be pretty common in XP. So lets fix it!
First, check to see if the disk/partition is actually DIRTY (IE broken/lost chains, bad cluster data etc), which it probably is. Open a command prompt. Type fsutil dirty query c: and replace the c: with whatever drive letter you wish to check. It will tell you if the disk is DIRTY or NOT.
Assuming that is is DIRTY, you will need to check it and repair damages. But, you will also need to reset your scheduled chkdsk that will forever try to run upon bootup (hence it being stuck).
Now use the chkntfs utility to reset this. From the command prompt, type chkntfs /d. This will reset the checkdisk but it will still have to run on the next boot up, but after that, it will no longer attempt to run every time and it removes it from the scheduler which will allow normal checkdisk access to the drive again. (You can also input chkntfs /? for a list of all the NTFS utility commands.)
Reboot and let the checkdisk run this last time.
Once you are back into the XP console, go to My Computer, right click the drive that you need to check, go to Tools and then go to Error-Checking and click the Check Now button. Select both options for automatically fix errors and scan disk for bad clusters. Depending on the size of the disk, this will take anywhere from a while to a very long while (6 Phases I think).
When that is finally done, the drive should be fixed of problems. Now it is highly recommended to do a defragmentation of the drive so everything gets moved and placed in proper order. Once the defrag is complete, check again for DIRTY drives using the fsutil dirty query c: command again. Your drive(s) should be NOT DIRTY now.
Reboot to make sure the scheduled checkdisk no longer launches on reboot (it should not) and then drink a beer or two and celebrate fixing this issue without the hassle of reloading the OS!
MetalKnight |
Hello there,
I am new to forums and such, but I was looking for help concerning the same chkdsk problem.
I am also a newbie concerning computing. I know all about the programs I need for work and such, but not to much in the way of walking around the system at all.
Soooo, I have done the above, got command prompt and checked for dirty drive, which it is. Now what? How do I "clean" itMetalKnight, you say I need to check it and repair it, how?
I went through the chkdsk again at reboot, but nothing has changed for me. I am still getting this message when trying defrag:
Disk Defragmenter has detected that chkdsk is scheduled to run in the volume: (D 
Please run Chkdsk /f
And when I do I get this:
Chkdsk cannot run because the volume is in use by another process...blah blah blah, no I didn't schedule it to run on the next start, because I have in the past and it hasn't done anything.
Please help me as well, as I really don't want to reformat. i honestly don't know how anyways.....
Mr Lube
|
04-13-2005, 05:37 AM
|
|
Registered User
|
|
Join Date: Apr 2005
Posts: 3
|
|
Yep
As I suspected....
after running the chkdsk again at login, it said an unspecified error has occured....
Not sure what to do
Mr Lube
|
04-15-2005, 01:23 AM
|
|
Registered User
|
|
Join Date: Apr 2005
Posts: 64
|
|
Quote:
|
Originally Posted by markd60
I've ran this disk as a slave in another machine, it doesn't find any errors. Monday, I'll plug it in as the master and see if I have the problem on that machine too.
I can tell there's the problem by the performance of this machine. Slow refreshing the screen, when I open a program, it acts like it has to think about awhile before opening it...
this is a relative new machine, a Toshiba Satellite P35-S609. the problem started after I put in a data CD it couldn't read, said the files were corrupt on the CD. The file that I was trying to open was a plain text file.
|
You might want to try a defrag program to see if that will fix your problem. Some companies will let you download a free trial copy. |
04-17-2005, 01:27 AM
|
|
Registered User
|
|
Join Date: Mar 2005
Location: Cayman Islands
Posts: 15
|
|
|
I will try a different defrag program. I didn't try to plug the drive in as a master in another machine because, Duh! - different hardware profiles.
Mr Lube, let me know what you find and I'll do the same. It sounds like different symptoms but may have the same solution.
Thanks for all everybodies help. Don' t give up!
|
04-20-2005, 07:50 PM
|
|
Registered User
|
|
Join Date: Apr 2005
Posts: 3
|
|
|
Yes, will do markd60...
|
04-20-2005, 10:35 PM
|
|
Registered User
|
|
Join Date: Mar 2005
Location: Cayman Islands
Posts: 15
|
|
|
I downloaded and ran Diskeeper but it didn't change a thing.
|
04-21-2005, 10:34 AM
|
 |
Registered User
|
|
Join Date: Apr 2004
Location: Bangkok, Thailand
Posts: 911
|
|
Mark, run scannow-sfc just in case. (You seem to have tried pretty much everything else )
http://www.updatexp.com/scannow-sfc.html
See what turns up...
__________________
.
There are only two men I trust with my computer. One's me. The other isn't you. 
.
|
04-28-2005, 10:12 AM
|
|
Registered User
|
|
Join Date: Mar 2005
Location: Cayman Islands
Posts: 15
|
|
|
I ran it the other day, I thought I replied...
It took a while to run, then I ran chkdsk and got the same message......
The only thing left is to reinstall the OS....
|
10-23-2006, 11:12 AM
|
|
Registered User
|
|
Join Date: Oct 2006
Posts: 1
|
|
|
I have the same problem!
I have the same problem.
CHKDSK finds errors. But even after I do CHKDSK /F or /X, which seems to complete successfully, and check again, there are still problems remaining!
I just replaced my harddisk, and transfered the system using Acronis Migrateeasy. But the problem is still there!
Neither the old HD or the new HD shows any SMART errors.
I have ran SPINRITE 6 level 2, and that didn't find any errors. But the problems are still found when I run CHKDSK.
I also did the SFC recommended here.
I suspect I've had a bad DIMM which may have caused this. But it's replaced.
Here is the verbose output of chkdsk this time (the files it complains at are different every time):
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)...
100 percent completed.
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
100 percent completed.
Index verification completed.
CHKDSK is recovering lost files.
Recovering orphaned file 006.part.met (10363) into directory file 20115.
Recovering orphaned file 006PAR~1.MET (10363) into directory file 20115.
Recovering orphaned file 006PAR~1.STA (64934) into directory file 20115.
Recovering orphaned file 006.part.stats (64934) into directory file 20115.
Recovering orphaned file 006PAR~1.SET (67357) into directory file 20115.
Recovering orphaned file 006.part.settings (67357) into directory file 20115.
Recovering orphaned file 006PAR~1.BAK (67574) into directory file 20115.
Recovering orphaned file 006.part.met.bak (67574) into directory file 20115.
CHKDSK is verifying security descriptors (stage 3 of 3)...
100 percent completed.
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.
312568640 KB total disk space.
115218860 KB in 96345 files.
34304 KB in 7480 indexes.
0 KB in bad sectors.
193740 KB in use by the system.
65536 KB occupied by the log file.
197121736 KB available on disk.
4096 bytes in each allocation unit.
78142160 total allocation units on disk.
49280434 allocation units available on disk.
|
12-15-2006, 02:05 PM
|
|
Registered User
|
|
Join Date: Dec 2006
Posts: 1
|
|
|
I have *exactly* the same problem. It stopped once when I changed the usb 4plug but it has come back. No apparent effects computer works as far as I can tell. But I would like to get rid of it
|
09-13-2007, 01:01 AM
|
|
Registered User
|
|
Join Date: Sep 2007
Posts: 2
|
|
|
Hi I've been having the same exact problem and i was wondering if anyone had ever found a resolution to this. I have it happening on 3 different computers. Every time I run chkdsk it keeps finding more errors but the disk is NOT dirty, and numerous hard drive diagnostic programs say there is nothing wrong with the disk. Any help would be greatly appreciated.
C:\Documents and Settings\Compaq_Administrator>chkdsk
The type of the file system is NTFS.
Volume label is PRESARIO.
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 29851.
Correcting error in index $I30 for file 85902.
Deleting index entry 794e24.rbf in index $I30 of file 17620.
Deleting index entry 1.Product.Inventory.LiveUpdate in index $I30 of file 26049.
Deleting index entry 1.Settings.LiveUpdate in index $I30 of file 26049.
Deleting index entry 1PRODU~1.LIV in index $I30 of file 26049.
Deleting index entry 1SETTI~1.LIV in index $I30 of file 26049.
Deleting index entry 2.Product.Inventory.LiveUpdate in index $I30 of file 26049.
Deleting index entry 2.Settings.LiveUpdate in index $I30 of file 26049.
Deleting index entry 2PRODU~1.LIV in index $I30 of file 26049.
Deleting index entry 2SETTI~1.LIV in index $I30 of file 26049.
Deleting index entry 3.Product.Inventory.LiveUpdate in index $I30 of file 26049.
Deleting index entry 3.Settings.LiveUpdate in index $I30 of file 26049.
Deleting index entry 3PRODU~1.LIV in index $I30 of file 26049.
Deleting index entry 3SETTI~1.LIV in index $I30 of file 26049.
Deleting index entry Product.Inventory.LiveUpdate in index $I30 of file 26049.
Deleting index entry PRODUC~1.LIV in index $I30 of file 26049.
Deleting index entry Settings.LiveUpdate in index $I30 of file 26049.
Deleting index entry SETTIN~1.LIV in index $I30 of file 26049.
Deleting index entry Persist.BAK in index $I30 of file 29541.
Deleting index entry Persist.Dat in index $I30 of file 29541.
Deleting index entry A0014005.msi in index $I30 of file 85902.
Deleting index entry A0014006.rbf in index $I30 of file 85902.
Deleting index entry A0014007.rbf in index $I30 of file 85902.
Deleting index entry A0014008.rbf in index $I30 of file 85902.
Deleting index entry A0014009.rbf in index $I30 of file 85902.
Deleting index entry A0014010.rbf in index $I30 of file 85902.
Deleting index entry A0014011.rbf in index $I30 of file 85902.
Deleting index entry A0014012.rbf in index $I30 of file 85902.
Deleting index entry A0014013.rbf in index $I30 of file 85902.
Deleting index entry A0014014.rbf in index $I30 of file 85902.
Deleting index entry A0014015.rbf in index $I30 of file 85902.
Deleting index entry A0014016.rbf in index $I30 of file 85902.
Deleting index entry A0014017.rbf in index $I30 of file 85902.
Deleting index entry A0014018.rbf in index $I30 of file 85902.
Deleting index entry A0014019.rbf in index $I30 of file 85902.
Deleting index entry A0014020.rbf in index $I30 of file 85902.
Deleting index entry A0014021.rbf in index $I30 of file 85902.
Deleting index entry A0014022.rbf in index $I30 of file 85902.
Deleting index entry A0014023.rbf in index $I30 of file 85902.
Deleting index entry A0014024.rbf in index $I30 of file 85902.
Deleting index entry A0014025.rbf in index $I30 of file 85902.
Deleting index entry A0014026.rbf in index $I30 of file 85902.
Deleting index entry A0014027.rbf in index $I30 of file 85902.
Deleting index entry A0014028.rbf in index $I30 of file 85902.
Deleting index entry A0014029.rbf in index $I30 of file 85902.
Deleting index entry A0014030.rbf in index $I30 of file 85902.
Deleting index entry A0014031.rbf in index $I30 of file 85902.
Deleting index entry A0014032.rbf in index $I30 of file 85902.
Deleting index entry A0014033.rbf in index $I30 of file 85902.
Deleting index entry A0014034.rbf in index $I30 of file 85902.
Deleting index entry A0014035.rbf in index $I30 of file 85902.
Deleting index entry A0014036.rbf in index $I30 of file 85902.
Deleting index entry A0014037.rbf in index $I30 of file 85902.
Deleting index entry A0014038.rbf in index $I30 of file 85902.
Deleting index entry A0014039.rbf in index $I30 of file 85902.
Deleting index entry A0014040.dll in index $I30 of file 85902.
Deleting index entry A0014041.cat in index $I30 of file 85902.
Deleting index entry A0014042.INF in index $I30 of file 85902.
Deleting index entry A0014043.sys in index $I30 of file 85902.
Deleting index entry A0014044.cat in index $I30 of file 85902.
Deleting index entry A0014045.INF in index $I30 of file 85902.
Deleting index entry A0014046.sys in index $I30 of file 85902.
Deleting index entry A0014047.dll in index $I30 of file 85902.
Deleting index entry A0014048.sys in index $I30 of file 85902.
Deleting index entry A0014049.vxd in index $I30 of file 85902.
Deleting index entry A0014050.dll in index $I30 of file 85902.
Deleting index entry A0014051.dll in index $I30 of file 85902.
Deleting index entry A0014052.cat in index $I30 of file 85902.
Deleting index entry A0014053.INF in index $I30 of file 85902.
Deleting index entry A0014054.sys in index $I30 of file 85902.
Deleting index entry A0014055.cat in index $I30 of file 85902.
Deleting index entry A0014056.INF in index $I30 of file 85902.
Deleting index entry A0014057.sys in index $I30 of file 85902.
Deleting index entry A0014058.dll in index $I30 of file 85902.
Deleting index entry A0014059.sys in index $I30 of file 85902.
Deleting index entry A0014060.vxd in index $I30 of file 85902.
Deleting index entry A0014061.dll in index $I30 of file 85902.
Deleting index entry A0014062.dll in index $I30 of file 85902.
Deleting index entry A0014063.cat in index $I30 of file 85902.
Deleting index entry A0014064.INF in index $I30 of file 85902.
Deleting index entry A0014065.sys in index $I30 of file 85902.
Deleting index entry A0014066.cat in index $I30 of file 85902.
Deleting index entry A0014067.INF in index $I30 of file 85902.
Deleting index entry A0014068.sys in index $I30 of file 85902.
Deleting index entry A0014069.dll in index $I30 of file 85902.
Deleting index entry A0014070.sys in index $I30 of file 85902.
Deleting index entry A0014071.vxd in index $I30 of file 85902.
Deleting index entry A0014072.dll in index $I30 of file 85902.
Deleting index entry A0014073.scr in index $I30 of file 85902.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
C:\Documents and Settings\Compaq_Administrator>chkdsk
The type of the file system is NTFS.
Volume label is PRESARIO.
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 recovering lost files.
Recovering orphaned file Dc4 (28451) into directory file 24111.
Recovering orphaned file Dc3 (77044) into directory file 24111.
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.
108228928 KB total disk space.
48381248 KB in 99396 files.
35308 KB in 7753 indexes.
0 KB in bad sectors.
198756 KB in use by the system.
65536 KB occupied by the log file.
59613616 KB available on disk.
4096 bytes in each allocation unit.
27057232 total allocation units on disk.
14903404 allocation units available on disk.
C:\Documents and Settings\Compaq_Administrator>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:\Documents and Settings\Compaq_Administrator>fsutil dirty query
Usage : fsutil dirty query <volume pathname>
Eg : fsutil dirty query C:
C:\Documents and Settings\Compaq_Administrator>fsutil dirty query c:
Volume - c: is NOT Dirty
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Rate This Thread |
 Linear Mode
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
All times are GMT -5. The time now is 11:59 PM. |
|
|
|
