From owner-freebsd-questions@freebsd.org Sat Jul 22 15:35:53 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B532DA4478 for ; Sat, 22 Jul 2017 15:35:53 +0000 (UTC) (envelope-from aimass@yabarana.com) Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF2E381A0F for ; Sat, 22 Jul 2017 15:35:52 +0000 (UTC) (envelope-from aimass@yabarana.com) Received: by mail-ua0-x22e.google.com with SMTP id k43so22051947uaf.3 for ; Sat, 22 Jul 2017 08:35:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yabarana-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZL1jJv27F0XONWlLANPh3qKehMTXVou7+tqmI812smk=; b=zzdmXGMqj4/1s/e3UN8WnGbl5D38wwpxufQYXiwIKoXoMuXpP32MiX/rGPk/MEher4 8PPFBTHvxgENPteg8+1j5c/CaeXRsHvb+jCfyMmQ8n+HpgEmxc9fglCp742xO1y/IUOA 5ZPKBNCB0P5NdAXsT4zgRVzytVnsSnUYxCodcZUfwvoZpW78ZD6z/IxVbVJEgrPUeXH0 LXiGTYZUndvcqt+qAd139vpbq814yhgDj9UjP77xVdCy/+IRN+dGSyVJqqJ3+HyPIGkN b35kTBqiJftXdYikhPIkZ6tl18eUsTOm8P4pm3lxvgwnjHfxxuooIZfPn/bOilaA7IBJ YYEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZL1jJv27F0XONWlLANPh3qKehMTXVou7+tqmI812smk=; b=tGDAygs1kHGz+Cii5pogSfsEUo7vyT08ke3LZ0HOf2Hr718lf1TADnd8Zc/yr+NYhR tnNV79ErkUUTqXVu6yFxLqe85ar/DJkcf00yGoHxl/6B4CxUgYmiC48wreOMe1UXex6K KhPpQECwzcJeqF3CwAQus8PKGCfHk7++LZgNJ3LO2t8hyLarzbot/a1DPAgLAf5Os8HY E2mImqnGYxWpbO/tn1Zd1BUzJnNcgRcx0ot3Sp4o/H4plKpxY7JdFpf1Bj/CklwIKIdp HofTThlScErfNXxIELlP5+uJm2kZIYFTgUF3XeRVTVrnMhtN+Dvobat2RN9+/yxeoHzg 5lrw== X-Gm-Message-State: AIVw112lPVkeJqIDSqPgQuLdHGSRUmlwIKBqPg3YP3cn08RdrZEJ6s2x xvUApvZaXGiOD+dYM+GeBLEa/YJWcfkn X-Received: by 10.176.25.45 with SMTP id v45mr6903826uag.16.1500737751570; Sat, 22 Jul 2017 08:35:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.147.133 with HTTP; Sat, 22 Jul 2017 08:35:51 -0700 (PDT) In-Reply-To: <398f92a2-e38a-05e9-89fa-8d7d53eb498d@FreeBSD.org> References: <398f92a2-e38a-05e9-89fa-8d7d53eb498d@FreeBSD.org> From: Alejandro Imass Date: Sat, 22 Jul 2017 11:35:51 -0400 Message-ID: Subject: Re: Upgrade from 10.1-RELEASE to 10.3-RELEASE went wrong, pls. help! To: Matthew Seaman Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jul 2017 15:35:53 -0000 On Sat, Jul 1, 2017 at 3:03 AM, Matthew Seaman wrote: > On 30/06/2017 18:17, Alejandro Imass wrote: >> Any idea what went wrong? I have upgraded FBSD since 6.x and never had >> it go so badly !! > > Not really. Clearly something went wrong with the process for executing > a binary, but quite what I couldn't say. The whole way an executable is > run hasn't changed significantly since the switch between a.out and elf > around 3.0-RELEASE, so it's not as if you've some half-implemented > change screwing things up. > > One of the problems with freebsd-update(8) is dealing with when things > go wrong. Thankfully this is a pretty rare occurrence, but even > something as trivial as running out of space in a partition in the > middle of an upgrade can leave you with an incomplete upgrade, and no > reasonable way of fixing it. > The data was intact and I have everything in Jails so it was easy to recover w/o a full restore from backup. I saved the original disk and took the opportunity upgrade the hard drives and a fresh install, so I just pulled the data from the old drive. I wonder if for some reason the upgrade process tried to install a 32 bit system over a 64 bit one, or something along those lines. I still have the old drive intact in case someone would like to explore this further and try to figure out what really happened and avoid for it to happen to someone else. Best, Alex