From owner-freebsd-questions Mon Jul 2 17:57:50 2001 Delivered-To: freebsd-questions@freebsd.org Received: from q.closedsrc.org (ip233.gte15.rb1.bel.nwlink.com [209.20.244.233]) by hub.freebsd.org (Postfix) with ESMTP id 90B6537B403 for ; Mon, 2 Jul 2001 17:57:47 -0700 (PDT) (envelope-from lplist@closedsrc.org) Received: by q.closedsrc.org (Postfix, from userid 1003) id 4AB2E55407; Mon, 2 Jul 2001 17:42:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by q.closedsrc.org (Postfix) with ESMTP id 391AB51610; Mon, 2 Jul 2001 17:42:53 -0700 (PDT) Date: Mon, 2 Jul 2001 17:42:53 -0700 (PDT) From: Linh Pham To: W Gerald Hicks Cc: Jim Freeze , Subject: Re: Is mod_php4 broken in ports? In-Reply-To: <0GFV00DWNGVQFM@mta1.snfc21.pbi.net> Message-ID: 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 On 2001-07-02, W Gerald Hicks scribbled: # Doesn't seem likely with a single bit error that softupdates would be to # blame; you'd probably see big hunks of data whacked if something were # wrong there. Some drives require you to force set them down from ATA66 or ATA100 to ATA33 if you are using a standard 40-pin cable or an ATA33 controller. You may need to check the hard drive manufacturer's website to see if you need to do that for your drive. # I suppose the drive and/or cable might be the culprit but didn't you see # Sig 11's too? In one of the earlier messages, there were some SIG 11's in the output. Not good :) -- Linh Pham [lplist@closedsrc.org] // 404b - Brain not found To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message