Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

chkdsk Bad Clusters File


  • Please log in to reply
3 replies to this topic

#1 mrshow

mrshow

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:16 PM

Posted 22 August 2009 - 08:20 PM

I am trying to run a chkdsk on an external hard drive that I have. The hard drive is connected via USB to the back of my machine. The Properties of the hard drive reveal that it has 200GB used space and 730GB free space. Despite the copious amount of free space available on the hard drive, chkdsk cannot write to the bad clusters file due to "insufficient disk space". Any ideas?

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\root>chkdsk f: /f
The type of the file system is NTFS.
Volume label is GreenDriveII.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Replacing bad clusters in logfile.
CHKDSK was unable to adjust the size of the log file.
Adding 13 bad clusters to the Bad Clusters File.
Insufficient disk space to fix the bad clusters file.
CHKDSK aborted.

C:\Documents and Settings\root>


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,116 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:16 PM

Posted 22 August 2009 - 08:29 PM

Run the chkdsk /r command, rather than just chkdsk.

Start/Run...type chkdsk /r (with space between k and /) and hit Enter. Type Y in response to onscreen query and hit Enter. Reboot the system...let the command execute before it boots into XP. It will boot into XP automatically when the chkdsk has been executed.

Louis

#3 mrshow

mrshow
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:16 PM

Posted 22 August 2009 - 09:36 PM

Well I used the "/f" argument (as you can see in my first post). The hard drive is external USB drive (not a local drive) so my system doesn't need to restart to lock out the NTFS drive.

Anyway, I used the "/R" argument as you'd suggested but it returned this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\root>chkdsk f: /R
The type of the file system is NTFS.
Volume label is GreenDriveII.

CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Windows replaced bad clusters in file 138
of name \mus\MUSIC_~1\IR4358~1.MP3.
The disk does not have enough space to replace bad clusters
detected in file 140 of name .

An unspecified error occurred.

C:\Documents and Settings\root>


#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,116 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:16 PM

Posted 23 August 2009 - 08:34 AM

Hmmm...not good.

FWIW: The /r argument includes the /f argument, is more comprehensive in that it attempts to recover files from bad sectors (where the /f argument does not attempt such).

See similar post at http://www.bleepingcomputer.com/forums/t/120127/chkdsk-reports-insufficient-space-and-unspecified-error-occurred/

I suggest skipping to the appropriate hard drive manufacturer's diagnostic (extended/long) test.

Don't give up on the drive yet, run the long test and let's see what comes up.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users