CHECKTABLE found 0 allocation errors and 4 consistency errors in table 'tbl_Command' (object ID 229575856).

Hello,

I've detected this database consistency problem in integrity check. This error was appeared since may of 2012 therefore the backup was overwritten. Can you help me about the solution about this issue? 

Errors:

Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 229575856, index ID 1, partition ID 72057594301382656, alloc unit ID 72057594324254720 (type In-row data). Page (1:57813) is missing a reference from previous page (1:194776). Possible chain linkage problem.
Msg 8928, Level 16, State 1, Line 1
Object ID 229575856, index ID 1, partition ID 72057594301382656, alloc unit ID 72057594324254720 (type In-row data): Page (1:194776) could not be processed.  See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 229575856, index ID 1, partition ID 72057594301382656, alloc unit ID 72057594324254720 (type In-row data), page (1:194776). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 96602121 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 229575856, index ID 1, partition ID 72057594301382656, alloc unit ID 72057594324254720 (type In-row data). Page (1:194776) was not seen in the scan although its parent (1:35639) and previous (1:120711) refer to it. Check any previous errors.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'tbl_Command' (object ID 229575856).
CHECKDB found 0 allocation errors and 4 consistency errors in database 'Tfs_DefaultCollection'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Tfs_DefaultCollection).

Thank you and best regards,

XaviN