From owner-freebsd-current Tue Oct 20 12:39:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24050 for freebsd-current-outgoing; Tue, 20 Oct 1998 12:39:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24044 for ; Tue, 20 Oct 1998 12:39:47 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id NAA29092; Tue, 20 Oct 1998 13:32:28 -0600 (MDT) Date: Tue, 20 Oct 1998 13:32:28 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199810201932.NAA29092@narnia.plutotech.com> To: Vijay Ramasubramanian cc: current@FreeBSD.ORG Subject: Re: Installation probs w/3.0 In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > Briefly stated, I was always getting installation crashes around the 40th > chunk with messages that indicated FS corruption (stuff such as > ufs_dirbad, ffs_alloccg: bad map, and so on). > > My hardware config is as below: > > AMD K6-233 (one of the latest revisions) > Intel TX chipset motherboard w/512KB cache > 64 MB SDRAM in 1 DIMM > AdvanSys ABP-940 SCSI host adapter, SCSI ID 7 Is this an ABP-940, an ABP-940U, an ABP-940UA, or an ABP-940UW? I have all three here, and I want to ensure that I use the same board you have to reproduce the bug. > IBM DCAS 2.2 GB Ultra SCSI drive, SCSI ID 0 > IBM DCAS 2.2 GB Ultra SCSI drive, SCSI ID 1 > Fujitsu 405 MB Fast SCSI-2 drive, SCSI ID 2 Which of these drives is being accessed at the time of the failure? Does the Fujitsu claim to support tagged queuing? Are there any SCSI error messages printed on the console? You can get this information by hitting and once you hit the install screen to see the kernel messages for the drives. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message