| 600 | Microsoft Corporation |
Microsoft Corporation |
| 602 | Scans fault-tolerant volumes for latent corruptions |
Scans fault-tolerant volumes for latent corruptions |
| 603 | Scans fault-tolerant volumes for fast crash recovery |
Scans fault-tolerant volumes for fast crash recovery |
| 0x30000000 | Info |
Info |
| 0x30000001 | Start |
Start |
| 0x30000002 | Stop |
Stop |
| 0x50000002 | Error |
Error |
| 0x50000003 | Warning |
Warning |
| 0x50000004 | Information |
Information |
| 0xB0000001 | Started checking data integrity. |
Started checking data integrity. |
| 0xB0000004 | Completed data integrity checks. |
Completed data integrity checks. |
| 0xB000000B | Disk scan started on \\\\?\\PhysicalDrive%1 (\\\\?\\Disk%2) |
Disk scan started on \\\\?\\PhysicalDrive%1 (\\\\?\\Disk%2) |
| 0xB000000C | Disk scan completed on \\\\?\\PhysicalDrive%1 (\\\\?\\Disk%2) |
Disk scan completed on \\\\?\\PhysicalDrive%1 (\\\\?\\Disk%2) |
| 0xB0000015 | Volume scan started on %4 (%2) in \\\\?\\PhysicalDrive%5 (\\\\?\\Disk%6) |
Volume scan started on %4 (%2) in \\\\?\\PhysicalDrive%5 (\\\\?\\Disk%6) |
| 0xB0000016 | Volume scan completed on %4 (%2)%nBytes repaired: %11%nBytes not repaired: %12%nHResult: %5 |
Volume scan completed on %4 (%2)%nBytes repaired: %11%nBytes not repaired: %12%nHResult: %5 |
| 0xB0000017 | Volume scan was partially completed on %4 (%2)%nBytes repaired: %11%nBytes not repaired: %12%nHResult: %5 |
Volume scan was partially completed on %4 (%2)%nBytes repaired: %11%nBytes not repaired: %12%nHResult: %5 |
| 0xB0000018 | Files were skipped during the volume scan.%nFiles skipped: %6%nVolume name: %4 (%2)%nFirst skipped file name: %8%nHResult: %5 |
Files were skipped during the volume scan.%nFiles skipped: %6%nVolume name: %4 (%2)%nFirst skipped file name: %8%nHResult: %5 |
| 0xB0000036 | File data inconsistency was detected and was repaired successfully.%nFile name: %2%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
File data inconsistency was detected and was repaired successfully.%nFile name: %2%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
| 0xB0000037 | File data scrub operation failed.%nFile name: %2%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nBytes not repaired: %7%nStatus: %8 |
File data scrub operation failed.%nFile name: %2%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nBytes not repaired: %7%nStatus: %8 |
| 0xB0000038 | Volume metadata inconsistency was detected and was repaired successfully.%nVolume name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
Volume metadata inconsistency was detected and was repaired successfully.%nVolume name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
| 0xB0000039 | Volume metadata scrub operation failed.%nVolume name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nBytes not repaired: %7%nStatus: %8 |
Volume metadata scrub operation failed.%nVolume name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nBytes not repaired: %7%nStatus: %8 |
| 0xB000003A | File metadata inconsistency was detected and was repaired successfully.%nFile name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
File metadata inconsistency was detected and was repaired successfully.%nFile name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
| 0xB000003B | File metadata scrub operation failed.%nFile name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nBytes not repaired: %7%nStatus: %8 |
File metadata scrub operation failed.%nFile name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nBytes not repaired: %7%nStatus: %8 |
| 0xB000003C | File data inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.%nFile name: %2%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
File data inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.%nFile name: %2%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
| 0xB000003D | Volume metadata inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.%nVolume name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
Volume metadata inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.%nVolume name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
| 0xB000003E | File metadata inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.%nFile name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
File metadata inconsistency was detected and the parity repair was scheduled at the end of the task. No user action is required.%nFile name: %2%nMetadata reference: %3%nRange offset: %4%nRange length (in bytes): %5%nBytes repaired: %6%nStatus: %8 |
| 0xB0000065 | Started checking data integrity for crash recovery. |
Started checking data integrity for crash recovery. |
| 0xB0000068 | Completed data integrity checks for crash recovery. |
Completed data integrity checks for crash recovery. |
| 0xB000006F | Crash recovery disk scan started on \\\\?\\PhysicalDrive%1 (\\\\?\\Disk%2) |
Crash recovery disk scan started on \\\\?\\PhysicalDrive%1 (\\\\?\\Disk%2) |
| 0xB0000070 | Crash recovery disk scan completed on \\\\?\\PhysicalDrive%1 (\\\\?\\Disk%2) |
Crash recovery disk scan completed on \\\\?\\PhysicalDrive%1 (\\\\?\\Disk%2) |
| 0xB0000079 | Crash recovery volume scan started on %4 (%2) in \\\\?\\PhysicalDrive%5 (\\\\?\\Disk%9) |
Crash recovery volume scan started on %4 (%2) in \\\\?\\PhysicalDrive%5 (\\\\?\\Disk%9) |
| 0xB000007A | Crash recovery volume scan completed on %4 (%2)%nBytes repaired: %11%nBytes not repaired: %12%nHResult: %5 |
Crash recovery volume scan completed on %4 (%2)%nBytes repaired: %11%nBytes not repaired: %12%nHResult: %5 |
| 0xB00000A0 | Parity repair completed.%nVolume name: %4 (%2)%nExtent count: %5%nLength (in bytes): %6 |
Parity repair completed.%nVolume name: %4 (%2)%nExtent count: %5%nLength (in bytes): %6 |
| 0xB00000A1 | Parity repair failed.%nVolume name: %4 (%2)%nExtent count: %5%nLength (in bytes): %6%nHResult: %7 |
Parity repair failed.%nVolume name: %4 (%2)%nExtent count: %5%nLength (in bytes): %6%nHResult: %7 |