On Wednesday 06 Apr 2005 13:42 pm, you wrote:
I was seeing the exact same thing happen in SusE 9.1 with a Seagate drive. As it turned out it was a ATA133 drive that I had hooked up as a slave on a ATA100 cable. In spite of the apparent "errors" I was not losing any data, so I ignored it. When I rebuilt the system I used that drive as a master with the proper cable and the problem went away.
Just a quick tip: If you're ever in that situation again, you can download a utility from Seagate that lets you tell the drive to run at a different maximum speed. Just runs off a bootable DOS floppy and lets you change some of the drive's parameters which are stored in non-volatile RAM somewhere, so you only have to do it once and it remembers the setting until you change it back. See the "Ultra ATA Mode Switching Utility" description here: http://www.seagate.com/support/disc/utils.html Cheers, Matt -- "It's the small gaps between the rain that count, and learning how to live amongst them." -- Jeff Noon