Chkdsk Unspecified Error Occurred Verifying Indexes
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: windows 2008 r2 server - chkdsk loop - An unspecified error occurred (696e647863686b2e dee) Windows Server > Windows Server General
Chkdsk An Unspecified Error Occurred (766f6c756d652e63 461)
Forum Question 0 Sign in to vote Hi, One of our main windows 2008 r2 chkdsk an unspecified error occurred 696 file servers (HP Proliant ML350 G6) seems to have a dirty d: drive. After every reboot, chkdsk runs on drive "d:" chkdsk an unspecified error occurred (766f6c756d652e63 3f1) and stops with an unspecified error (696e647863686b2e dee) when checking indexes. After the error it continues to bootand start normallyinto windows. The d: drive looks ok, but when I run chkdsk in windows the chkdsk runs
An Unspecified Error Occurred During Chkdsk
andstops at the same point without warning or anything else. The guistops andexits, period. No message nothing. WhenI check the d: drive with "fsutil dirty query d:", the disk is marked as "dirty" .... The HPadvanced Proliantdiagnostic tools did not show any problems with the hardisks, I'm running latest HP drivers and firmwares on the server. Last but not least I don't have any special warnings/errors etc in the event viewer.
Chkdsk Verifying Indexes Stuck
Here is the output of chkdsk f.ex. in safe mode I did a few hours ago, the output/error is always identical: C:\>chkdsk d: /R /F /X The type of the file system is NTFS. Volume label is DATA. CHKDSK is verifying files (stage 1 of 5)... 184832 file records processed. File verification completed. 15624 large file records processed. 0 bad file records processed. 0 EA records processed. 5 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 10 percent complete. (182686 of 212928 index entries processed) An unspecified error occurred (696e647863686b2e dee). --------------------------- As of now, I have disabled the boot-time check on drive d: (with "chkntfs d: /x"), but I would prefer to restore it when the problem is fixed. I tried a lot of chkdsk and safe mode combinations, nothing helped. I don't have anyclues ... so your help is really welcome. Thanks a lot! KInd regards, Didier Edited by didierlux Friday, March 28, 2014 6:37 AM it is a Proliant G6 not G7 Thursday, March 27, 2014 8:17 PM Reply | Quote Answers 0 Sign in to vote Hi, There are multiple cause for the issue such as an improper shutdown sequence, or a more serious hardware problem that can indicate a fa
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 chkdsk verifying indexes slow Business Learn more about hiring developers or posting ads with us Super User Questions Tags
Check Disk Unspecified Error Occurred
Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it an unspecified error occurred (696e647863686b2e 60e) 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 An unspecified error occurred 6c6f6766696c652e 29c up https://social.technet.microsoft.com/Forums/en-US/f877ed5e-6f2e-4037-9b82-d7cc33b718f2/windows-2008-r2-server-chkdsk-loop-an-unspecified-error-occurred-696e647863686b2e-dee?forum=winservergen vote 1 down vote favorite UPDATE: It was a bad SATA cable. I ran the chkdsk /R command on an external WD 1TB hardrive connected via SATA. Here is the output log from chkdsk from event viewer. Not sure what the error message means? Chkdsk was executed in read/write mode. Checking file system on E: The type of the file system is NTFS. Volume label is Backup Drive. CHKDSK is verifying files (stage 1 of 5)... http://superuser.com/questions/871110/chkdsk-an-unspecified-error-occurred-6c6f6766696c652e-29c 768 file records processed. File verification completed. 0 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)... 884 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 768 file SDs/SIDs processed. Cleaning up 6 unused index entries from index $SII of file 0x9. Cleaning up 6 unused index entries from index $SDH of file 0x9. Cleaning up 6 unused security descriptors. Security descriptor verification completed. 58 data files processed. CHKDSK is verifying file data (stage 4 of 5)... 752 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 196108954 free clusters processed. Free space verification is complete. Read failure with status 0xc000009d at offset 0xb62f1000 for 0x10000 bytes. Read failure with status 0xc000009d at offset 0xb62f1000 for 0x1000 bytes. An unspecified error occurred (6c6f6766696c652e 29c). windows-7 hard-drive chkdsk share|improve this question edited Jan 30 '15 at 1:04 asked Jan 29 '15 at 13:52 steve 613 1 nice to hear that a new cable fixed it. Accept my answer to "close" the question. –magicandre1981 Jan 31 '15 at 15:24 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote 0xc000009d = STATUS_DEVICE_NOT_CONNECTED Looks like
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 http://superuser.com/questions/229079/chkdsk-an-unspecified-error-occurred-696e647863686b2e-e19 Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges http://www.theeldergeek.com/forum/index.php?showtopic=23696 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 “An unspecified error occurred (696e647863686b2e e19)” up vote 3 down unspecified error vote favorite System is Win7x64 Pro on Core i7-920, 12GB I'm experiencing some system flakiness and am trying to pin down the cause. SMART shows zero bad sectors, zero pending reallocations on all drives Memory tests show no problems. Chkdsk fails in various different ways: When run from a normal command line (no /f option) it gets to 63% and then hangs When run on boot (autocheck) it hangs immediately on starting. Actually, the countdown timer unspecified error occurred (Press any key to skip chkdsk) gets to 1 second and the system hangs. When run from the F8 "Repair System" option (the Win7 "recovery console"), with /f, it runs to about 63% (end of stage 2) and then fails as follows: Volume label is OS. CHKDSK is verifying files (stage 1 of 3)... 5068288 file records processed. File verification completed. 308 large file records processed. 0 bad file records processed. 2 EA records processed. 77 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 63 percent complete. (6078872 of 7562028 index entries processed) An unspecified error occurred (696e647863686b2e e19). Unable to obtain a handle to the event log. Googling and searching on Technet for the error code and "Unable to obtain a handle to the event log" both turn up nothing useful. Anybody have any info on what the problem is? windows-7 64-bit chkdsk share|improve this question edited Jan 4 '11 at 22:12 Bobby 7,42122639 asked Jan 4 '11 at 18:43 Ex Umbris 7451513 Was this drive originally partitioned with Windows 7 or with a previous OS? Is this a basic or dynamic disk? Have you tried deleting the partition and recreating under Win7? Or are you trying to avoid this? Do you have another machine you could move the disk to and try chkdsk anymore? –IrqJD Jan 4 '11 at 22:
Connection refused The remote host or network may be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 06 Oct 2016 05:58:58 GMT by s_hv977 (squid/3.5.20)