| I've seen people mention in comp.os.linux.development.system that the
| BadCRC error may indicate a cable problem. However, (a) I'm pretty
| certain that I'm using Ultra66 cables for both hde and hdg, and (b) if
| that's the problem, why don't I get the same errors with 2.2.19?
|
| As for (a), I believe I've got the right cables because I checked when
| I installed them and because the controller (Promise Ultra66)
| recognizes both hde and hdg as Ultra-capable drives when it starts up
| (which it wouldn't do if I didn't have the correct cables -- I know
| this because it wasn't doing it when I didn't have the correct cables
| ;-).
I've had drive problems simply as a result of bad _instances_ of cables,
even though it was the right kind of cable. I've also had drive problems
as a result of looseness of connections. Some connector _instances_
seem to be more prone to this, and some headers on some motherboards
also seem to be more prone to this.
<paranoid>
Pull the cable and clean all the connections on the cable, board, and
drive. High pressure air is good enough in most cases, but liquid
cleaner might be needed in some. Check the cable for dings, nicks,
and sharp bends. These have more impact on ATA66 cables. If it has
any, get a new cable and cut the old one in half. If you have a
single ATA66 drive, be sure it is on the _end_ connector. While you
can cut off the end of older IDE cables to make short ones, not so
with ATA66 cables. Leave the middle connector dangling or get a cable
with just 2 connectors. Also, don't "round" an ATA66 cable.
</paranoid>
And finally, I actually have a couple drives that exhibit these problems
no matter what I do. The drives _can_ simply be bad.
-- ----------------------------------------------------------------- | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | | phil-nospam@ipal.net | Texas, USA | http://phil.ipal.org/ | ----------------------------------------------------------------- - 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/