From owner-freebsd-questions@FreeBSD.ORG Tue Nov 20 22:28:50 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E612F8C8 for ; Tue, 20 Nov 2012 22:28:50 +0000 (UTC) (envelope-from ah@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id 81F088FC16 for ; Tue, 20 Nov 2012 22:28:50 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id qAKMSg1w057474; Tue, 20 Nov 2012 15:28:42 -0700 (MST) (envelope-from ah@dreamchaser.org) Message-ID: <50AC041A.7050607@dreamchaser.org> Date: Tue, 20 Nov 2012 15:28:42 -0700 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121116 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd@johnea.net Subject: Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3 References: <50ABE97B.5030408@johnea.net> In-Reply-To: <50ABE97B.5030408@johnea.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Tue, 20 Nov 2012 15:28:43 -0700 (MST) Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 22:28:51 -0000 On 11/20/12 13:34, freebsd@johnea.net wrote: > > Hello, > > I recently installed a 9.1-RC2 system using gmirror with MBR, and swap in first bsdlabel. > > orsbackup# gpart show > => 63 3907029104 mirror/gm0 MBR (1.8T) > 63 63 - free - (31k) > 126 3907028979 1 freebsd [active] (1.8T) > 3907029105 62 - free - (31k) > > => 0 3907028979 mirror/gm0s1 BSD (1.8T) > 0 2 - free - (1.0k) > 2 16777216 1 freebsd-swap (8.0G) > 16777218 3890251760 2 freebsd-ufs (1.8T) > 3907028978 1 - free - (512B) > > The drive was setup with the following commands: > > orsbackup# gpart create -s MBR mirror/gm0 > mirror/gm0 created > orsbackup# gpart add -t freebsd -a 4k mirror/gm0 > # ignored "mirror/gm0s1 added, but partition is not aligned on 4096 bytes" > # create the bsdlabel partitions in slice 1 (s1) > orsbackup# gpart create -s BSD mirror/gm0s1 > orsbackup# gpart add -t freebsd-swap -a 4k -s 8g mirror/gm0s1 > orsbackup# gpart add -t freebsd-ufs -a 4k mirror/gm0s1 > # put bootcode on the MBR and mark the first slice active > orsbackup# gpart bootcode -b /boot/mbr mirror/gm0 > orsbackup# gpart set -a active -i 1 mirror/gm0 > # put bootcode on the bsdlabel > orsbackup# gpart bootcode -b /boot/boot mirror/gm0s1 > > > The system rebooted several times without issue. This system is a testbed for 9.1 and is not yet deployed as a production server. > > I thought I'd update to 9.1-RC3, so I ran: > > freebsd-update upgrade -r 9.1-RC3 > freebsd-update install > reboot > > The system won't boot and complains about: > > "Not UFS" "No ada0" "No boot" > > Before I charge ahead with reissuing the gpart bootcode commands I thought I'd: > > a) make others aware there may be issues in freebsd-update with the 9.1 release candidates > > b) ask about the best way to resolve this bootloader issue. > > Thanks you for any pointers in resolving this bootloader issue! > > johnea Not sure, but this might apply: The freebsd-update tool is used to fetch, install, and rollback binary updates to the FreeBSD base system. Note that updates are only available if they are being built for the FreeBSD release and architecture being used; in particular, the FreeBSD Security Team only builds updates for releases shipped in binary form by the FreeBSD Release Engineering Team, e.g., FreeBSD 7.3-RELEASE and FreeBSD 8.0-RELEASE, but not FreeBSD 6.3-STABLE or FreeBSD 9.0-CURRENT. Seems like it isn't supposed to work for 9.1-RC2