From owner-freebsd-hackers Wed Mar 1 16: 7:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arthur.intraceptives.com.au (arthur.intraceptives.com.au [203.22.72.70]) by hub.freebsd.org (Postfix) with SMTP id 9F83D37BDDA for ; Wed, 1 Mar 2000 16:07:31 -0800 (PST) (envelope-from wwlists@intraceptives.com.au) Received: (qmail 7356 invoked from network); 2 Mar 2000 00:07:29 -0000 Received: from wks-pc1.intraceptives.com.au (HELO waddy) (203.22.72.32) by arthur.intraceptives.com.au with SMTP; 2 Mar 2000 00:07:29 -0000 Message-Id: <4.2.1.20000302103756.05601b50@arthur.intraceptives.com.au> X-Sender: wwlists@arthur.intraceptives.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 Date: Thu, 02 Mar 2000 11:07:28 +1100 To: freebsd-hackers@FreeBSD.ORG From: Warren Welch Subject: fdisk / disklabel issues... In-Reply-To: References: <200002282312.PAA15070@enginet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've got a problem with a couple of machines... The first time I saw the problem, I thought it was my hardware, but now I've encountered the problem on three different systems, all with different motherboards, and hard disks. The only think in common, is that with all of them I'm working with FreeBSD 3.4, and that all the disks are LARGER than 12Gb IDE's. One of the things that I notice are that the size of the disk that gets reported by the BIOS, and FreeBSD are totally different... As an example, the following system reports:- wdc0: unit 0 (wd0): wd0: 12419MB (25434228 sectors), 25232 cyls, 16 heads, 63 S/T, 512 B/S from dmesg yet, when I get the system BIOS to probe the disk, it reports:- 24062 cyls 16 heads 63 sects. As you can see, FreeBSD recognizes the disk as larger than what it actually is. I've found that if I partition the disk using the entire disk (fdisk -e wd0), then the last partition on the disk (the one that uses the last sectors on the disk) won't be newfs'd... It's not at all good. sysinstall also seems to have a problem with allowing you to set the geometry. I'd expect that if I set the geometry to what the BIOS detects, and then say to use the entire disk, that it would use that defined geometry. It doesn't... The moment you say to use the entire disk, ('A', No), it resets the geometry to something it likes. If I calculate the number of sectors manually (to what the bios detects), and then create a slice all things work fine within that slice. I think there is something wrong with the way that FreeBSD is detecting the size of the disk. (Interigating the disk that is...) So far I've only had this problem with IDE disks. Warren wwelch@intraceptives.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message