From owner-freebsd-questions Mon Jul 3 23:40:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id EF2EE37B58D for ; Mon, 3 Jul 2000 23:40:12 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id XAA31938; Mon, 3 Jul 2000 23:40:11 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id XAA37722; Mon, 3 Jul 2000 23:41:15 -0700 (PDT) (envelope-from john) Message-Id: <200007040641.XAA37722@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <39614608.303A5D6F@buckhorn.net> Date: Mon, 03 Jul 2000 23:41:15 -0700 (PDT) From: John Baldwin To: Bob Martin Subject: Re: install fails on 10.2 GB drive using 4.0 Cc: FreeBSD-questions@FreeBSD.ORG, "Kim J. Brand" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jul-00 Bob Martin wrote: > "Kim J. Brand" wrote: >> >> after selecting every default choice in the partitioning and slicing of a >> new 10.2 GB WD HD, the install failes with an error message saying it >> couldn't swap to /dev/ad0s1... >> >> i changed the hard drive to a smaller 6.4 GB drive and it works. >> >> i searched the archives and found some references to large hard drives in >> LBA mode. i didn't notice a selection for that in the setup. but what i >> found allowed me to believe it should work. >> >> is there an option i'm missing? >> >> thanks, >> >> kim > We just ran into the same problem. It has to be a magic number thing. If > you look at the diagnostic screen, you'll find that your system thinks > the drive size is astronomical. (I never did the math, but we are > talking 100s of gigs here.) That means the MBR has some wacky geometry in it. If you could boot into the install and use the live filesystem CD fixit option and then run fdisk on the drive in question (e.g., 'fdisk ad0'), the output could be rather helpful in figuring out where sysinstall is getting confused. > We found 2 work arounds. Load 3.x and upgrade, or manually correct the > disk label. > > We let the bios auto detect the drive, and used LBA mode. > > Bob -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message