From owner-freebsd-questions Tue Apr 24 4:17: 0 2001 Delivered-To: freebsd-questions@freebsd.org Received: from deborah.paradise.net.nz (deborah.paradise.net.nz [203.96.152.32]) by hub.freebsd.org (Postfix) with ESMTP id 6878F37B42C for ; Tue, 24 Apr 2001 04:16:57 -0700 (PDT) (envelope-from davep@afterswish.com) Received: from duron700.afterswish.com (203-79-83-91.cable.paradise.net.nz [203.79.83.91]) by deborah.paradise.net.nz (8.11.3/8.11.3) with ESMTP id f3OBGtU27921 for ; Tue, 24 Apr 2001 23:16:55 +1200 (NZST) Message-Id: <5.0.2.1.1.20010424231436.02358ec0@pop3.paradise.net.nz> X-Sender: dpreece@pop3.paradise.net.nz X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 24 Apr 2001 23:18:34 +1200 To: freebsd-questions@freebsd.org From: David Preece Subject: Apache + php4 problem, probably solved. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I decided to do the build process by 'hand' to see where the problem was: bash-2.03# ./configure --activate-module=src/modules/php4/libphp4.a Configuring for Apache, Version 1.3.12 + using installation path layout: Apache (config.layout) + activated php4 module (modules/php4/libphp4.a) Creating Makefile Creating Configuration.apaci in src Creating Makefile in src + configured for FreeBSD 4.0 platform + setting C compiler to gcc + setting C pre-processor to gcc -E + checking for system header files + adding selected modules o php4_module uses ConfigStart/End ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: read interrupt arrived earlyad0: read error detected latead0: HARD READ ERROR blk# 1011231 status=50 error=00 Apr 24 23:09:59 firewall /kernel: ad0: READ command timeout - resetting Apr 24 23:09:59 firewall /kernel: ad0: READ command timeout - resetting Apr 24 23:09:59 firewall /kernel: ata0: resetting devices .. done Apr 24 23:09:59 firewall /kernel: ata0: resetting devices .. done Apr 24 23:09:59 firewall /kernel: ad0: read interrupt arrived earlyad0: read error detected latead0: HARD READ ERROR blk# 1011231 status=50 error=00 Apr 24 23:09:59 firewall /kernel: ad0: read interrupt arrived earlyad0: read error detected latead0: HARD READ ERROR blk# 1011231 status=50 error=00 Apr 24 23:09:59 firewall /kernel: pid 6892 (ld), uid 0: exited on signal 11 (core dumped) Apr 24 23:10:01 firewall /kernel: pid 6928 (ld), uid 0: exited on signal 11 (core dumped) Apr 24 23:10:02 firewall /kernel: pid 6965 (ld), uid 0: exited on signal 11 (core dumped) Apr 24 23:10:04 firewall /kernel: pid 7002 (ld), uid 0: exited on signal 11 (core dumped) Apr 24 23:10:05 firewall /kernel: pid 7040 (ld), uid 0: exited on signal 11 (core dumped) + checking sizeof various data types Apr 24 23:10:07 firewall /kernel: pid 7084 (ld), uid 0: exited on signal 11 (core dumped) + doing sanity check on compiler and options So, that's what a disk losing the plot looks like? While we're on the subject, how can I pre-empt something like this? How can I get FreeBSD to do a scan of the surface of the disk for these 'hard read errors', or is it a question of RAID if it's that important... Thanks, Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message