Results of the dbcc checkdb:
for one database:
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:16648) with latch type SH. 1117(The request could not be performed because of an I/O device error.) failed.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:16648) allocated to object ID 1061578820, index ID 2, partition ID 72057594065387520, alloc unit ID 72057594066763776 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1061578820, index ID 2, partition ID 72057594065387520, alloc unit ID 72057594066763776 (type In-row data). Page (1:16648) was not seen in the scan although its parent (1:50739) and previous (1:16647) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1061578820, index ID 2, partition ID 72057594065387520, alloc unit ID 72057594066763776 (type In-row data). Page (1:16649) is missing a reference from previous page (1:16648). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'WAClickAggregationByDate' (object ID 1061578820).
CHECKDB found 0 allocation errors and 4 consistency errors in database 'WebAnalyticsServiceApplication_ReportingDB_81a47478-1052-4bb2-a2b9-b1d481880451'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (WebAnalyticsServiceApplication_ReportingDB_81a47478-1052-4bb2-a2b9-b1d481880451).
for the second db:
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:41200) with latch type SH. 1117(The request could not be performed because of an I/O device error.) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:390378) with latch type SH. 1117(The request could not be performed because of an I/O device error.) failed.
CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:41200) allocated to object ID 1099150961, index ID 1, partition ID 72057594052608000, alloc unit ID 72057594055753728 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1099150961, index ID 1, partition ID 72057594052608000, alloc unit ID 72057594055753728 (type In-row data). Page (1:41200) was not seen in the scan although its parent (1:477330) and previous (1:39815) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1099150961, index ID 1, partition ID 72057594052608000, alloc unit ID 72057594055753728 (type In-row data). Page (1:41201) is missing a reference from previous page (1:41200). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'FeatureUsage_Partition8' (object ID 1099150961).
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:390378) allocated to object ID 1342627826, index ID 1, partition ID 72057594048806912, alloc unit ID 72057594300465152 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1342627826, index ID 1, partition ID 72057594048806912, alloc unit ID 72057594300465152 (type In-row data). Page (1:390378) was not seen in the scan although its parent (1:390816) and previous (1:390377) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1342627826, index ID 1, partition ID 72057594048806912, alloc unit ID 72057594300465152 (type In-row data). Page (1:390379) is missing a reference from previous page (1:390378). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'RequestUsage_Partition11' (object ID 1342627826).
CHECKDB found 0 allocation errors and 8 consistency errors in database 'WSS_Logging'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (WSS_Logging).
Again thanks for help with this.