If I'm correct, you have one disk in, with one partition that you access, C: - please correct me if I'm wrong.
The last scan was ok
Windows has scanned the file system and found no problems.
No further action is required.
What problem do you see now?
I have two internal hard drives. My main system drive and a drive designated F, which I use to store documents, videos, etc. I've only been checking the system drive for errors (as F is not necessary for Windows to run - it's just a storage drive). When running scans through AOMEI, I only check the one C partition of my system drive. (I checked the other two partitions of the system drive with AOMEI once each, and it found no errors on them. It only finds errors on the C partition.)
The problem is that CHKDSK didn't find any issues on its own. It's only when I run AOMEI and use its "Check partition for errors by using chkdsk.exe" option that the errors present themselves. (And those are like a game of Whack-a-Mole - fixing some of them by going through the restart CHKDSK session that's automatically triggered by selecting to allow AOMEI to fix the errors just allows more to pop up, and AOMEI even once said that there's something wrong with my MFT, as you can see in one of the error messages in my previous post.)The last scan was ok
Windows has scanned the file system and found no problems.
No further action is required.
What problem do you see now?
In fact, I paused writing this message to run another scan with AOMEI, and got this result:
Attachment 138465
As you can see, AOMEI's CHKDSK scan found the errors that CHKDSK when run on its own missed. (the errors listed right after "Stage 2".
CHKDSK (when run straight from Windows, rather than through AOMEI) doesn't seem to find or fix any errors, and running both sfc /scannow and dism /Online /NoRestart /Cleanup-Image /CheckHealth didn't find any either. Only running a scan through AOMEI finds them.
And not only didn't CHKDSK find those index entry errors that AOMEI did, but a while back, when AOMEI had given me the error message "The master file table's (MFT) BITMAP attribute is incorrect. The Volume Bitmap is incorrect. Windows has checked the file system and found problems. Please run chkdsk /scan to find the problems and queue them for repair.", I ran chkdsk /scan through an elevated command prompt, and it likewise neither found nor corrected any issues.
One thing to note is that the last standalone (ie, non-AOMEI) CHKDSK session that I ran (which found no problems) was just the cursory type that can be run with Windows running. It wasn't a full one that requires a restart. But AOMEI had previously triggered two full restart CHKDSK sessions in attempts to fix the errors that it found. Neither one caused AOMEI to stop finding errors in subsequent scans (although exactly which errors were present changed every time). You can look at the AOMEI error reports in my previous post for more details regarding that.
EDIT: I found something interesting.
Here's a thread on another forum about someone who encountered an issue very similar to my current one (but while using a Glarysoft product instead of an AOMEI one):
https://www.wilderssecurity.com/thre...lities.384471/
In one of the replies in that thread, one user quoted the following from a linked page:
Now, when I run CHKDSK by itself (even in read-only mode) it finds no issues on my computer. But running it through AOMEI always finds some kind of problem.Chkdsk is prone to falsely reporting errors when in read-only mode, and it might report that a volume is corrupted even when no corruption is present. For example, Chkdsk might report corruption if NTFS modifies an area of the disk on behalf of a program at the same time Chkdsk is examining the same area. To verify a volume correctly, the volume must be in a static state, and the only way to guarantee that state is to lock the volume. Chkdsk locks the volume only when you specify the /f, /r, or /x parameters. Thus, you might need to run Chkdsk more than once for Chkdsk to complete all stages in read-only mode.
Could the particular way that AOMEI is using CHKDSK be causing false positives?
Last edited by hbenthow; 08 Jun 2017 at 00:36.
I'm afraid I can't comment on Aomei and chkdsk. You might want to ask the question in Aomei's forums or of Aomei support.
Have you run chkdsk on restart?
Yes and no. As I mentioned two posts ago, AOMEI's way of attempting to fix the errors that it finds is to trigger a restart CHKDSK session (if you select to let AOMEI fix the errors that it found, it immediately triggers the restart). It did this twice. CHKDSK itself seemed to complete perfectly each time, giving a message saying that it was 100% finished.
Each time, after the computer restarted and completed a CHKDSK session, I again logged into Windows, checked the C partition using AOMEI, and was again presented with messages claiming that it had found problems (always different errors, though).
However, I did not run a restart CHKDSK session manually using Command Prompt.
Last edited by hbenthow; 08 Jun 2017 at 18:52.
Update: I ran an extended Western Digital Data Lifeguard test (as my system drive is a Western Digital drive), and it too passed.
Attachment 138576
Also, I decided to try a small experiment. I opened up AOMEI and used it to check my C partition (just as before). I then saved the result (which unsurprisingly contained several error messages). Here's the result, with the errors highlighted in bold text:
I then opened and closed two Internet browsers (browsing the Internet for a few seconds in one before closing it), then ran another AOMEI disc check immediately afterward. This check was performed less than two minutes after the first check. Here are the results:Checking (C:), please wait a few seconds or minutes...-------------------------------------------------------------
Volume label is Windows.
Stage 1: Examining basic file system structure ...
414720 file records processed.
File verification completed.
11790 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
Index entry 03d1e1da-f580-45d7-afdd-3598ed7cdba4_withdraw.xml in index $I30 of file 170100 is incorrect.
Index entry 03D1E1~2.XML in index $I30 of file 170100 is incorrect.
Index entry eac38764-c24d-4954-8096-70b6c0a53e08_show.xml in index $I30 of file 170100 is incorrect.
Index entry eac38764-c24d-4954-8096-70b6c0a53e08_withdraw.xml in index $I30 of file 170100 is incorrect.
Index entry EAC387~1.XML in index $I30 of file 170100 is incorrect.
Index entry EAC387~2.XML in index $I30 of file 170100 is incorrect.
548140 index entries processed.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
Chkdsk has completed, but some errors were found in the partition.
You could use AOMEI Partition Assistant to fix it.
As you can see, AOMEI gave a drastically different list of errors in two separate scans run within mere minutes of each other, with only about a minute of browser use in between.Checking (C:), please wait a few seconds or minutes...-------------------------------------------------------------
Volume label is Windows.
Stage 1: Examining basic file system structure ...
414720 file records processed.
File verification completed.
11790 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
An index entry from index $O of file 25 is incorrect.
An index entry from index $O of file 25 is incorrect.
An index entry from index $O of file 25 is incorrect.
An index entry from index $O of file 25 is incorrect.
An index entry from index $O of file 25 is incorrect.
An index entry from index $O of file 25 is incorrect.
An index entry from index $O of file 25 is incorrect.
An index entry from index $O of file 25 is incorrect.
Missing object id index entry or duplicate object id detected
for file record segment 118856.
Missing object id index entry or duplicate object id detected
for file record segment 118858.
Missing object id index entry or duplicate object id detected
for file record segment 118865.
Missing object id index entry or duplicate object id detected
for file record segment 118869.
Missing object id index entry or duplicate object id detected
for file record segment 118889.
Missing object id index entry or duplicate object id detected
for file record segment 118894.
Missing object id index entry or duplicate object id detected
for file record segment 118895.
Missing object id index entry or duplicate object id detected
for file record segment 121311.
Index entry 1496964152 in index $I30 of file 95081 is incorrect.
Index entry 149696~1 in index $I30 of file 95081 is incorrect.
Error detected in index $I30 for file 109472.
Index entry 093b765d-d33c-40c6-bb61-39d9a8300f1b.up_meta in index $I30 of file 109472 is incorrect.
Index entry 093b765d-d33c-40c6-bb61-39d9a8300f1b.up_meta_body in index $I30 of file 109472 is incorrect.
Index entry 093B76~1.UP_ in index $I30 of file 109472 is incorrect.
Index entry 093B76~2.UP_ in index $I30 of file 109472 is incorrect.
Index entry 112bb30a-82e7-4493-8fd5-511661361c22.up_meta in index $I30 of file 109472 is incorrect.
Index entry 112bb30a-82e7-4493-8fd5-511661361c22.up_meta_body in index $I30 of file 109472 is incorrect.
Index entry 112BB3~1.UP_ in index $I30 of file 109472 is incorrect.
Index entry 112BB3~2.UP_ in index $I30 of file 109472 is incorrect.
Index entry 356d92a4-9645-4416-9e61-a64dbb9bc85c.up_meta in index $I30 of file 109472 is incorrect.
Index entry 356d92a4-9645-4416-9e61-a64dbb9bc85c.up_meta_body in index $I30 of file 109472 is incorrect.
Index entry 356D92~1.UP_ in index $I30 of file 109472 is incorrect.
Index entry 356D92~2.UP_ in index $I30 of file 109472 is incorrect.
Index entry 5d56c867-0039-4455-84be-b905cfb23b98.up_meta in index $I30 of file 109472 is incorrect.
Index entry 5d56c867-0039-4455-84be-b905cfb23b98.up_meta_body in index $I30 of file 109472 is incorrect.
Index entry 5D56C8~1.UP_ in index $I30 of file 109472 is incorrect.
Index entry 5D56C8~2.UP_ in index $I30 of file 109472 is incorrect.
Index entry 701762f0-9a08-4405-a4a0-ecbcc6f16a33.up_meta in index $I30 of file 109472 is incorrect.
Index entry 701762f0-9a08-4405-a4a0-ecbcc6f16a33.up_meta_body in index $I30 of file 109472 is incorrect.
Index entry 701762~1.UP_ in index $I30 of file 109472 is incorrect.
Index entry 701762~2.UP_ in index $I30 of file 109472 is incorrect.
Index entry 9dcb2f15-3845-4087-adf4-3aaa8fa3e86a.up_meta in index $I30 of file 109472 is incorrect.
Index entry 9dcb2f15-3845-4087-adf4-3aaa8fa3e86a.up_meta_body in index $I30 of file 109472 is incorrect.
Index entry 9DCB2F~1.UP_ in index $I30 of file 109472 is incorrect.
Index entry 9DCB2F~2.UP_ in index $I30 of file 109472 is incorrect.
Index entry a51d90a2-9284-4fb9-9e4c-9f57683da112.up_meta in index $I30 of file 109472 is incorrect.
Index entry a51d90a2-9284-4fb9-9e4c-9f57683da112.up_meta_body in index $I30 of file 109472 is incorrect.
Index entry A51D90~1.UP_ in index $I30 of file 109472 is incorrect.
Index entry A51D90~2.UP_ in index $I30 of file 109472 is incorrect.
Index entry e4e0c6ed-32c8-4a06-a13d-2673707a0f97.up_meta in index $I30 of file 109472 is incorrect.
Index entry e4e0c6ed-32c8-4a06-a13d-2673707a0f97.up_meta_body in index $I30 of file 109472 is incorrect.
Index entry E4E0C6~1.UP_ in index $I30 of file 109472 is incorrect.
Index entry E4E0C6~2.UP_ in index $I30 of file 109472 is incorrect.
Index entry 1496964147 in index $I30 of file 124497 is incorrect.
Index entry 149696~1 in index $I30 of file 124497 is incorrect.
Index entry 1496964152 in index $I30 of file 203996 is incorrect.
Index entry 149696~1 in index $I30 of file 203996 is incorrect.
548134 index entries processed.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
Chkdsk has completed, but some errors were found in the partition.
You could use AOMEI Partition Assistant to fix it.
I then opened up my main browser (the one that I'm using now), and (with this browser window still open) opened up AOMEI and ran a third scan, with these results:
This time, the errors are very different from those reported by the second scan, but have some entries that are identical to some of those from the first scan. What do you make of all this?Checking (C:) , please wait a few seconds or minutes...-------------------------------------------------------------
Volume label is Windows.
Stage 1: Examining basic file system structure ...
414720 file records processed.
File verification completed.
11790 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
Index entry Local State in index $I30 of file 126169 is incorrect.
Index entry LOCALS~2 in index $I30 of file 126169 is incorrect.
Index entry ssdfp5488.0.2004048940 in index $I30 of file 126169 is incorrect.
Index entry SSDFP5~1.200 in index $I30 of file 126169 is incorrect.
Index entry 03d1e1da-f580-45d7-afdd-3598ed7cdba4_withdraw.xml in index $I30 of file 170100 is incorrect.
Index entry 03D1E1~2.XML in index $I30 of file 170100 is incorrect.
Index entry eac38764-c24d-4954-8096-70b6c0a53e08_withdraw.xml in index $I30 of file 170100 is incorrect.
Index entry EAC387~2.XML in index $I30 of file 170100 is incorrect.
Index entry the-real-index in index $I30 of file 241580 is incorrect.
Index entry THE-RE~1 in index $I30 of file 241580 is incorrect.
548088 index entries processed.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
Chkdsk has completed, but some errors were found in the partition.
You could use AOMEI Partition Assistant to fix it.
Also, should I run a restart CHKDSK session manually using Command Prompt, then find the log file and post its results here?
If so, do you know the exact best string of letters to enter when running CHKDSK? I usually run chkdsk C: /f /r /x, but I think I saw a claim somewhere that it's not necessary to enter all three letters (f, r, and x) at once.
Are there any other ways to ascertain whether or not AOMEI's results are false positives? I've already posted at the AOMEI forum, but have yet to receive a response.
EDIT: I decided to look the the Windows Event Viewer to see if I could find the logs from the two times that AOMEI triggered a restart CHKDSK session in order to repair errors (as a result of me selecting the option to let AOMEI attempt to fix the errors it had found). Sure enough, I was able to find them. Here's the first one (with a certain part highlighted in bold text for emphasis):
And here's the second:Log Name: ApplicationSource: Microsoft-Windows-Wininit
Date: 6/7/2017 2:36:14 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: WINDOWS-SJ9IF72
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure ...
414720 file records processed.
File verification completed.
11759 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
551140 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 3222 unused index entries from index $SII of file 0x9.
Cleaning up 3222 unused index entries from index $SDH of file 0x9.
Cleaning up 3222 unused security descriptors.
Security descriptor verification completed.
68211 data files processed.
CHKDSK is verifying Usn Journal...
53683240 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
976146431 KB total disk space.
50080888 KB in 312140 files.
233412 KB in 68212 indexes.
0 KB in bad sectors.
567075 KB in use by the system.
65536 KB occupied by the log file.
925265056 KB available on disk.
4096 bytes in each allocation unit.
244036607 total allocation units on disk.
231316264 allocation units available on disk.
Internal Info:
00 54 06 00 9f cd 05 00 09 a7 0b 00 00 00 00 00 .T..............
25 02 00 00 92 00 00 00 00 00 00 00 00 00 00 00 %...............
Windows has finished checking your disk.
Please wait while your computer restarts.
Log Name: ApplicationSource: Microsoft-Windows-Wininit
Date: 6/7/2017 2:42:11 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: WINDOWS-SJ9IF72
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure ...
414720 file records processed.
File verification completed.
11758 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
551148 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
Security descriptor verification completed.
68215 data files processed.
CHKDSK is verifying Usn Journal...
53965232 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
976146431 KB total disk space.
50080608 KB in 312156 files.
233420 KB in 68216 indexes.
0 KB in bad sectors.
567651 KB in use by the system.
65536 KB occupied by the log file.
925264752 KB available on disk.
4096 bytes in each allocation unit.
244036607 total allocation units on disk.
231316188 allocation units available on disk.
Internal Info:
00 54 06 00 b3 cd 05 00 25 a7 0b 00 00 00 00 00 .T......%.......
25 02 00 00 92 00 00 00 00 00 00 00 00 00 00 00 %...............
Windows has finished checking your disk.
Please wait while your computer restarts.
Is this information of any use? I noticed some of the data stated, "Cleaning up [insert number here] unused index entries from index [insert index name here] of file [insert filename here]". Might these entries have anything to do with the errors that AOMEI gives?
Last edited by hbenthow; 08 Jun 2017 at 19:28.
Best wait for Aomei's comment. There may be some technical detail related to partition management it's sensitive to. I can't comment further, sorry.
Quote