From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 08:23:40 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B90D516A468 for ; Sun, 11 Nov 2007 08:23:40 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 2735A13C4B5 for ; Sun, 11 Nov 2007 08:23:39 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 11 Nov 2007 08:23:30 -0000 Received: from nat-wh-1.rz.uni-karlsruhe.de (EHLO mobileKamikaze.norad) [129.13.72.169] by mail.gmx.net (mp027) with SMTP; 11 Nov 2007 09:23:30 +0100 X-Authenticated: #5465401 X-Provags-ID: V01U2FsdGVkX1/Csy4ySY3C/8AFn2+RKuRrNfl6h7B3hsktQHa+/d H2SCGX7eArxY0s Message-ID: <4736BC01.2000800@gmx.de> Date: Sun, 11 Nov 2007 09:23:29 +0100 From: "[LoN]Kamikaze" User-Agent: Thunderbird 2.0.0.6 (X11/20071101) MIME-Version: 1.0 To: Clint Olsen References: <20071102095628.GA796@0lsen.net> <472AF94B.1020600@gmx.de> <20071111043931.GA1460@0lsen.net> In-Reply-To: <20071111043931.GA1460@0lsen.net> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: Ok, so now what? Binary upgrade to 6.2-RELEASE fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2007 08:23:40 -0000 Clint Olsen wrote: > On Nov 02, [LoN]Kamikaze wrote: >> I think you might have no choice but to omit the reboots, because the >> world contains lots of stuff that has to do with the kernel (like >> mounting). >> >> So just go into single user mode and do the usual stuff: >> # make installkernel >> # mergemaster -p >> # make installworld >> # mergemaster >> # shutdown -r now >> >> and pray to your deity of choice. >> >> If the reason for your problem is something else however you're stuck >> with a system that can not run with your old kernel. So better backup >> before you try. > > I attempted to just do a binary upgrade, assuming that I botched the source > upgrade somehow. After installing FreeBSD 6.2-RELEASE, I was left with a > system that would not boot (similar errors on boot as before). Reverting > the kernel of course was of limited help because userland was all expecting > 6.2. So, I had a couple of tarballs from my last backup and I attempted to > bandage up / and /usr and was able to resurrect my 5.5-STABLE image. > > This is f'n scary. I've never had this much trouble upgrading a system > before. Does anyone have any idea what remnant could be remaining after a > binary upgrade that would keep it from booting yet I can boot from the > 6.2-RELEASE iso's just fine? I am very apprehensive to do a newfs and wipe > the drives now that I've failed both source and binary upgrade paths. > > -Clint That's strange, I've gone right from 5.3 through to RELENG_7 without ever doing the reboots during the install process (I know that's not recommended) and I never ran into trouble. Did you accidently turn off compat6x in the kernel before you built? Did your remember to install the misc/compat6x port?