Symptom:

When using DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS parameter to repair a corrupt .MDF database, like this:

DBCC CHECKDB(xxxx, ‘REPAIR_ALLOW_DATA_LOSS’)

you see the following error message:

Msg 8921, Level 16, State 1, Line 8
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8998, Level 16, State 2, Line 8
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 39 pages from (1:0) to (1:8087). See other errors for cause.
CHECKDB found 1 allocation errors and 0 consistency errors not associated with any single object.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:157) is pointed to by the next pointer of IAM page (0:0) in object ID 3, index ID 1, partition ID 196608, alloc unit ID 196608 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘sys.sysrscols’ (object ID 3).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:131) is pointed to by the next pointer of IAM page (0:0) in object ID 5, index ID 1, partition ID 327680, alloc unit ID 327680 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘sys.sysrowsets’ (object ID 5).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:21) is pointed to by the next pointer of IAM page (0:0) in object ID 7, index ID 1, partition ID 458752, alloc unit ID 458752 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:18) is pointed to by the next pointer of IAM page (0:0) in object ID 7, index ID 2, partition ID 562949953880064, alloc unit ID 562949953880064 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysallocunits’ (object ID 7).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:12) is pointed to by the next pointer of IAM page (0:0) in object ID 8, index ID 0, partition ID 524288, alloc unit ID 524288 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘sys.sysfiles1’ (object ID 8).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:137) is pointed to by the next pointer of IAM page (0:0) in object ID 20, index ID 1, partition ID 281474978021376, alloc unit ID 281474978021376 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘sys.sysdbfiles’ (object ID 20).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:152) is pointed to by the next pointer of IAM page (0:0) in object ID 23, index ID 1, partition ID 281474978217984, alloc unit ID 281474978217984 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘sys.sysphfg’ (object ID 23).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:154) is pointed to by the next pointer of IAM page (0:0) in object ID 24, index ID 1, partition ID 281474978283520, alloc unit ID 281474978283520 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘sys.sysprufiles’ (object ID 24).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:92) is pointed to by the next pointer of IAM page (0:0) in object ID 27, index ID 1, partition ID 281474978480128, alloc unit ID 281474978480128 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:288) is pointed to by the next pointer of IAM page (0:0) in object ID 27, index ID 2, partition ID 562949955190784, alloc unit ID 562949955190784 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:96) is pointed to by the next pointer of IAM page (0:0) in object ID 27, index ID 3, partition ID 844424931901440, alloc unit ID 844424931901440 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 3 allocation errors and 0 consistency errors in table ‘sys.sysowners’ (object ID 27).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:102) is pointed to by the next pointer of IAM page (0:0) in object ID 29, index ID 1, partition ID 281474978611200, alloc unit ID 281474978611200 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘sys.sysprivs’ (object ID 29).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:117) is pointed to by the next pointer of IAM page (0:0) in object ID 34, index ID 1, partition ID 281474978938880, alloc unit ID 281474978938880 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:295) is pointed to by the next pointer of IAM page (0:0) in object ID 34, index ID 2, partition ID 562949955649536, alloc unit ID 562949955649536 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:368) is pointed to by the next pointer of IAM page (0:0) in object ID 34, index ID 3, partition ID 844424932360192, alloc unit ID 844424932360192 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:123) is pointed to by the next pointer of IAM page (0:0) in object ID 34, index ID 4, partition ID 1125899909070848, alloc unit ID 1125899909070848 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 4 allocation errors and 0 consistency errors in table ‘sys.sysschobjs’ (object ID 34).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:108) is pointed to by the next pointer of IAM page (0:0) in object ID 41, index ID 1, partition ID 281474979397632, alloc unit ID 281474979397632 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:245) is pointed to by the next pointer of IAM page (0:0) in object ID 41, index ID 2, partition ID 562949956108288, alloc unit ID 562949956108288 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.syscolpars’ (object ID 41).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:10) is pointed to by the next pointer of IAM page (0:0) in object ID 44, index ID 1, partition ID 281474979594240, alloc unit ID 281474979594240 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:286) is pointed to by the next pointer of IAM page (0:0) in object ID 44, index ID 2, partition ID 562949956304896, alloc unit ID 562949956304896 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysnsobjs’ (object ID 44).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:76) is pointed to by the next pointer of IAM page (0:0) in object ID 50, index ID 1, partition ID 281474979987456, alloc unit ID 281474979987456 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:292) is pointed to by the next pointer of IAM page (0:0) in object ID 50, index ID 2, partition ID 562949956698112, alloc unit ID 562949956698112 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:294) is pointed to by the next pointer of IAM page (0:0) in object ID 50, index ID 3, partition ID 844424933408768, alloc unit ID 844424933408768 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 3 allocation errors and 0 consistency errors in table ‘sys.sysscalartypes’ (object ID 50).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:125) is pointed to by the next pointer of IAM page (0:0) in object ID 54, index ID 1, partition ID 281474980249600, alloc unit ID 281474980249600 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:284) is pointed to by the next pointer of IAM page (0:0) in object ID 54, index ID 2, partition ID 562949956960256, alloc unit ID 562949956960256 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysidxstats’ (object ID 54).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:141) is pointed to by the next pointer of IAM page (0:0) in object ID 55, index ID 1, partition ID 281474980315136, alloc unit ID 281474980315136 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:55) is pointed to by the next pointer of IAM page (0:0) in object ID 55, index ID 2, partition ID 562949957025792, alloc unit ID 562949957025792 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysiscols’ (object ID 55).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:13) is pointed to by the next pointer of IAM page (0:0) in object ID 58, index ID 1, partition ID 281474980511744, alloc unit ID 72057594037993472 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:84) is pointed to by the next pointer of IAM page (0:0) in object ID 58, index ID 2, partition ID 562949957222400, alloc unit ID 72057594038059008 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysbinobjs’ (object ID 58).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:129) is pointed to by the next pointer of IAM page (0:0) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 281474980642816 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:45) is pointed to by the next pointer of IAM page (0:0) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysobjvalues’ (object ID 60).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:88) is pointed to by the next pointer of IAM page (0:0) in object ID 64, index ID 1, partition ID 281474980904960, alloc unit ID 281474980904960 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:243) is pointed to by the next pointer of IAM page (0:0) in object ID 64, index ID 2, partition ID 562949957615616, alloc unit ID 562949957615616 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysclsobjs’ (object ID 64).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:15) is pointed to by the next pointer of IAM page (0:0) in object ID 69, index ID 1, partition ID 281474981232640, alloc unit ID 72057594039697408 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:39) is pointed to by the next pointer of IAM page (0:0) in object ID 69, index ID 2, partition ID 562949957943296, alloc unit ID 72057594039762944 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:290) is pointed to by the next pointer of IAM page (0:0) in object ID 69, index ID 3, partition ID 844424934653952, alloc unit ID 72057594039828480 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 3 allocation errors and 0 consistency errors in table ‘sys.sysrts’ (object ID 69).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:98) is pointed to by the next pointer of IAM page (0:0) in object ID 74, index ID 1, partition ID 281474981560320, alloc unit ID 281474981560320 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:100) is pointed to by the next pointer of IAM page (0:0) in object ID 74, index ID 2, partition ID 562949958270976, alloc unit ID 562949958270976 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.syssingleobjrefs’ (object ID 74).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:104) is pointed to by the next pointer of IAM page (0:0) in object ID 75, index ID 1, partition ID 281474981625856, alloc unit ID 281474981625856 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:106) is pointed to by the next pointer of IAM page (0:0) in object ID 75, index ID 2, partition ID 562949958336512, alloc unit ID 562949958336512 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysmultiobjrefs’ (object ID 75).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:33) is pointed to by the next pointer of IAM page (0:0) in object ID 90, index ID 1, partition ID 281474982608896, alloc unit ID 72057594038583296 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:81) is pointed to by the next pointer of IAM page (0:0) in object ID 90, index ID 2, partition ID 562949959319552, alloc unit ID 72057594038648832 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysqnames’ (object ID 90).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:49) is pointed to by the next pointer of IAM page (0:0) in object ID 91, index ID 1, partition ID 281474982674432, alloc unit ID 72057594038779904 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:35) is pointed to by the next pointer of IAM page (0:0) in object ID 91, index ID 2, partition ID 562949959385088, alloc unit ID 72057594038845440 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysxmlcomponent’ (object ID 91).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:83) is pointed to by the next pointer of IAM page (0:0) in object ID 92, index ID 1, partition ID 281474982739968, alloc unit ID 72057594038976512 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table ‘sys.sysxmlfacet’ (object ID 92).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:130) is pointed to by the next pointer of IAM page (0:0) in object ID 93, index ID 1, partition ID 281474982805504, alloc unit ID 72057594039107584 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:22) is pointed to by the next pointer of IAM page (0:0) in object ID 93, index ID 2, partition ID 562949959516160, alloc unit ID 72057594039173120 (type In-row data), but it was not detected in the scan.
Could not repair this error.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysxmlplacement’ (object ID 93).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:114) is pointed to by the next pointer of IAM page (0:0) in object ID 97, index ID 1, partition ID 281474983067648, alloc unit ID 72057594038190080 (type In-row data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:134) is pointed to by the next pointer of IAM page (0:0) in object ID 97, index ID 2, partition ID 562949959778304, alloc unit ID 72057594038255616 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 2 allocation errors and 0 consistency errors in table ‘sys.sysbinsubobjs’ (object ID 97).
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Could not repair this error.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Could not repair this error.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Could not repair this error.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Could not repair this error.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Could not repair this error.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 99, index ID 0, partition ID 0, alloc unit ID 6488064 (type System allocation data), page (57311:268369920). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
CHECKDB found 5 allocation errors and 28 consistency errors in table ‘(Object ID 99)’ (object ID 99).
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:120) is pointed to by the next pointer of IAM page (0:0) in object ID 245575913, index ID 0, partition ID 72057594040549376, alloc unit ID 72057594045792256 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:118) is pointed to by the next pointer of IAM page (0:0) in object ID 245575913, index ID 0, partition ID 72057594040549376, alloc unit ID 72057594045857792 (type LOB data), but it was not detected in the scan.
Could not repair this error.
Msg 2575, Level 16, State 1, Line 8
The Index Allocation Map (IAM) page (1:126) is pointed to by the next pointer of IAM page (0:0) in object ID 245575913, index ID 2, partition ID 72057594040614912, alloc unit ID 72057594045923328 (type In-row data), but it was not detected in the scan.
Repairing this error requires other errors to be corrected first.
CHECKDB found 3 allocation errors and 0 consistency errors in table ‘TestTable’ (object ID 245575913).
CHECKDB found 58 allocation errors and 28 consistency errors in database ‘xxxx’.

where ‘xxxx’ is name of the corrupt MDF database being repaired.

This is an allocation error since there are problems with the IAM pages, corresponding to Msg 2575 error.

Screenshot of error message:

Precise Explanation:

The data in MDF file are stored as pages, each page is 8KB. The Index Allocation Map (IAM) page is used to allocate the pages in the MDF File, and they are linked as a list.

If DBCC CHECKDB command finds the linked list of the IAM pages are invalid and it cannot correct the problem, then it will report this error.

You can use our product DataNumen SQL Recovery to recover the data from the corrupt MDF file and solve this error.

Sample Files:

Sample corrupt MDF files that will cause the Msg 2575 error:

SQL Server version Corrupt MDF file MDF file fixed by DataNumen SQL Recovery
SQL Server 2014 Error2.mdf Error2_fixed.mdf

 

References:

1. https://docs.microsoft.com/en-us/sql/relational-databases/errors-events/mssqlserver-2575-database-engine-error?view=sql-server-ver15