periodic disk error messages

[NewtownGuy]

Hello,

I'm seeing periodic disk error messages in Fedora Core 3. At about 4 AM everyday, and over about 1/2 hour, I'm seeing the same errors. So some periodic task must be running.

smartd is active using default settings. I ran short, long and conveyance tests with smartctl and there aren't any errors.

Are these errors significant ? What do they mean ? How do I stop them ?

Here are several parts of syslog that show the errors. I put some lines in blue to show the grouping of the errors:

[COLOR=blue]Sep  3 04:03:50 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  3 04:03:50 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  3 04:03:50 -001 kernel: ide: failed opcode was: unknown
[/color]Sep  3 04:14:35 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  3 04:14:35 -08072007-001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  3 04:14:35 -001 kernel: ide: failed opcode was: unknown
Sep  3 04:31:02 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  3 04:31:02 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  3 04:31:02 -001 kernel: ide: failed opcode was: unknown
Sep  3 04:34:00 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  3 04:34:00 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  3 04:34:00 -001 kernel: ide: failed opcode was: unknown
Sep  3 04:35:09 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  3 04:35:09 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  3 04:35:09 -001 kernel: ide: failed opcode was: unknown

-- snip --

[COLOR=blue]Sep  4 04:07:20 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  4 04:07:20 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  4 04:07:20 -001 kernel: ide: failed opcode was: unknown
[/color]Sep  4 04:09:39 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  4 04:09:39 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  4 04:09:39 -001 kernel: ide: failed opcode was: unknown
Sep  4 04:10:59 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  4 04:10:59 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  4 04:10:59 -001 kernel: ide: failed opcode was: unknown
Sep  4 04:19:48 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  4 04:19:48 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  4 04:19:48 -001 kernel: ide: failed opcode was: unknown
Sep  4 04:29:31 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  4 04:29:31 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  4 04:29:31 -001 kernel: ide: failed opcode was: unknown
Sep  4 05:01:02 -001 crond(pam_unix)[19385]: session opened for user root by (uid=0)
Sep  4 05:01:02 -001 crond(pam_unix)[19385]: session closed for user root
Sep  4 05:23:29 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  4 05:23:29 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  4 05:23:29 -001 kernel: ide: failed opcode was: unknown
Sep  4 05:26:32 -001 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep  4 05:26:32 -001 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep  4 05:26:32 -001 kernel: ide: failed opcode was: unknown

Thank you.

-- NewtownGuy

 

[giganetwireless]

Give this site a look...

http://www.captain.at/howto-linux-driveready-seekcomplete-error-drivestatuserror.php

Regards

 

[Annihilannic]

Red Hat runs its daily and weekly cron jobs at 4am, which is why they are coming up at that time. See the contents of /etc/cron.daily and /etc/cron.weekly. It may be related to the updatedb job that runs out of slocate.cron to update the database used by the locate command, or something like that.

Annihilannic.