From owner-freebsd-questions Wed Sep 18 9: 1: 7 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF3B737B401 for ; Wed, 18 Sep 2002 09:01:05 -0700 (PDT) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1958F43E3B for ; Wed, 18 Sep 2002 09:01:05 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198]) by be-well.ilk.org (8.12.6/8.12.5) with ESMTP id g8IFogLm013972; Wed, 18 Sep 2002 11:50:42 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.6/8.12.6/Submit) id g8IFog5x013969; Wed, 18 Sep 2002 11:50:42 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f To: "Jack L. Stone" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Server Lockups during Backups ad0 to ad1 References: <3.0.5.32.20020916122857.0117d8b8@mail.sage-one.net> From: Lowell Gilbert Date: 18 Sep 2002 11:50:41 -0400 In-Reply-To: <3.0.5.32.20020916122857.0117d8b8@mail.sage-one.net> Message-ID: <44sn07wb3i.fsf@be-well.ilk.org> Lines: 42 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Jack L. Stone" writes: > Am running FreeBSD 4.5-RELEASE Updating might help; there are some changes to the ATA code which I think *might* be relevant. Don't do that first, though; it could certainly compound your problems. > BTW, the BIOS doesn't even show the ad1 IDE on first reboot, which takes a > hard switch reset. Tnen a complete power down/power up to bring the ad1 HD > in the BIOS back....OUCH! Is scary for this server which is not very old. [...] > ============================================================================== > Sep 16 10:38:23 sage-one /kernel: ad1: WRITE command timeout tag=0 serv=0 - > resetting > Sep 16 10:40:07 sage-one /kernel: ata0: resetting devices .. done > Sep 16 10:40:07 sage-one /kernel: ad1: WRITE command timeout tag=0 serv=0 - > resetting > Sep 16 10:40:07 sage-one /kernel: ata0: resetting devices .. done This looks like the drive is going out to lunch. > 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 This looks like an actual media problem on the drive. > Sep 16 10:40:07 sage-one /kernel: ad1: timeout waiting for DRQ - resetting > Sep 16 10:40:07 sage-one /kernel: ata0: resetting devices .. done > Sep 16 10:40:07 sage-one /kernel: ad1: timeout waiting for DRQ - resetting > Sep 16 10:40:07 sage-one /kernel: ata0: resetting devices .. done > Sep 16 10:40:07 sage-one /kernel: swap_pager: indefinite wait buffer: > device: #ad/0x20001, blkno: 392, size: 4096 The drive seems to have gone away... I'd recommend starting by replacing the ad1 drive, if possible. Good luck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message