From owner-freebsd-stable Thu Nov 30 15:32:33 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 5B29337B400; Thu, 30 Nov 2000 15:32:30 -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 eAUNWAC76927; Thu, 30 Nov 2000 15:32:10 -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: <3A26E040.5162159A@we.lc.ehu.es> Date: Thu, 30 Nov 2000 15:32:31 -0800 (PST) From: John Baldwin To: "Jose M. Alcaide" Subject: RE: The trouble with boot0 Cc: rnordier@FreeBSD.org, stable@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Nov-00 Jose M. Alcaide wrote: > I was succesfully using the "boot0" boot manager with an 8GB ATA disk > (in LBA mode) partitioned into two slices of 4GB (ad0s1 and ad0s2). > The second one starts after cylinder 1023, but this does not cause any > problems thanks to the boot0's "packet mode". Then, I decided to > delete ad0s1 and replace it by two slices, each one of 2GB; these > partitions were automatically named "ad0s1" and "ad0s3". In summary, > the 8GB disk ended up having this partition scheme: > > ad0s1 (2GB) > ad0s3 (2GB) > ad0s2 (4GB) > > I installed FreeBSD 4.2-RELEASE into ad0s3 and, after that, pressing > F3 for booting from ad0s3 only produces the famous beep. Note, however, > that I can still boot from ad0s2 (which also contains FreeBSD and begins > after cylinder 1023) and ad0s1. Only ad0s3 fails and I don't know why. > I think that boot0 does not like a 3rd slice physically placed before > the 2nd one. Is this a bug or a "feature"? > > The real disk geometry is: > > ad0: 8223MB [16708/16/63] at ata0-master UDMA33 > > The geometry used (from fdisk(8)) is: > > cylinders=3037 heads=88 sectors/track=63 (5544 blks/cyl) > > And "boot0cfg -v ad0" shows > > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0x06 720: 87:63 63 3997161 > 2 0x80 1023:255:63 0xa5 1023: 87:63 8415792 8421336 > 3 0x00 721: 0: 1 0xa5 1023: 87:63 3997224 4418568 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... > version=1.1 drive=0x80 mask=0xf ticks=182 > options=packet,noupdate,nosetdrv > default_selection=F2 (Slice 2) > > Cheers, > -- JMA -- 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