Wednesday, April 15, 2009

How Long Does a Chkdsk r Take?

So, as I sat in the office till all hours of the night, watching my Small Business Server 2003 stuck on the same stage 4 of 5 while running a check disk (chkdsk r), I began to wonder what I was in for.
I googled "How long does a checkdisk take?" and "How long does a chkdsk r take?" and found lots of people asking the question, though the answers were not detailed enough to give me an estimate.

First, a word of advice, even if it appears your server/pc is doing nothing, it is, so never never never power off or reboot the machine.

So, for me, the answer is, just under 4 hours for the chkdsk r.

Now, here is the part people never mention, their system specifications! As mentioned, my server is a Microsoft Windows Small Business Server 2003, running exchange. I have 2 (raid) 300GB SCSI drives in the machine (total capacity is only 300gb, just cloned hot-swap drives). I have two 3.06 ghz Xeon processors on the box with 3GB of ram.

Hopefully that answer helped someone out there late at night that has a similar machine and wants to know if they should order pizza and beer.

18 comments:

Drew said...

Fantastic news.

Not.

Still waiting on mine here. ~220GB in a RAID0 that I inherited from the revolving door of IT "professionals."

I think I'm into Hour 2 now.

Thoughts said...

I hope it finished for you!

ninjovee said...

I was searching google for an answer to this question and I'm honestly baffled. Most people say it just takes 2-3 hours...or 4-5 at the most. I already left chkdsk running for almost 10 hours and it's still not finished, let alone, is still stuck at 10% at the 4th stage.

I'm running Chkdsk r on a 1TB external hard drive (that only has 100GB of files in it) and my PC has 4GB RAM and Intel Core 2 Quad Q8400 processor. I would think that it would at the least run for a few hours but this is too long for comfort. I do see the light on the HDD blinking so that means chkdsk is doing something. What do you suggest?

Thoughts said...

Unfortunately External drives are limited by the speed of the USB bus. I would imagine it could easily takes 10 hours if the disk has problems. Anything beyond 12 hours, and I would personally give up.

ninjovee said...

Thanks for the comment. It's been running for three days since I started it and it's still displaying that it's at 10%. There's a message that says it fixed some bad clusters on file 40 so I guess that means it's really running. But I have 400+ files in there. I really do want to recover the HD since it's roughly just a week old from when I bought it. I'm not sure the PC store would replace this for this kind of problem.

I did see a post in a forum that says that chkdsk ran for 63 hours on a server with 4 million files... so I'll be patient and give it about a week. Hopefully it's done by then. Thanks again

Canadian Patriot said...

I am currently running CHKDSK /R on a 1 TB drive I suspect of having problems. I freshly formatted the drive, and ran CHKDSK /R to identify any bad sectors upfront before archiving files. I started the CHKDSK at around 2:00pm, and it is now 7:30pm and it is at stage 5, 30%. It is moving, but very slowly as it checks and verifies every free cluster on the drive. I estimate at the rate it is going it will take another 24 hours to complete...which is a small cost to verify whether the drive is botched or not.

LRod said...

I have a SBS 2003 on an intel xeon dual core 3ghz 2gbs ram.... I am running chkdsk on the 30GB c:\ partition of a drive I suspect is bad... been going on for 2hrs holding at stage 4 of 5. Mine doesnt have a percentage meter, I really detest having to do this on labor day.

MidSpeck said...

Even though it's an old post, it's still good solid information.

Thanks for also posting the size/setup of your disks as that's important too.

Three observations to provide a little more info for people:
1) Stages 4 and 5 only run if you do a chkdsk /r
2) Stage 4 checks the parts of your disk being used by files, stage 5 checks the part unused. So if you have a mostly empty hard drive, stage 4 will be quick and stage 5 will be long. If your hard drive is mostly full, it'll be opposite.
3) You usually get a percentage if you are checking while Windows is fully booted. If it is checking on startup (also called autochk) then you will get no percentages.

Freebies said...

Ok thanks for the info. Unfortunately I rebooted several times because my system froze. I hope I am not in deep shit because of it. I ran it again and I am still stuck at stage 4 so I guess it will take a while. The first time I did it I let it sit for two hours. Now I will not touch it.

Hippisak said...

How can i skip the test if I dont have the patience to let it run for three days?

Thoughts said...

You really should not skip the test. It might be damaging to do so.

Jorge Montano Parraga said...

I have a 256 GB HDD, leave it running for long hours and had no success, so I'm afraid I need to replace this, is there a way to save this drive to be thrown away, someone told me that through programs you can create a partition with bad sectors and use that disk without problems, does anyone knows which program can do that?

nuklear said...

I am working remotely and only 30minutes has gone by and was getting a little ansty but after seeing these posts it makes me a little more comfortable.

Running chkdsk /r on local C:\ Windows Server 2008 STD 64bit 12gb ram.

phaetoncz said...

hi ppl,

i have 1,5 Tb hdd and i was doing chkdsk during night. At morning i was on 3 percent (6 hours of work). At evening i got 10 percent. Estimated time of work about 5 days for me (stage of repairing bad sectors run really slow) but still worthy, because i got there photos nowhere else saved and so on.

Good luck with chckdsk, keep my long time in mind while checking yours hdds.

(Btw conected by eSata).

Thom Gordon said...

WHS v1 Chkdsk - Still Waiting at 4 days.

I am trying to remember when I started this! Wednesday, I think (it's Sat now). I have a Windows Home Server (HP Mediasmart) with 3 2TB drives and a 500 GB Drive. Space Used is 4.9 TB of 5.9 TB. Because WHS uses the Drive Extender, D: drive CHKDSK split into 3 extra chkdsk windows. Yesterday they all completed successfully but one. The last one is popping up a few file cluster errors and sitting at 36%. The bad news is that WHS Backups are inaccessible although most other files are OK. I am starting a WHS 2011 machine build so hopefully I can copy the files off before the drive craters! I think the failing 2TB Drive is almost 10 years old...

Good news - My Backups are not critical and all my photos and personal files are also backed up on other machines. I got hacked in 2002 (Kuwait!) and lost many key files so I am paranoid at the best of times.

May the Bytes be ever in your favor!

Alex said...

I'm running checkdisk at system startup (before Windows loads) on a 1.5 TB (2/3 full) 5400 RPM drive connected via SATA 2, on a C2D 6400 @ 2.98 GHz CPU.

It ran quickly until 10% through Step 4, and then it slowed down to a crawl after it found the first bad block. It stayed at 10% for hours, though the file count would increment every so often.

As of right now it's been running for 14 hours and still isn't done. :(

Alex said...

I have a 1.5 TB (1TB full) 5400 RPM drive on a SATA 2 connection, with a C2D 6400 @ 2.98GHZ CPU.

I started the scandisk at system bootup, figuring it would be faster without Windows loaded. My mistake.

Scandisk quickly got to Step 4, where it seemed to stop at 10% for hours. The file count kept incrementing, but the % stayed at 10%.

It's been running for 20 hours now, still not done. :(

ice_kenshin_of_bushido said...

It really depends on the damage on the drive. if there is alot of errors the process will take longer because it has to repair then check it to consistency, then scan that sector over again, and then it moves on... its a lengthy process for disks that may have more damage than one with maybe one or four bad sectors...