Error with CMD 649 ATA100 controller while copying files over NFS on 4.11-Stable

Doug White dwhite at
Tue Mar 8 18:38:02 GMT 2005

On Sat, 5 Mar 2005, Eric Buchanan wrote:

> Hash: SHA1
> I switched one hard drive to a CMD 649 ATA100 controller last summer, and I've
> had some trouble with it on 4.11-Stable. When I copy a large volume of files
> over NFS (800 Megabytes, lets say) the add on controller will stop
> recognizing my hard drive. This time the files were not being copied off a
> drive handled by this controller.
> Any ideas? This only occurs when copying files over nfs, and it will happen
> even when I am not copying anything involving the drive on the controller.
> I've tried "atacontrol reinit 2" and it won't re-recognize the hard drive
> (ad5s4f).  I have absolutely zero problems when I am not using NFS,
> especially zero problems with make worlds or building large ports on this
> hard drive in question.

the CMD controller chips are known to be poor quality, you may be better
off switching to a different controller. And change the cables out while
you're at it.

The messages below indicate that the drive itself is getting confused and
ceasing to respond, but its hard to tell.

> ad5: 57241MB <OEM60-54A 60GB 5400RPM> [116301/16/63] at ata2-slave UDMA100

What brand/model is this drive, actually?  It looks like its lost its
identity data.

> ad5s4f: soft error (ECC corrected) reading fsbn 185641109 of 84275072-84275075
> (
> ad5s4 bn 185641109; cn 11555 tn 159 sn 17)ad5s4f: hard error reading fsbn
> 185641                                                              109 of
> 84275072-84275075 (ad5s4 bn 185641109; cn 11555 tn 159 sn 17) trying PIO
> mode
> ad5: READ command timeout tag=0 serv=0 - resetting
> ata2: resetting devices ..
> ad5: removed from configuration
> done

Doug White                    |  FreeBSD: The Power to Serve
dwhite at          |

More information about the freebsd-stable mailing list