Chkdsk Unspecified Error Occurred Stage 2
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 06 Oct 2016 05:57:24 GMT by s_hv1000 (squid/3.5.20)
Posted on December 2, 2012 by Ray Woodcock I wanted to test a hard drive. I put it into an external USB enclosure and connected it to an ASUS
6e74667363686b2e
Eee PC. I booted the Eee using a multiboot USB jump drive. an unspecified error occurred 0x80070190 Upon booting, I chose the Windows 7 Recovery Disk and ran CHKDSK from the Command Prompt. I made many
An Unspecified Error Occurred 75736e6a726e6c2e 4f6
attempts to check and fix that external hard drive, using CHKDSK /R and CHKDSK /B. They all failed. Attempts using /I (e.g., CHKDSK /B /I) did not fail, but of course those http://answers.microsoft.com/en-us/windows/forum/all/chkdsk-throws-unspecified-error/a5e9f168-8885-4d89-ae0d-be7e236c2332 produced a warning that /I would not necessarily repair disk problems. When the attempts failed, they failed in stage 2 of 5, and most if not all produced this error message: An unspecified error occurred (696e647863686b2e e19). I hoped that, by running CHKDSK many times, perhaps the program would slowly eat its way through whatever corruption it might be encountering. At first it appeared https://raywoodcockslatest.wordpress.com/2012/12/02/unspecified-error-hkdsk/ that this might be taking place. But at some point I became convinced that we were not getting past the 25% mark, and in some cases the number of index entries processed was actually less than had been processed on the previous try. I ran a search on the "unspecified error" message. This produced a plethora of plausible possibilities. It tentatively appeared that there might be different causes of the unspecified error. Mine, for instance, might have been caused by something that would only produce the "e19" at the right end of the error message shown above. Some of the solutions suggested in those webpages, or coming to mind as I read, were that trying with a different machine might solve the problem; perhaps the (Samsung) hard drive manufacturer's diagnostic CD would help; maybe I could accomplish something with other DOS-like commands (e.g., FIXMBR); maybe some other program (e.g., TestDisk) would do a better job than CHKDSK; possibly I could boot into Windows 7 and use its disk checking feature to fix the problem (i.e., in Windows Explorer, right-click on the drive > Properties > Tools > Check No
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://superuser.com/questions/310998/chkdsk-stop-no-response-at-stage-2-verifying-indexes more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top CHKDSK stop (no response) at stage 2 (verifying indexes) up vote 5 unspecified error down vote favorite 1 I am using Windows 7. I was trying to synchronize the folder. Then the FreeFileSync freeze. I think there is some problem to my folder. Then I tried to copy the folder to another location. When calculating the size, the copying dialog freeze. So I suspect there is something wrong with the NTFS file system. So, I tried to use CHKDSK /F g: (my target drive) However, the CHKDSK is stopped at stage unspecified error occurred 2 (verifying indexes) for a long time. The stop I mean is no response. Then I tried CHKDSK /F /R /X /V g: Still the same. The following is the message: CHKDSK is verifying files (stage 1 of 5)... 168432 file records processed. File verification completed. 16 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 13 percent complete. (169112 of 181698 index entries processed) Please help. windows ntfs chkdsk share|improve this question asked Jul 15 '11 at 16:33 Allen 1142412 2 "A long time" is how long exactly? –user3463 Jul 15 '11 at 16:37 Stuck at the 13 percent around 1 hour. Previously I chkdsk, it goes through smoothly. –Allen Jul 15 '11 at 16:41 Go with the /i option suggested by @afrazier below. –user3463 Jul 15 '11 at 18:10 1 Only 1 hour! Try to wait more time (3h) to see if it changes... –kokbira Jul 15 '11 at 18:31 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote accepted If the drive is large and has lots of problems a disk check could take hours, if not days, to complete. A couple things to try before letting Chkdsk potentially destroy your data: SpinRite. The hard drive manufacturer's diagnostics utility. SpinR