I have a MSSQL 2000 system on a Windows 2000 server that backups of a
particular database fail.

Nonrecoverable I/O error occurred on file 'd:\data\database.mdf'

and I have enough space on the OUTPUT disk.

I run
DBCC CHECKTABLE on a big table on my database I get these errors

is there any relation?
Server: Msg 8966, Level 16, State 2, Line 1
Could not read and latch page (1:1739600) with latch type UP. 23(Data error
(cyclic redundancy check).) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1739601) with latch type UP. 23(Data error
(cyclic redundancy check).) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1739602) with latch type UP. 23(Data error
(cyclic redundancy check).) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1739603) with latch type UP. 23(Data error
(cyclic redundancy check).) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1739604) with latch type UP. 23(Data error
(cyclic redundancy check).) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1739605) with latch type UP. 23(Data error
(cyclic redundancy check).) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1739606) with latch type UP. 23(Data error
(cyclic redundancy check).) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1739607) with latch type UP. 23(Data error
(cyclic redundancy check).) failed.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1739600) allocated to object ID 295672101, index ID 29
was not seen.  Page may be invalid or have incorrect object ID information in
its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 295672101, index ID 29. Page (1:1739600) was not seen
in the scan although its parent (1:1490082) and previous (1:1698663) refer to
it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1739601) allocated to object ID 295672101, index ID 29
was not seen.  Page may be invalid or have incorrect object ID information in
its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 295672101, index ID 29. Index node page (1:1490082),
slot 15 refers to child page (1:1739601) and previous child (1:1739600), but
they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1739602) allocated to object ID 295672101, index ID 29
was not seen.  Page may be invalid or have incorrect object ID information in
its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 295672101, index ID 29. Index node page (1:1490082),
slot 16 refers to child page (1:1739602) and previous child (1:1739601), but
they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1739603) allocated to object ID 295672101, index ID 29
was not seen.  Page may be invalid or have incorrect object ID information in
its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 295672101, index ID 29. Index node page (1:1490082),
slot 17 refers to child page (1:1739603) and previous child (1:1739602), but
they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1739604) allocated to object ID 295672101, index ID 29
was not seen.  Page may be invalid or have incorrect object ID information in
its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 295672101, index ID 29. Index node page (1:1490082),
slot 18 refers to child page (1:1739604) and previous child (1:1739603), but
they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1739605) allocated to object ID 295672101, index ID 29
was not seen.  Page may be invalid or have incorrect object ID information in
its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 295672101, index ID 29. Index node page (1:1490082),
slot 19 refers to child page (1:1739605) and previous child (1:1739604), but
they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1739606) allocated to object ID 295672101, index ID 29
was not seen.  Page may be invalid or have incorrect object ID information in
its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 295672101, index ID 29. Index node page (1:1490082),
slot 20 refers to child page (1:1739606) and previous child (1:1739605), but
they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1739607) allocated to object ID 295672101, index ID 29
was not seen.  Page may be invalid or have incorrect object ID information in
its header.
CHECKTABLE found 0 allocation errors and 8 consistency errors not associated
with any single object.
DBCC results for 'CDR_tmp'.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 295672101, index ID 29. Index node page (1:1490082),
slot 21 refers to child page (1:1739607) and previous child (1:1739606), but
they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 295672101, index ID 29. Page (1:1743648) is missing a
reference from previous page (1:1739607). Possible chain linkage problem.
There are 5339984 rows in 147986 pages for object 'CDR_tmp'.
CHECKTABLE found 0 allocation errors and 17 consistency errors in table
'CDR_tmp' (object ID 295672101).
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKTABLE (ViaStarBilling.dbo.CDR_tmp ).