From owner-freebsd-questions@FreeBSD.ORG Sat Oct 5 20:00:26 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B5D1DFC7 for ; Sat, 5 Oct 2013 20:00:26 +0000 (UTC) (envelope-from efeldhusen.lists@gmail.com) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 75BF1232C for ; Sat, 5 Oct 2013 20:00:26 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id p19so3782398qcv.11 for ; Sat, 05 Oct 2013 13:00:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Mw2+uklm9m8EPt/WmJKb1K/Gnwv5ug/5qgtXKDY6GNs=; b=xXPqjrZShaB1mjRFNuSQDeJtqxzqAcsQWmDkUONLRUAYDsyxV+gqqLXAn26xFchLE6 JtqIEsCoqW3XTTrix7PzS/ZMw4zYOX+Ob+A3IkyBiov1yHiOLW1sT0JALaNok74N+tX2 jdYIfdJP36X1C2lZPmvrAJvgt7bdhuMJtejJfopDw4hzvQO2E8AIQNGDY84vudq22I8Q adojyxHzLZI6yyEEJFEATh5BlYQXA2cR7DnczP+kwxEQ81di9YdOkb64SAYBpgT3EAQ3 aBIVFfoMiI+610lrXNzkp9E96wu0SB+o9nQKAcGhkM0lwI32odlCNhiqMo7nOi8PKmux sjpA== MIME-Version: 1.0 X-Received: by 10.49.30.227 with SMTP id v3mr348897qeh.92.1381003225641; Sat, 05 Oct 2013 13:00:25 -0700 (PDT) Received: by 10.49.75.231 with HTTP; Sat, 5 Oct 2013 13:00:25 -0700 (PDT) In-Reply-To: <525069AD.7040505@FreeBSD.org> References: <525069AD.7040505@FreeBSD.org> Date: Sat, 5 Oct 2013 16:00:25 -0400 Message-ID: Subject: Re: Problem completing a 9.1 release to 9.2 release upgrade From: Eric Feldhusen To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Sat, 05 Oct 2013 20:00:26 -0000 Ah, yes, when this particular box was a 9.0-release, I had compiled a custom kernel to enable ipsec. When I check the strings, it's a 9.1 release kernel. I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? Thanks for the help. Eric On Sat, Oct 5, 2013 at 3:34 PM, Matthew Seaman wrote: > On 05/10/2013 20:11, Eric Feldhusen wrote: > > I have a server that was/is running 9.1 release that I tried to upgrade > to > > 9.2 release. I missed the step of updating to the latest 9.1 patches by > > doing > > > > freebsd-update fetch > > freebsd-update install > > > > I went right to > > > > freebsd-update upgrade -r 9.2-RELEASE > > freebsd-update install > > > > rebooot > > > > freebsd-update install > > > > reboot again > > > > But my system still comes up as 9.1 release. > > > > Any suggestions on the steps to fix my goof? > > Did you replace the generic kernel from 9.1-RELEASE with something you > compiled yourself? If so, you may well have caused freebsd-update to > ignore any modifications to the kernel. > > You can fix that by re-compiling a kernel using the 9.2-RELEASE sources > and basically the same kernel configuration as for 9.1 (you will need to > check for 9.2 related differences to the configuration, but these are > likely to be pretty minor or not needed at all.) > > If you aren't using a customized kernel, then has the kernel in the > standard location on your system actually been updated? You can tell if > it's a 9.2 kernel by running strings(1) against the kernel binary, like so: > > # strings /boot/kernel/kernel | grep RELEASE > > If that's clearly a 9.2 kernel, then are you actually booting up from a > different kernel somewhere else on your system? First of all, are > there any other copies of FreeBSD kernels around anywhere -- on > memsticks, or on split mirrors perhaps? You may need to fiddle with the > bios settings or interrupt the boot sequence and type things directly at > the loader if so. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. > PGP: http://www.infracaninophile.co.uk/pgpkey > > >