From owner-freebsd-stable Fri Dec 1 7:48:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ULTRASW (unknown [204.17.51.7]) by hub.freebsd.org (Postfix) with ESMTP id 989F237B400 for ; Fri, 1 Dec 2000 07:48:50 -0800 (PST) Received: from crazyhorse (unverified [207.138.88.126]) by mail.ULTRASW (Vircom SMTPRS 4.2.181) with SMTP id ; Fri, 1 Dec 2000 08:43:51 -0700 Message-Id: <3.0.5.32.20001201084345.009ad100@mail.ultrasw.com> X-Sender: paschal@mail.ultrasw.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 01 Dec 2000 08:43:45 To: Robert Nordier From: Richard Paschal Subject: Re: The trouble with boot0 Cc: stable@FreeBSD.ORG In-Reply-To: <200012011457.eB1EvDQ00734@nordier.com> References: <3A27AF02.423BED40@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same problems with 3.1 and 4.0. In both cases, I installed from CD obtained from Walnut Creek. I was getting the error message "Invalid Partition Table" from the NT boot sector. It seems that FreeBSD doesn't co-exist with other OS as well as might be thought. As it turns out, all that needed to be done was sort the table in increasing order by, I believe, beginning cylinder (apologies, this was months ago and its no longer all that clear). I did it manually using something called "Norton Utilities Disk Edit" on an MSDOS diskette and it booted fine afterward. Regards, Richard At 04:57 PM 12/1/00 +0200, you wrote: >Jose M. Alcaide wrote: > >> If this a geometry problem, I cannot understand why boot0 cannot >> boot from ad0s3 while there are no problems for booting from >> ad0s2, which is placed after ad0s3 and beyond the cylinder 1023. > >Can you try the -current version of boot0? You can pick up both >source and binary files at > > http://www.freebsd.org/~rnordier/download/boot0-latest.tar.gz > >Be sure to specifically enable packet support when installing it: > > boot0cfg -Bv -b $PATH_TO_BINARY -o packet ad0 > >The problem may be that the 4.2 boot0 uses the CHS interface where >it can, and the packet interface otherwise. The -current boot0 >(and the old boot0) will always use one interface or the other, >though. I think that could account for the problem you're having. > >> I am more interested on an explanation for this problem than on >> finding the solution. I found this problem while doing a >> demo for the students of the installation procedure of FreeBSD, >> so that I would like to be able to explain clearly the reason of the >> boot failure to them. > >Understood. If the -current boot0 doesn't work, I'd suggest you >send along the following data and I'll think about it some more: > > dd if=/dev/ad0 bs=512 count=3 >foo0 > dd if=/dev/ad0 bs=512 skip=3997224 count=17 >foo1 > dd if=/dev/ad0 bs=512 skip=8415792 count=17 >foo2 > >-- >Robert Nordier > >rnordier@nordier.com >rnordier@FreeBSD.org > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message