problems defragmenting, please help
Hey guys, I'm trying to defragment my (CSmile drive since my comp has a been running a little slow lately, and I'm using the standard windows XP Disk Defragmenter from the system tools. The last time i defragmented was about a year ago, but then everything worked normally. But now that i try a message pops up saying
"Disk Defragmenter has detected that Chkdsk is scheduled to run on the volume: (CSmile. Please run Chkdsk /f"
I'm guessing that stands for CheckDisk? but from my inexperience i really don't know what to do in order to continue with the defragmentation of my computer, so anyone got any clues at all would be very much appreciated, thanks
It tells you what to do... you run chkdsk /f
This stems from the old MSDOS days. Back then, the filesystem (FAT or FAT16) limited us to 8 characters to a file name, plus 3 characters for an extention. So, the checkdisk utility became 'chkdsk.exe' and that is what we used.
Chkdsk is still used today on ocassion, as you can see. Windows XP wants you to run it with the /f switch. A switch is a ammendment to running a program. You put them in the command line to tell the program to run, but run in a certian way. The /f switch means FIX. It will scan the hard disk and fix any structural errors it finds. Note also that it will LOCK you out of the hard disk till it's done. It's a delacate operation, and the program doesn't want you interfering.
So, what I would do is turn off any power management settings you have (like turn off hard disks after X minutes, or turn off computer... you can leave the monitor setting) and then run the sucker. To run chkdisk.exe, go to Start, Run, and then type 'chkdsk /f' (no quotes) into the run box. Push enter and let it go.
Note that this will probably take a very, very long time. You... might want to leave it over night or while you go to work or something. I haven't seen this type of thing needed in a long time, and have never run it on a hard disk with so many gigs as they put in now. I suspect it will be quite the long haul.
Note: Since windows didn't tell you, don't try it right away... but you may have to run the command as 'chkdsk c: /f'... probably not, but it's something you should be aware of. Also, make sure there are no open files when you run it. Shut down as much as you can afford to. If you STILL have problems running it after all this... use this command instead.
chkntfs /c C:
That will schedual chkdsk to be run at the next startup, which should fix any open handle errors you may recieve.
thanks to Silverwmoon!
As far as I know, chkdsk /f shouldn't take a long time - the /f switch just makes sure that chkdsk automatically fix any file system errors. It depends on the size and speed of your hard disk, but typically takes less than 15 minutes. My 30GB hdd takes less than 15 minutes to check - I'm not sure how long it really takes, I haven't checked it for long. I think last time it ran for 5-7 minutes.
However, chkdsk /r WILL take a long time - this switch causes chkdsk to run over EVERY single sector of your hard disk to ensure there is no bad sector - physical damage done to parts of the hard disk that makes the sector unreadable.
And doesn't power management settings regarding the hard drive only turns the hdd off when the hdd is idle? I don't think it will turn the drive off when chkdsk is running, since chkdsk will make the drive busy - not idle.
Last edited by qualia; 08-12-2006 at 09:22 AM.
OK. I haven't done it in a long time, so I couldn't remember how long it took. Thanks for clearing that up.
Well, my HD isn't technically idle when I'm burning DVDs, or encoding something either, yet I've had more costers come out of power management shit than anything else. In theory, no... power management shouldn't be an issue. I don't trust it though... and it only takes a minute to turn everything off, and another minute to turn it back on when your done.
Originally Posted by qualia
thanks to Silverwmoon!
hum, okay. So there is some annoyance with power management stuff.. Haven't done any encoding for a while, but as far as I remember, it never troubles me. Ah well, yeah.. might as well turn power management off then..