Date: Wed, 18 Sep 2002 11:06:08 -0500 From: "Jack L. Stone" <jackstone@sage-one.net> To: tonerboy <geoffrey@reptiles.org> Cc: freebsd-stable@freebsd.org Subject: Re: Server lockups/crashes Message-ID: <3.0.5.32.20020918110608.00e8d428@mail.sage-one.net> In-Reply-To: <20020918111627.S76715-100000@iguana.reptiles.org> References: <1032296346.399.11.camel@owen1492.it.oot>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:26 AM 9.18.2002 -0400, tonerboy wrote: >On 17 Sep 2002, Craig Boston wrote: > >> 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. >> > Yes. And if all else fails, it wouldn't hurt to try another >(beefier?) power supply. Had this happen to me twice in one week (once >with scsi, second with ide). > Power supply is pretty ample at 400W.... but have got it figured out now I hope. Removing the two (new) Quantum Fireball HDs in this server and replacing with two new Seagate HDs may have done the trick! On original install, I had noticed that the jumpering of the Quantums did not make sense and were not according to the diagrams sent with the drives in order for the BIOS to see them properly. Had to reverse the placement and make 'em both the same -- otherwise the BIOS could not see the 2nd HD..!! (BIOS is current) That had made me suspicious as a top contender as being the cuplrit. The Seagates are running fine now as two Masters. Have yet to run the big test of dump/restore, but want the busy server to settle in before trying again. (incantations now under way though!) Funny though, the Quantums are now recognized properly in the BIOS of another machine and are doing fine and did the dump/restore without a hitch. Jumpers work were they should Strange! Makes me think the BIOS on the server with the problem is a little flaky... Fairly new 1.6GHz AMD Athlon GA-7DX AMD 761 Chipset 1GB RAM. Thanks to everyone who responded. At least helped me eliminate some possibles. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20020918110608.00e8d428>