From owner-freebsd-questions@FreeBSD.ORG Mon Oct 18 12:19:52 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AF4416A4CE for ; Mon, 18 Oct 2004 12:19:52 +0000 (GMT) Received: from amsfep14-int.chello.nl (nl-ams-slo-l4-01-pip-5.chellonetwork.com [213.46.243.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49E6543D1F for ; Mon, 18 Oct 2004 12:19:50 +0000 (GMT) (envelope-from Danovitsch@Vitsch.net) Received: from Vitsch.net ([212.187.78.35]) by amsfep14-int.chello.nl (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20041018121948.EPBB26025.amsfep14-int.chello.nl@Vitsch.net>; Mon, 18 Oct 2004 14:19:48 +0200 Received: from 192.168.1.254 (f59122.upc-f.chello.nl [80.56.59.122]) by Vitsch.net (8.12.3p2/8.11.3) with ESMTP id i9ICJjun004254; Mon, 18 Oct 2004 14:19:45 +0200 (CEST) (envelope-from Danovitsch@Vitsch.net) From: "Daan Vreeken [PA4DAN]" To: Svein Halvor Halvorsen Date: Mon, 18 Oct 2004 14:19:42 +0200 User-Agent: KMail/1.5.2 References: <20041018125351.R24455@maren.thelosingend.net> In-Reply-To: <20041018125351.R24455@maren.thelosingend.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410181419.42642.Danovitsch@Vitsch.net> cc: FreeBSD-Questions@FreeBSD.org Subject: Re: 128 GiB+ disks on Intel PIIX4 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 12:19:52 -0000 On Monday 18 October 2004 13:03, Svein Halvor Halvorsen wrote: > Is this at all possible? My BIOS don't seem to recognize my brand new 200 > GB disk, but that is nothing new. I can initialize a new slize, setup > bsdlabel and do newfs on if without problems. How can I verify that the > entire disk is usable without filling it all up (or past the 128 GiB > barrier), and then reading everything back out? Try copying the entire disk to /dev/null : dd if=/dev/ad1 of=/dev/null If it succeeds without errors, you should also be able to write the entire disk. grtz, Daan