I fixed this on one of my servers by buying a new UDMA cable.  The
original was about 3" longer than the new one.

wojtek@wojtek.from.pl wrote:
> 
> > wd0: drive supports 16-sector pio transfers, lba addressing
> > wd0: 29319 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 60046560
> > sectors
> > wd0: 32-bit data port
> > wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5
> > wd1 at pciide0 channel 0 drive 1: <FUJITSU MPA3043ATU>
> > wd1: drive supports 32-sector pio transfers, lba addressing
> > wd1: 4172 MB, 9042 cyl, 15 head, 63 sec, 512 bytes/sect x 8544940 sectors
> > wd1: 32-bit data port
> > wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2
> > wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data
> > transfers)
> > wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 (using DMA data
> > transfers)
> > wd1: no disk label
> > boot device: wd0
> > root on wd0a dumps on wd0b
> > wd0: transfer error, downgrading to Ultra-DMA mode 1
> > wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 1 (using DMA data
> > transfers)
> > wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 (using DMA data
> > transfers)
> > wd0a: aborted command, interface CRC error writing fsbn 16 of 16-31 (wd0
> > bn 79; cn 0 tn 1 sn 16), retrying
> > wd0: soft error (corrected)
> > /dev/wd0e: file system not clean (fs_flags=20); please fsck(8)
> exactly the same error my friend has. and then everything works right (but
> with UDMA 1 only)