Chkdsk cannot run because the volume is in use by another process

Anonymous
2014-12-25T22:56:33+00:00

Hi,

Whenever I turn on my computer or even restarted it, and then tried to run the command 'chkdsk /r /f', I faced the error 'cannot lock current drive', although there are no other process hare running.

I had to schedule it to be running in the next restart.

When I scheduled it to be running in the next system restart , it was running well when it was restarted.

Threads merged.

Duplicate deleted.

Moved from Windows 7 Email and Communications Forum.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2014-12-31T16:14:25+00:00

I personally don't think you'd gain anything from a scan with UBCD.  We can learn all about the HDD's health by looking at its SMART data.  It may pass a diagnostic test with flying colors, and still have corrupted numerous files (in the past) and/or have many (remapped) bad sectors.

    Looking at your HDD's SMART status, I can see that it had 104 (hex 68) bad sectors which have since been reallocated (see Reallocated Sectors Count).  Since Current Pending Sector Count is 0, all suspected bad sectors have been successfully remapped, probably thanks to an earlier chkdsk /r scan.

    Everything else looks good.  I would suggest keeping an eye on the HDD every once in a while to make sure that it isn't developing more bad sectors (Current Pending Sector Count or Read Error Rate increasing from 0 in the far-right column).

    In case you didn't know this, HDDs are quite sensitive to being jostled while in operation.  Setting a laptop down too hard while it's on are is one the easiest ways to kill a laptop's HDD.  If you need a laptop that can be thrown around, it would be a good idea to upgrade to a SSD, since they have no moving parts.  This will also greatly speed up the laptop since the HDD is the biggest bottleneck in practically all laptops made nowadays.

Was this answer helpful?

1 person found this answer helpful.
0 comments

60 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-12-29T03:31:59+00:00

    The message  'cannot lock current drive' is not an error as such.  That will always be the case when you try to run the disk check on the system drive.

     re. "why ''chkdsk /r /f' ran"  - If you don't specify a drive letter chkdsk will use the current default drive as the target.   In your case, with the command prompt open on the c drive that is equivalent to typing chkdsk C:   /f  /r

    Although many people harmlessly use /f and /r together, it is redundant.  /r runs the same disk checks as /f and then ADDITIONALLY runs a check for bad sectors.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-12-29T03:01:20+00:00

    http://www.w7forums.com/threads/how-to-use-chkdsk-check-disk.448/

    **Command Prompt Method:**Alternatively, you can use the command prompt to perform a scan on a drive letter of your choice by running "chkdsk x:" where x is your drive letter. The manual scan options are:

    • /F Fixes errors on the disk.
    • /V On FAT/FAT32: Displays the full path and name of every file on the disk. On NTFS: Displays cleanup messages if any.
    • /R Locates bad sectors and recovers readable information (implies /F).
    • /L:size NTFS only: Changes the log file size to the specified number of kilobytes. If size is not specified, displays current size.
    • /X Forces the volume to dismount first if necessary. All opened handles to the volume would then be invalid (implies /F).
    • /I NTFS only: Performs a less vigorous check of index entries.
    • /C NTFS only: Skips checking of cycles within the folder structure.
    • /B NTFS only: Re-evaluates bad clusters on the volume (implies /R) "CHKDSK x: /F /R" would perform a full scan (including bad sectors) and attempt to fix them.
    • "How to Read the Event Viewer Log for Check Disk (chkdsk) in Vista, Windows 7, and Windows 8"
    • http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
    • Cheers.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-12-29T02:37:47+00:00

    Could anyone please take some of his precious time out to reply to me?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-12-26T01:47:05+00:00

    Youre cmd is wrong... To run CHKDSK, on a HD,it would be:

     CHKDSK C: /F  or /R  C: being the drive letter,youre letter r would be a

    disk

    Thanks a lot all of you.

    Yes, but I still insist on saying why ''chkdsk /r /f' run well when I have chosen 'Yes' as an answer on the question 'Would you like to schedule this volume to be checked in the next time system restarts?'   If the command 'chkdsk /r /f' were incorrect, then it would not have been working in the next time system restarted.

    • Could you please let me know why 'chkdsk /r /f' worked in the the next time system restarted??
    • The same error message showed me when runing your commands(screen shot below)

    • Moreover, could you please let me know if these commands have the same functionality. If no, then I can run these commands separately, if so, what benefit is of each one? If each one has another function, then if I want to save the time by letting the system automatically run them all together sequentially, how to let system do this:

    CHKDSK C: /F

    CHKDSK C: /R

    Was this answer helpful?

    0 comments