Alan Cox wrote:
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>
> CRC errors are cable errors so that bit is reasonable in itself
Could this be caused by the RAID configuration? The first sector of the
first disk holds the partition table. The other disks in the raid have
no valid partition table:
dmesg message from Jussi Laako:
hdf: unknown partition table
hdg: unknown partition table
hdh: unknown partition table
[snip]
If there is a raid (1+)0 configured you got a volume that is bigger than
the first hd. So if you have extended partitions or freebsd slices which
are located beyond the capacity of the hd, then the partition table
check would have to read datastructures which have an offset which is to
high. => read error during partition check => nasty error messages
I have the error message problem on my box. DMA is disabled because of
the error on /dev/hda. But a hdparm -d 1 /dev/hda fixes this, and I do
not get more errors regarding that. Everything works fine. (I did not
compile with Athlon optimization.)
regards,
Wilfried
-
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 May 23 2001 - 21:00:32 EST