From owner-freebsd-stable Tue Sep 17 14: 5:48 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 607E137B401 for ; Tue, 17 Sep 2002 14:05:47 -0700 (PDT) Received: from nat72962.owentools.com (nat72962.owentools.com [206.50.138.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11F5D43E42 for ; Tue, 17 Sep 2002 14:05:47 -0700 (PDT) (envelope-from craig@meoqu.gank.org) Received: by owen1492.it.oot (Postfix, from userid 1001) id D4828AB52; Tue, 17 Sep 2002 15:59:06 -0500 (CDT) Subject: Re: Server lockups/crashes From: Craig Boston To: "Jack L. Stone" Cc: freebsd-stable@freebsd.org In-Reply-To: <3.0.5.32.20020917151456.0118ee90@mail.sage-one.net> References: <3.0.5.32.20020917151456.0118ee90@mail.sage-one.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 17 Sep 2002 15:59:06 -0500 Message-Id: <1032296346.399.11.camel@owen1492.it.oot> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2002-09-17 at 15:14, Jack L. Stone wrote: > ERROR LOG > #################################################################### > Sep 16 10:38:23 sage-one /kernel: ad1: WRITE command timeout tag=0 > serv=0 - resetting <----snip---> > Sep 16 10:40:07 sage-one /kernel: ad1s1f: hard error writing fsbn > 23516351 of 5466688-5466943 (ad1s1 bn 23516351; cn 1463 tn 210 sn > 26)ata0-slave: timeout waiting for command=ef s=01 e=04 <----snip---> > Sep 16 10:40:07 sage-one /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x20001, blkno: 392, size: 4096 > #################################################################### > LOCKED UP FROM HERE ON...... > ==================================================================== Could possibly be a dying hard drive or bad connection; especially if even the BIOS intermittently doesn't detect it. If possible, check the cables or try swapping this disk with another. It looks like the problems with ad1 are causing the ata driver to reset the bus as a last resort, and the system is hanging as it tries to swap to ad0 (which is temprarily unavailable due to the bus reset)... That's just a guess. If there isn't anything there, you might try putting this disk on ata1 (secondary master rather than primary slave). It would become ad2 and might avoid killing the entire system when it has problems. For a disk-to-disk backup, it might be a good idea anyway and improve performance (ad0 and ad1 share bandwidth). Hope this helps, Craig Boston To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message