| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 84174 | 2007-10-26 22:38:00 | XP insists on checking drives | mzee (3324) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 605695 | 2007-10-26 22:38:00 | I am running XP pro. Have c,d,e,f partitions. Every time I boot xp it insists on checking drive "D" which only has backups on it. Never finds anything wrong, just wastes time! How do I curb its enthusiasm? | mzee (3324) | ||
| 605696 | 2007-10-26 23:26:00 | First click Start> Run> bring up a command prompt by typing in "CMD" and type " fsutil dirty query d: ". This queries the drive, and more than likely it will tell you that it is dirty. Next, type "CHKNTFS /X D:". The X tells Windows to NOT check that particular drive on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows. Once Windows has fully loaded, bring up another CMD prompt and type and now you want to do a Chkdsk manually by typing "Chkdsk /f /r d:". This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type "fsutil dirty query d:" and Windows will confirm that the dirty bit is not set on that drive. |
Agent_24 (57) | ||
| 605697 | 2007-10-27 00:59:00 | might be an idea to download and run the drive manufacturers diagnostic program maybe windoze is trying to tell you something.... | drcspy (146) | ||
| 605698 | 2007-10-28 00:08:00 | Thanks Agent 24. It worked a treat! The Auto Checkdisk was not picking it up. |
mzee (3324) | ||
| 605699 | 2007-10-28 03:46:00 | I wouldn't be telling windows to ignore it. Either you have some file structure problem on that partition or the drive itself has a problem. Fix it - don't ignore it. |
pctek (84) | ||
| 605700 | 2007-10-28 06:17:00 | My guess, he is using fat32 file system on a large disk using overlay software Microsofts reccomendation for this known error is low level format, Agents cure is well known and yes I know chkntfs (implies ntfs file system) but this command switches removes the dirty bit that scan disk cannot, but normally does. Our Network xp clients do this reguraly and I use this command with no determental effects |
beama (111) | ||
| 605701 | 2007-10-28 23:28:00 | My guess, he is using fat32 file system on a large disk using overlay software And how did you co9me to that conclusion? |
pctek (84) | ||
| 605702 | 2007-10-28 23:57:00 | Fix it - don't ignore it. You cant get better advice than that:thumbs: |
wainuitech (129) | ||
| 605703 | 2007-10-30 08:40:00 | The fix by "Agent 24" worked. It takes about 10 minutes so must do a full scan of the partition which is NTFS. It does not hide anything, it repairs it! | mzee (3324) | ||
| 605704 | 2007-10-30 08:45:00 | The fix by "Agent 24" worked. It takes about 10 minutes so must do a full scan of the partition which is NTFS. It does not hide anything, it repairs it! Yep it fixes it by telling it to ignore the possible problem that caused the chkdsk to "stick" in the first place. Sooner or later it will return, usually may cause some damage to files etc. Seen that happen lots. chkdsk /f locks the disk then fixes any errors on the disk, then unlocks it, if it doesn't unlock then you need to use the /x, this forces a dismount. But that normally means that there is a problem someplace on the disk, hence it locked and stayed locked. /x forces chkdsk to ignore the problem. so as Pcteck said - fix it don't ignore it. |
wainuitech (129) | ||
| 1 2 | |||||