How to run CHKDSK off flash drive ?

[compguy786]

Hello,

So my desktop is doing chkdsk right before boot every single time and in reality, needs a chkdsk r to complete it. I am trying to make a image of my desktop and i cant because there are errors on the disk. I tried hirens boot cd with mini xp, and it never mounts the C drive to chkdsk on.

Any ideas of how to go about ? Possibly safe mode may let me.

This is Windows 7 btw.

Thanks !

 

[TheELF]

You can create a rescue disk/usb
http://www.7tutorials.com/create-usb-memory-stick-system-recovery-tools
or just boot from a normal installation dvd to get to the recovery

 

[Smoblikat]

Dont use chkdsk to find hardware faults. Boot into windows, run a normal chkdsk to check the filesystem, then get HDTune lite and run the error scan on that. IMO better than a chkdsk /r

 

[Burpo]

https://www.raymond.cc/blog/manually-reset-or-clear-dirty-bit-in-windows-without-chkdsk/2/

 

[compguy786]

Well this is what happens....when i run it in windows

The type of the file system is NTFS.
Volume label is Seagate.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
582400 file records processed.
File verification completed.
373 large file records processed.
0 bad file records processed.
8 EA records processed.
23 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
62 percent complete. (577359 of 651140 index entries processed)
Index entry FD6F.tmp in index $I30 of file 1402 is incorrect.
63 percent complete. (591793 of 651140 index entries processed)
Index entry JumpListIcons in index $I30 of file 70667 is incorrect.
Index entry JUMPLI~2 in index $I30 of file 70667 is incorrect.
651140 index entries processed.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

 

[vailr]

chkdsk c: /f

 

[mfenn]

chkdsk c: /f

:thumbsup: It should say something along the lines of "cannot check the current system disk, would you like to schedule a check for the next reboot?" If you say yes, then it will run chkdsk in fix mode the next time you reboot.

 

[compguy786]

:thumbsup: It should say something along the lines of "cannot check the current system disk, would you like to schedule a check for the next reboot?" If you say yes, then it will run chkdsk in fix mode the next time you reboot.

Yes, and it runs every single time and is annoying !

HD Tune found no errors btw....but still !

 

[mfenn]

Yes, and it runs every single time and is annoying !

HD Tune found no errors btw....but still !

A block level program like HD Tune isn't going to able to do anything about filesystem issues. Are you saying that after scheduling a fix to run at next boot with chkdsk /f, it it still complains about being in read-only mode?

 

[compguy786]

A block level program like HD Tune isn't going to able to do anything about filesystem issues. Are you saying that after scheduling a fix to run at next boot with chkdsk /f, it it still complains about being in read-only mode?

That is correct !

 

[vailr]

@compguy:
Try this free Windows repair software:
Tweaking.com - Windows Repair 2.11.2
http://www.majorgeeks.com/files/details/tweaking_com_windows_repair.html

 

[mfenn]

That is correct !

Can you show the full output of chkdsk /f, both when you run it on the command line in Windows and after you reboot?

 

[inachu]

Dont use chkdsk to find hardware faults. Boot into windows, run a normal chkdsk to check the filesystem, then get HDTune lite and run the error scan on that. IMO better than a chkdsk /r

YOu are correct but files are locked for the files that are being used.
that is why booting from thumb drive is 99% better than doing it inside windows.

CHKDSK finds more errors outside of windows environment than within.

 

[Ketchup]

If chkdsk is finding additional bad sectors each you start the computer, you very well could be looking at a failing drive, in which case you don't want to make things worse with several runs of chkdsk. You need to put the drive in another computer or an enclosure and save as much data as you can.

After that, you can run a program like SeaTools for DOS, which is going to check the physical drive, not just the file system. It will let you know if things can be fixed.

 

[vailr]

YOu are correct but files are locked for the files that are being used.
that is why booting from thumb drive is 99% better than doing it inside windows.

CHKDSK finds more errors outside of windows environment than within.

chkdsk c: /f will allow running chkdsk in pre-Windows "pure DOS mode" which is in no way "less good" than booting to a DOS prompt from a USB thumb drive.

@compguy: There appears to be some kind of mis-communication going on.
Are you sure you didn't simply forget to include the /f parameter: [chkdsk c: /f ]?
Because: that's what your posted error output would seem to suggest.

 

[compguy786]

C:\Users\Saad>chkdsk c: /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by an
process. Would you like to schedule this volume to
checked the next time the system restarts? (Y/N) n

 

[compguy786]

chkdsk c: /f will allow running chkdsk in pre-Windows "pure DOS mode" which is in no way "less good" than booting to a DOS prompt from a USB thumb drive.

@compguy: There appears to be some kind of mis-communication going on.
Are you sure you didn't simply forget to include the /f parameter: [chkdsk c: /f ]?
Because: that's what your posted error output would seem to suggest.

I am trying to do it outside of windows, because exactly as stated above, its better to do it on a outside.

Ive backed all my data up, thats not the concern really, but a failing drive for sure !

 

[JackMDS]

Degraggler is portable and free.

No need to Defrag (if you do not want to) it can be use for Disk Checking only.

http://forum.piriform.com/?showtopic=19957

https://www.piriform.com/docs/defraggler/using-defraggler/checking-a-drive-for-errors

https://www.piriform.com/defraggler/download/standard

 

[vailr]

C:\Users\Saad>chkdsk c: /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by an
process. Would you like to schedule this volume to
checked the next time the system restarts? (Y/N) n

Try changing the "checked the next time the system restarts? (Y/N)" to: Y

 

[inachu]

Just for future reference when needing to make a bootable CD that you can use to scan your drive with using chkdsk:
https://www.google.com/search?q=win...7.3391j0j8&sourceid=chrome&es_sm=122&ie=UTF-8

 

[mfenn]

C:\Users\Saad>chkdsk c: /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by an
process. Would you like to schedule this volume to
checked the next time the system restarts? (Y/N) n

Well, your problem is that chkdsk asked you if you wanted it to do the check outside of Windows (well, during very early boot), and you said "no"!

Answer "y" (yes), and reboot. Your filesystem will then be checked and repaired, no extra work needed.

 

[mfenn]

Ive backed all my data up, thats not the concern really, but a failing drive for sure !

To be clear, filesystem errors do not necessarily mean that a drive is failing. They're much more commonly caused by unclean shutdowns or crashes. The fact that chkdsk, when run in read-only mode, didn't find any bad file records, but was only complaining about directory indexes pretty much confirms this.

 

[compguy786]

Well, your problem is that chkdsk asked you if you wanted it to do the check outside of Windows (well, during very early boot), and you said "no"!

Answer "y" (yes), and reboot. Your filesystem will then be checked and repaired, no extra work needed.

I have had it set as yes forever...it runs literally EVERY time and still fails the check. Thats why i dont understand whats up with it. I have it all backed up constantly as if this thing fails, ill have it all backed up.

 

[TheELF]

You could try and clean out your dirty bit... ... No it's nothing indecent,it's just how windows knows that something is wrong with the filesystem,clean it and it should stop trying to fix things.
https://technet.microsoft.com/en-us/library/cc788091.aspx

 

[mfenn]

I have had it set as yes forever...it runs literally EVERY time and still fails the check. Thats why i dont understand whats up with it. I have it all backed up constantly as if this thing fails, ill have it all backed up.

Can you provide the full output of chkdsk, both on the command line, and when it runs the check? It's really hard to troubleshoot when we can't see what you're seeing. Please answer "y" to the prompt that chkdsk gives you on the command line of course.

You could try and clean out your dirty bit... ... No it's nothing indecent,it's just how windows knows that something is wrong with the filesystem,clean it and it should stop trying to fix things.
https://technet.microsoft.com/en-us/library/cc788091.aspx

That would "work", but the filesystem is marked as dirty for a reason.