Date: Tue, 12 May 2009 14:45:26 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-embedded@freebsd.org Subject: Re: nanobsd boot slice selection does not work Message-ID: <200905121445.27090.jhb@freebsd.org> In-Reply-To: <20090512171555.GA4985@psconsult.nl> References: <200904201535.21191.nick@van-laarhoven.org> <200905121008.19196.jhb@freebsd.org> <20090512171555.GA4985@psconsult.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 12 May 2009 1:15:55 pm Paul Schenkeveld wrote: > After rebooting, the kernel in /dev/ad0s2a is loaded (verified by > uname -a, both slices have a kernel with a different timestamp) and: > > # boot0cfg -v ad0 > # flag start chs type end chs offset size > 1 0x00 0: 1: 1 0xa5 333: 14:48 48 240432 > 2 0x80 334: 1: 1 0xa5 667: 14:48 240528 240432 > 3 0x00 668: 0: 1 0xa5 670: 14:48 480960 2160 > 4 0x00 671: 0: 1 0xa5 693: 14:48 483120 16560 > > version=1.0 drive=0x80 mask=0x3 ticks=182 > options=packet,update,nosetdrv > default_selection=F2 (Slice 2) > # > > The active marker has moved from slice 1 to slice 2, most likely this > was done by boot0 but I cannot verify this easily. Yes, it is done by boot0. > Trying the same on FB7.2 will show that default_selection has changed > and slice 1 still marked active in the MBR after 'boot0cfg -v -s 2 ad0' > just like on FB7.1 but during the reboot the kernel from slice 1 gets > loaded and ad0s1a becomes the root partition. Ok, so can you verify if 'update' is enabled for boot0 in the 7.2 case? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905121445.27090.jhb>