Date: Sat, 14 Jan 2006 15:45:30 -0800 From: Sebastian <list@mindling.com> Cc: freebsd <freebsd-questions@freebsd.org> Subject: Re: Getting around WRITE_DMA errors Message-ID: <43C98D1A.8030909@mindling.com> In-Reply-To: <43C97BE6.5060901@mindling.com> References: <43C96C73.9010904@mindling.com> <0T2rehckIn3Nv9%markus@bsd.trippelsdorf.de> <43C97BE6.5060901@mindling.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sebastian wrote: > Markus Trippelsdorf wrote: > >> Are you sure that your hard drive is not dying? Run smartctl -a >> /dev/ad0 and see if any errors were being logged. >> (smartctl is part of the smartmontools port) >> You should also try another cable. >> >> > Thanks for the response. I'm reasonably sure, the disk is brand new, > and though it could certainly be bad, I installed Linux on the system > this morning without issue. I've tried two different UDMA cables also, > just to be sure. Under PIO4 mode in BSD (by setting hw.ata.ata_dma=0), > I can install and then write data to my heart's content without any > errors. > > I'm currently reinstalling again, because I believe a partition has > become corrupted after panicking with the disk in UDMA6 mode. > Just as a followup: Attempting to run "atacontrol mode ad0 UDMA6" resulted in WRITE_DMA48 errors and a panic. Afterwards, disk access was slow, and trying to use _any_ UDMA mode resulted in DMA errors being logged, and eventually another panic. Having briefly tested UDMA3-5 with success previously, I felt that the partitions must have been corrupted somehow, so I reinstalled FreeBSD from scratch. It's better, after booting with "hw.ata.ata_dma=0" and then running "atacontrol mode ad0 UDMA5", it's running fine using UDMA5 and copying lots of data around: # atacontrol mode ad0 current mode = UDMA100 So my question remains: How do I tell FreeBSD to use UDMA5 on this drive at boot-time? Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43C98D1A.8030909>