search for: badcrc

...02:55:07 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_find_entry: bad entry in directory #1111941: inode out of bounds - offset=36, inode=537868397, rec_len=12, name_len=4 I've also had these messages too Nov 3 20:25:42 jaguar kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Nov 3 20:34:07 jaguar kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } I'm just guessing, but i presume it's a sign of a bad hard drive? Thanks, Matt

I am getting occasional seek error on my boot drive. The messages are as follows: pshda: dma_intr: status = 0x51 { Drive ReadySeekComplete Error } hda: dma_intr: error= 0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown Everything seems to be working fine but these errors do have me concerned. The last time they occurred I was created a fairly large cpio backup file in the '/tmp' directory. The drive has been checked via fsck, and any errors found were reported to be...

...vice: /dev/hda, 993 Currently unreadable (pending) sectors For details see host's SYSLOG (default: /var/log/messages). Nov 23 18:20:22 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Nov 23 18:20:22 localhost kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Nov 23 18:20:22 localhost kernel: ide: failed opcode was: unknown Nov 23 18:20:22 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Nov 23 18:20:22 localhost kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Nov 23 18:20:22 localhost kernel: ide: failed op...

...er botting the machine up everything works fine again: the /hdc1 and /hdc2 partitions were cleaned and are accessible. However the I still notice the following errors in the /var/log/messages (occasionaly): ----------------- Oct 26 12:19:38 lynx kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 26 12:19:38 lynx kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } ----------------- I am trying to determine where the problem is: - connection cable, - motherboard IDE port, - hard drive, - ext3 filesystem in kernel 2.4.18-27.7.x. - sth else. I'd appreciate any hel...

Can anyone point me in the right direction for correcting errors on an HD when using LVM? I've tried e2fsck and indicates bad block. I've tried with -b 8193, 16384, and 32768 and no good. I've found some info about reiserfsck on google, but this utility doesn't seem to be included in Centos4.3. I did find it on my old FC1 box. I am thinking now I really should have went with

...s been going on quite a while. I've posted before with no success on getting this fixed. I was getting these errors. Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } And now for the amazing smartctl -a command. The output actually had a link that advised and directed me to a link to upgrade my firmware, which looks to have fixed it. Simply amazing. smartctl -a /dev/hda: smartctl version 5.33 [i686-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen Home p...