From owner-freebsd-stable Thu Nov 30 16: 2:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2703037B400; Thu, 30 Nov 2000 16:02:42 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB102LC77948; Thu, 30 Nov 2000 16:02:21 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: 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: <3A26E955.C103AD88@we.lc.ehu.es> Date: Thu, 30 Nov 2000 16:02:42 -0800 (PST) From: John Baldwin To: "Jose M. Alcaide" Subject: Re: The trouble with boot0 Cc: stable@FreeBSD.org, rnordier@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Nov-00 Jose M. Alcaide wrote: > John Baldwin wrote: >> >> Look at the geometry in your BIOS setup and make sure that the geometry >> fdisk >> uses matches the geometry in your BIOS exactly. If it doesn't, then you >> will >> have to re-partition with the correct geometry I'm afraid. Or you can try >> lying to your BIOS and telling it that your disk's geometry is 3037/88/63, >> but >> I doubt that that will work... >> > > I'll try that tomorrow at work. But, if this is a geometry problem, > why can I boot from ad0s1 and ad0s2, but not from ad0s3? Typically > the geometry problems prevent booting from any slice. In addition, > boot0 is working in "packet mode". packet mode doesn't use the starting C/H/S, it uses the starting offset. Also, as long as the you have the sectors right, ad0s1's starting C/H/S is ok. However, if you have the cylinders and/or heads wrong, then the C/H/S for ad0s3 is bogus. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message