Recently we got the following nasty messages in our syslog files.
Everything is back to normal now, but these messages have us a bit
worried. Is this a general hard disk problem? Or is squid doing something
strange here?
Aug 18 06:40:00 proxy1 /USR/SBIN/CRON[737]: (root) CMD (updatedb)
Aug 18 06:40:00 proxy1 /USR/SBIN/CRON[738]: (root) CMD (/usr/sbin/atrun)
Aug 18 06:40:57 proxy1 kernel: hdb: dma_intr: status=0x51 {DriveReady
SeekComplete Error}
Aug 18 06:40:57 proxy1 kernel: hdb: dma_intr: error=0x40 {UncorrectableError},
LBAsect=954482, sector=954418
Aug 18 06:40:57 proxy1 kernel: end_request: I/O error, dev 03:41, sector
954418
Aug 18 06:40:57 proxy1 kernel: EXT2-fs error (device 09:00):
ext2_read_inode: unable to read inode block - inode=477226,
block=1908837 Aug 18 06:41:01 proxy1 kernel: hdb: dma_intr: status=0x51
{DriveReadySeekComplete Error}
Aug 18 06:41:01 proxy1 kernel: hdb: dma_intr: error=0x40 {UncorrectableError},
LBAsect=954482, sector=954418
Aug 18 06:41:01 proxy1 kernel: end_request: I/O error, dev 03:41, sector
954418
Aug 18 06:41:01 proxy1 kernel: EXT2-fs error (device 09:00):
ext2_read_inode: unable to read inode block - inode=477228,
block=1908837
Aug 18 06:42:00 proxy1 /USR/SBIN/CRON[765]: (root) CMD (run-parts --report
/etc/cron.daily)
Aug 18 06:45:01 proxy1 /USR/SBIN/CRON[818]: (root) CMD (/usr/sbin/atrun)
As you can see after about 5 minutes, everything returns to normal. This
happened only a couple times - and currently everything seems to be
running just fine. Any suggestions would be greatly appreciated!
Thanks in advance...
Marcus Hecht
====================================================
Marcus Hecht PCs Made Easy
Support Specialist Internet Services
marcus@pcez.com http://www/pcez.com
====================================================
Received on Tue Aug 18 1998 - 12:07:36 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:41:38 MST