From owner-freebsd-questions Thu Sep 30 20:43:27 1999 Delivered-To: freebsd-questions@freebsd.org Received: from inet03.citec.qld.gov.au (inet03.citec.qld.gov.au [203.5.10.10]) by hub.freebsd.org (Postfix) with ESMTP id EE1FB14EBC for ; Thu, 30 Sep 1999 20:43:22 -0700 (PDT) (envelope-from sgcccdc@citec.qld.gov.au) Received: by inet03.citec.qld.gov.au; id NAA03887; Fri, 1 Oct 1999 13:43:21 +1000 (EST) Received: from guru.citec.qld.gov.au( 147.132.20.47) by inet03.citec.qld.gov.au via smap (V2.0) id xma003782; Fri, 1 Oct 99 13:43:12 +1000 Received: from localhost (sgcccdc@localhost) by guru.citec.qld.gov.au (8.8.5/8.8.5) with SMTP id NAA18975 for ; Fri, 1 Oct 1999 13:43:13 +1000 X-Authentication-Warning: guru.citec.qld.gov.au: sgcccdc owned process doing -bs Date: Fri, 1 Oct 1999 13:43:13 +1000 (EST) From: Colin Campbell To: freebsd-questions@freebsd.org Subject: installation problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Pentium III 450, BX2000 motherboard, 512MB RAM, Adaptec 2940B UW SCSI (auto termination), 1xIBM 34560D (4.35GB, SCSI-id=1), 1xQuantum Viking II (4.35GB SCSI-id=0, terminated). Trying to install 3.2 from the Walnut Creek CD-ROM/Book. It gets to installing the bin dist (from "User" set, default disk partitions) into / and it will then either: Write failure on transfer (write returns -1) (If I try again, it normally panics the machine) or just plain panics (saw a virtual address 0xc once) I have tried without the IBM disk, disabling the CPU secondary cache, disabling cpu internal and secondary cache (boy did that slow it down!). I have even tried installing Red Hat 6.0 (machine panicked) and BSDI 3.1 (no problems at all!) The machine came with BSDI/3.1 on it. Is that significant? Searching the archives showed a thousand people over a thousand years getting the write fails but I only found one reply. That one suggested any or all of: 1) disabling cache (tried that - ran slow then panicked) 2) check SCSI termination (done that) 3) put DOS on then overwrite it (not yet) Or is all this a symptom of the hardware being screwed? Colin -- Colin Campbell Unix Support/Postmaster/Hostmaster CITEC +61 7 3227 7112 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message