On Sat, Oct 05, 2002 at 05:01:49PM +0800, JCS wrote:
> On Saturday 05 October 2002 16:43, Arjan van de Ven wrote:
> > > hdc:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > > hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
> >
> > BadCRC errors are a cable issue. The drive sends its data and includes a
> > crc checksum; the controller receives the data and notices the data is
> > corrupted via the checksum.
> >
> > Are you sure you have an 80 ribbon cable (as opposed to a 40 ribbon
> > one)? Is it one of those ultra-long cables?
>
> 40-wire cables work, they're just slower.
>
> In _my_ experience, CRC errrors are dead drives.
Not in mine. I've got a different Via chipset, and I was getting lots of
CRC errors. I swapped the drive for a different one, and the system is
working fine. Strangely enough, I put that original drive into my
Windows system and it's working flawlessly. So...the cables and drives
are all fine, but Linux didn't like that original drive. It's running
Red Hat Linux 7.1.
I'm convinced that there are some incompabilities between some chipsets
and some drives, but I haven't narrowed it down beyond that.
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:ewilts@;ewilts.org
Member #1, Red Hat Community Ambassador Program
