From owner-freebsd-questions Fri Apr 14 15: 2: 9 2000 Delivered-To: freebsd-questions@freebsd.org Received: from area51.v-wave.com (area51.v-wave.com [24.108.26.39]) by hub.freebsd.org (Postfix) with SMTP id 49BF237B525 for ; Fri, 14 Apr 2000 15:02:06 -0700 (PDT) (envelope-from flatline@area51.v-wave.com) Received: (qmail 33036 invoked by uid 1001); 14 Apr 2000 22:02:04 -0000 Date: Fri, 14 Apr 2000 16:02:04 -0600 From: Chris Wasser To: Otter Cc: Oscar Ricardo Silva , freebsd-questions@FreeBSD.ORG Subject: Re: Large disks (34GB), mounting and newfs problems Message-ID: <20000414160204.A32946@area51.v-wave.com> References: <4.2.2.20000414161740.00a82a60@mail.utexas.edu> <38F7922C.B936D566@otter.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38F7922C.B936D566@otter.cc>; from otter@otter.cc on Fri, Apr 14, 2000 at 05:48:28PM -0400 X-Operating-System: FreeBSD 4.0-STABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 14, 2000 at 05:48:28PM -0400, Otter wrote: > IIRC, there was a bug in the wd driver that made it hiccup on disks > >27GB. If you're running under 3.x or 4.0, try upgrading to the ata (ad) driver for a fix. > -Otter I had a similar problem with a 37GB maxtor drive under 3.x and solved it by using the b0ffb0ff flags on the wd driver, after that I was able to newfs and mount it no problem, ie: controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xb0ffb0ff disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xb0ffb0ff disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 hth... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message