Upgrade from 10.1-RELEASE to 10.3-RELEASE went wrong, pls. help!

Alejandro Imass aimass at yabarana.com
Sat Jul 22 15:35:53 UTC 2017

On Sat, Jul 1, 2017 at 3:03 AM, Matthew Seaman <matthew at freebsd.org> 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.


More information about the freebsd-questions mailing list