> Sep 1 19:32:59 localhost kernel: hdd: dma_timer_expiry: dma status == 0x41
> Sep 1 19:33:09 localhost kernel: hdd: DMA timeout error
> Sep 1 19:33:09 localhost kernel: hdd: dma timeout error: status=0xf1 {Busy
> } Sep 1 19:33:09 localhost kernel:
> Sep 1 19:33:09 localhost kernel: hdd: DMA disabled
> Sep 1 19:33:09 localhost kernel: ide1: reset: master: error (0x7f?)
> Sep 1 19:33:09 localhost kernel: hdd: set_geometry_intr: status=0x71
> {DriveReady DeviceFault SeekComplete Error }
> Sep 1 19:33:09 localhost kernel: hdd: set_geometry_intr: error=0x04
> {DriveStatusError }Have you tried swapping drives/jumpers round so that the problematic drive is the master? Possibly also try putting it on its own channel. Misconfigured multiple-drive IDE setups will often appear to work, then give strange errors. I've seen problems when mixing master/slave drives with different capabilities, particularly when the master was a cdrom drive. AFAICT this is caused by buggy drive hardware/firmware, and the only solution is to move things about till you find a configuration that works. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
