DriveReady SeekComplete Error & DriveStatusError BadCRC

[messyone]

Hi all

We have a Fedora Core 4 server that was working 100% for the past month but now over the past day it has froozen up 3 times with the hard drive light on.
Had to remove power to reboot the box. We have done no updates etc...

Errors that I see:
hde:hde: recal_intr: status=0x51 { DriveReady SeekComplete Error }
hde: recal_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hde1 hde2
hdf: max request size: 128KiB
hdf: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63, BUG
hdf: cache flushes not supported
hdf:hdf: recal_intr: status=0x51 { DriveReady SeekComplete Error }
hdf: recal_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hdf1
hdg: max request size: 128KiB
hdg: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63, BUG
hdg: cache flushes not supported
hdg:hdg: recal_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: recal_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hdg1

Plus more errors:
cdrom: open failed.
input: AT Translated Set 2 keyboard as /class/input/input0
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: recal_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: recal_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide3: reset: master: error (0x00?)
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: dm-0: orphan cleanup on readonly fs

Any idea's????

[tomcat]

There are several things that could cause this:

1. Have you updated a kernel recently (just before the problem appeared)? If yes, then it is probably a kernel bug with improper DMA modes.

2. Have you perhaps wrong cables attached to the drive (40 vs 80 nodes)? Wrong cables can cause this error, too.

3. Is the drive older? If yes, it may well be that it is nearing its end. Backup all data, download diagnostic tools from the disk-manufacturer and check the drive thoroughly for bad sctructure/sectors. If you hear a clicking sound, then the drive is slowly collapsing and a new drive must be bought.

[dbits]

Hi,

I have a similar problem after upgrading from FC5 to FC6, very tedious messages like:

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown

The HD is few weeks old and in good state, I have tested it with full diagnostics sw provided by the factory (Hitachi).
On the same hd I have installed Knoppix 5.0.1, and there are not problems at all.
Then I can exclude hw problems at 100% as well, but I cannot use DMA and disabled it. This is not a solution, my system is very tedious on long files transfers.
On the net I found only a possible solution: patching kernel iosched, see http://lkml.org/lkml/2006/8/27/108.
Do you know if FC6 developers are working on it? Or other solutions?

Thanks

[tomcat]

In your case it seems to be a kernel bug. Check bugzilla if they are working on it and submit a new bug if there is no entry yet. Or ask on IRC.

[dbits]

Thanks tomcat... already done, I have found a similar bug already opened https://bugzilla.redhat.com/bugzilla....cgi?id=214566

Bye