Date: Tue, 23 Sep 2003 16:14:04 +0200 From: "Putinas" <pilkis@gmx.net> To: <freebsd-current@FreeBSD.ORG> Subject: Re: SATA drive lock-up Message-ID: <004c01c381dc$f27aace0$1e64a8c0@spotripoli.local> References: <200309200807.h8K87j38049734@spider.deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi all, Inspired with all the FreeBSD is free software , windows and buggy hardware and blabla I realize what maybe I could do more to help solve this problem. I made small research on my computer and I find out what till the cvsup date 2003.08.24.00.00.00 till ATAng commitment to the source my SATA Sil3112A working fine. After this date I always get WRITE_DMA recovered from missing interrupt error after more or less intensive input output with harddisk subsystem , and after I/O error and so on ... My bet is what in this case buggy is not hardware .. at least this bug didn't show up until 25 August Best regards, Putinas ----- Original Message ----- From: "Soren Schmidt" <sos@spider.deepcore.dk> To: "Derek Ragona" <derek@computinginnovations.com> Cc: <freebsd-current@FreeBSD.ORG> Sent: Saturday, September 20, 2003 10:07 Subject: Re: SATA drive lock-up > It seems Derek Ragona wrote: > > I have a single SATA drive on an Adaptec 1210SA card. > > > > The drive will give a write error warning a few times, then will repeatedly > > give: > > ad4: timeout sending command=ca > > > > The only recovery is the reset switch, reboot single-user fsck, and then > > come back up in multiuser. > > > > These errors occur with disk access, but not with a predictable nature (not > > on large files, or small files, etc.) > > And you are on an uptodate -current ? > > If so I'd suspect HW ... > > -Søren > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004c01c381dc$f27aace0$1e64a8c0>