For the last 7 months, I've been getting the following error in
/var/log/messages every night during the cron.daily execution. I've finally
tracked it down to happening during my tripwire run, and I suspect
(based on linear time into the run, and sizes of files) the problem file
lies somwhere in /usr/lib.
The error message has been identical for months, so I assume I have a bad
spot that is not spreading. I'd like to find the affected file, rename it
and ignore the problem for a while longer.
If I know the sector and lbasector, can I determine the inode and/or
the actual file affected?
The error message is:
Jan 23 04:24:34 helium kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 23 04:24:34 helium kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=4200315, sector=4200248
Jan 23 04:24:34 helium kernel: end_request: I/O error, dev 16:01 (hdc), sector 4200248
as I said before, the sector number has never changed in months.
thanks,
-chuck
--
ACCEL Services, Inc.| Specialists in Gravity, Magnetics | 1(713)993-0671 ph.
1980 Post Oak Blvd. | and Integrated Interpretation | 1(713)960-1157 fax
Suite 2050 | |
Houston, TX, 77056 | Chuck Campbell | campbell@neosoft.com
| President & Senior Geoscientist |
"Integration means more than having all the maps at the same scale!"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jan 23 2002 - 21:01:05 EST