fyi: snap from 080304 will not boot
freebsd at jdc.parodius.com
Tue Aug 3 11:47:20 PDT 2004
Applicable threads about this problem:
I believe there to still be a problem with boot1/2 which *wasn't* taken
care of in the committed fix. Seems to depend on the system though...
A workaround is to pull the bootstraps off of a 5.2.1-RELEASE machine and
use those. For those who don't have access to older straps, I've put
5.2.1-RELEASE's /boot/boot up here:
You'll want to download the applicable strap and apply it such (assuming
disk ad0 and slice s1):
# disklabel -B -b /tmp/5.2.1-RELEASE__boot ad0s1
The boot0 strap seems to work; boot1 or boot2 seems to be the problem.
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. |
On Tue, Aug 03, 2004 at 11:21:54AM -0700, Doug White wrote:
> On Tue, 3 Aug 2004, Kim Culhan wrote:
> > Greetings-
> > Just an fyi here.. The latest snap, 080304, from
> > snapshots.se.FreeBSD.org did not install a bootable system here.
> This looks like the boot2 breakage. I think a fix was committed not too
> long ago and its possible the snapshot server hadn't picked it up in time.
> You might try tomorrow's.
> > Hitting enter or letting it time-out at:
> > F1 FreeBSD
> > returns
> > invalid partition
> > no /boot/loader
> > FreeBSD/i386 boot
> > default: 0:ad(0,c)/kernel
> Doug White | FreeBSD: The Power to Serve
> dwhite at gumbysoft.com | www.FreeBSD.org
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current