chkdsk /r on a 2TB drive = really long time

[zephxiii]

I started chkdsk /r on this drive maybe....Tuesday morning and as I post this it is at 57%!! It's still going though, just really really slowly. Does it normally take this long? I think it is averaging 6% every 24 hours.

Is there any safe way to stop it? I suppose I could close the command line window etc.

 

[C1]

Are you sure that you dont have the surface scan option checked/enabled? Also are you formatted NTFS or FAT32 (yes, FAT32 supports 2TB drives)?

Normally a straight disk check shouldnt take much more than a minute or two. If you are including a surface scan, then that would take hours.

Try running Chkdsk from a command line. Here are some switchs for available options: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx?mfr=true

Addendum
BTW, I always run a straight Chkdsk first to see if any issues are found before deciding to fix anything. Shotgunning over the disk with the /f switch allows, I believe, Chkdsk to fix files, but that ends up authorizing Chkdsk to modify files deemed damaged. In the process a bunch of temp file types are created (file fragments from the repairs), and original files deemed damaged may be changed are even disappear altogether.

 

[zephxiii]

It is running in command line and i ran with /r option to look for bad sectors etc. I knew it would take many hours....not as many days as it has been taking though! It didn't seem like the other 2TB I scanned took this long (different model though), but it found lil over 700GB of bad sectors (not sure if it cut the scan short because of this).

 

[razel]

That is far too long. Even with USB 2.0 at 33MB per second it shouldn't take more than 19 hours. It is ok to stop it since chkdsk is primarily just reading. It is when it encounters a bad sector and preps your file system to mark it as bad is when you don't want to close it.

If you can stop it while it is reading you are ok. Closing the command line doesn't always close it. You can guarantee it's closed by bringing up Task Manager. Look for 'chkdsk' and end it's process. Also ensure that no disk utilities are running then bury into your 'Services' and check that 'virtual disk' is not started.

Once you have this clean slate, I would check the drive manufacturer to see if they have any HDD diagnosis. If it's an external drive, it will run much faster and diagnosis will be more reliable if you can figure out how to plug it in natively via SATA. Have fun.

 

[Cerb]

That is far too long.

+1. Even a drive that big that performs the check slowly should finish within ~8 hours. Just kill it, use vendor diags, and then start over.

 

[zephxiii]

Yea, this is an internal SATA storage tank drive on my 2003 server machine. I suppose I could pull it out and run the manufacturer scan.