Windows Forum / Windows XP / General Topics 1 / May 2008
Chkdisk Question...
|
|
Thread rating:  |
John - 12 May 2008 02:14 GMT How often, if at all, should chkdisk be run on a computer running Windows XP?
John
Colin Barnhorst - 12 May 2008 03:17 GMT Chkdsk is not routine maintenance. It should not be run without a compelling reason.
> How often, if at all, should chkdisk be run on a computer running Windows > XP? > > John Bill in Co. - 12 May 2008 04:31 GMT Besides which, the version that comes with WinXP is just way too limited in what it reports (as compared with that in Win9x).
> Chkdsk is not routine maintenance. It should not be run without a > compelling reason. [quoted text clipped - 3 lines] >> >> John Colin Barnhorst - 12 May 2008 15:38 GMT They are different utilities.
> Besides which, the version that comes with WinXP is just way too limited > in what it reports (as compared with that in Win9x). [quoted text clipped - 7 lines] >>> >>> John Bill in Co. - 12 May 2008 17:24 GMT Sorry, I was really thinking of SFC. (Not chkdsk). Although, in retrospect, even chkdsk seems a bit more limited in its options (and more automated).
> They are different utilities. > [quoted text clipped - 9 lines] >>>> >>>> John ju.c - 12 May 2008 07:33 GMT Run chkdsk:
1. After moving or copying many files. 2. After uninstalling a large program like Nero or Photoshop. 3. Before installing a large program like Nero or Photoshop. 4. Always run chkdsk before you run a full defrag. 5. You cannot run it too often. 6. Unless otherwise noted, always select to fix found errors.
See:
Seven Golden Rules for Disk Maintenance http://www.windowsnetworking.com/articles_tutorials/Troubleshooting-File-System- Problems.html
"5. Run chkdsk /r on a regular basis. This command finds bad sectors on your disk and tries to fix them by recovering data from them and moving it elsewhere. You can run this command either from a command-prompt window or from the Recovery Console if you can't boot your system normally. Remember that when you try and run chkdsk.exe on your system or boot volume, Windows configures autochk.exe (the boot version of chkdsk.exe) to run at your next reboot. This means you'll need to schedule downtime for your server when you perform this kind of maintenance so that autochk.exe can run."
ju.c
> How often, if at all, should chkdisk be run on a computer running > Windows XP? > > John Unknown - 12 May 2008 15:25 GMT None of those are compelling reasons to run chkdsk. This is completely hogwash.
> Run chkdsk: > [quoted text clipped - 26 lines] >> >> John Malke - 12 May 2008 16:05 GMT > Run chkdsk: > [quoted text clipped - 4 lines] > 5. You cannot run it too often. > 6. Unless otherwise noted, always select to fix found errors. All of the above is incorrect.
Chkdsk should *never* been run unless a problem is suspected *and* if all data is backed up onto external media.
Malke
 Signature MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic!
Colin Barnhorst - 12 May 2008 17:41 GMT Ed Bott, in his Windows XP Inside and Out, second edition, pages 1240 ff, does advise running chkdsk proactively to catch file system errors before trouble breaks out.
However, I have never heard of anyone advising users to run chkdsk as a clean up tool preceding or following basic copy, move, deletion, installation, or uninstallation of files and software. Defragmentation yes, chkdsk no.
>> Run chkdsk: >> [quoted text clipped - 11 lines] > > Malke Malke - 12 May 2008 21:42 GMT > Ed Bott, in his Windows XP Inside and Out, second edition, pages 1240 ff, > does advise running chkdsk proactively to catch file system errors before > trouble breaks out. So I've heard. Then I guess I have to disagree with Ed Bott. As far as I'm concerned, Chkdsk is for when things go sour and not to be used lightly.
Best regards,
Malke
 Signature MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic!
Bruce Chambers - 13 May 2008 01:48 GMT > Run chkdsk: > > 1. After moving or copying many files. Why? Please provide a technical reason.
> 2. After uninstalling a large program like Nero or Photoshop. Why? Please provide a technical reason.
> 3. Before installing a large program like Nero or Photoshop. Why? Please provide a technical reason.
> 4. Always run chkdsk before you run a full defrag. Why? Please provide a technical reason.
> 5. You cannot run it too often. Utter nonsense, unless one's sole goal is to create utterly unnecessary wear and tear on the hard drive.
> 6. Unless otherwise noted, always select to fix found errors. No. The correct answer would be "*ONLY* to seek/fix errors reported by the OS."
> See: > > Seven Golden Rules for Disk Maintenance > http://www.windowsnetworking.com/articles_tutorials/Troubleshooting-File-System- Problems.html Er.... That link is about Windows Server 2003, *NOT* WinXP. They're completely different operating systems, you know. (And even then I'd call it bad advice.)
 Signature Bruce Chambers
Help us help you: http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/default.aspx/kb/555375
They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin
Many people would rather die than think; in fact, most do. ~Bertrand Russell
The philosopher has never killed any priests, whereas the priest has killed a great many philosophers. ~ Denis Diderot
windmap - 12 May 2008 08:31 GMT After an Improper or hard shutdown.When you cant boot/login to windows.If you recieve errors when strating windows. CHKDSK Checks windows file system for errors.
> How often, if at all, should chkdisk be run on a computer running Windows > XP? > > John Ken Blake, MVP - 12 May 2008 19:39 GMT > How often, if at all, should chkdisk be run on a computer running Windows XP? It should be run in response to a disk problem or suspected problem. Otherwise not at all.
 Signature Ken Blake, Microsoft MVP - Windows Desktop Experience Please Reply to the Newsgroup
Bill in Co. - 12 May 2008 19:51 GMT >> How often, if at all, should chkdisk be run on a computer running Windows >> XP? > > It should be run in response to a disk problem or suspected problem. > Otherwise not at all. OR, I'd say: just run occasionally, to make sure there isn't any problem that we're unaware of (which has happened, on occasion).
John John (MVP) - 12 May 2008 20:41 GMT >>>How often, if at all, should chkdisk be run on a computer running Windows >>>XP? [quoted text clipped - 4 lines] > OR, I'd say: just run occasionally, to make sure there isn't any problem > that we're unaware of (which has happened, on occasion). That is like getting "preemptive surgery" for no reason at all. If the disk isn't "dirty" it has no errors to fix and running chkdsk is completely unnecessary.
John
Bill in Co. - 12 May 2008 20:52 GMT >>>> How often, if at all, should chkdisk be run on a computer running >>>> Windows [quoted text clipped - 11 lines] > > John Trouble is, I've, on occasion, run it (without any switches, which is even safer), and found there were a few errors, which it has reported resolving. So I'd say it's more like going in for a checkup.
Colin Barnhorst - 12 May 2008 21:28 GMT Occaisonally? As in "just for the heck of it"?
>>> How often, if at all, should chkdisk be run on a computer running >>> Windows XP? [quoted text clipped - 4 lines] > OR, I'd say: just run occasionally, to make sure there isn't any problem > that we're unaware of (which has happened, on occasion). Bill in Co. - 12 May 2008 21:41 GMT If it's been awhile, and I remember, I do it. I wouldn't say "just for the heck of it". As I said before, it's kinda like going in for a checkup. And I'd rather know about it first before making a TI image backup (again, running it w/o the switches, which is safer)
> Occasionally? As in "just for the heck of it"? > [quoted text clipped - 6 lines] >> OR, I'd say: just run occasionally, to make sure there isn't any problem >> that we're unaware of (which has happened, on occasion). Colin Barnhorst - 12 May 2008 22:03 GMT You can simply run chkntfs x: or use R McCarty's suggested FSUtil command to see if the dirty bit is set. Why keep the drive churning through a lengthy chkdsk run?
> If it's been awhile, and I remember, I do it. I wouldn't say "just for > the heck of it". [quoted text clipped - 13 lines] >>> problem >>> that we're unaware of (which has happened, on occasion). R. McCarty - 12 May 2008 21:49 GMT Just open a Command Prompt Window & type FSUtil Dirty Query C: to determine a volume's health *Substitute C: with whatever drive you wish to check
> Occaisonally? As in "just for the heck of it"? > [quoted text clipped - 6 lines] >> OR, I'd say: just run occasionally, to make sure there isn't any problem >> that we're unaware of (which has happened, on occasion). Bruce Chambers - 13 May 2008 01:42 GMT > How often, if at all, should chkdisk be run on a computer running Windows XP? > > John Only when an error is detected by the OS.
 Signature Bruce Chambers
Help us help you: http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/default.aspx/kb/555375
They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin
Many people would rather die than think; in fact, most do. ~Bertrand Russell
The philosopher has never killed any priests, whereas the priest has killed a great many philosophers. ~ Denis Diderot
|
|
|