Date: Sat, 11 Nov 2017 00:46:59 -0800 From: Doug Hardie <bc979@lafn.org> To: Polytropon <freebsd@edvax.de> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Upgrade old System Message-ID: <A2B4E9EC-9B0E-4FC0-891A-7C402C8DCE87@mail.sermon-archive.info> In-Reply-To: <20171111093555.a28a5692.freebsd@edvax.de> References: <BB1D7DC1-A988-4911-97E0-82C95B0A77C2@mail.sermon-archive.info> <20171111093555.a28a5692.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 11 November 2017, at 00:35, Polytropon <freebsd@edvax.de> wrote: > > On Sat, 11 Nov 2017 00:16:35 -0800, Doug Hardie wrote: >> I have a remote host that has not been on or available for several years. It just came back up and I need to upgrade it. >> >> FreeBSD waldo.remotesupportservicesllc.com 8.2-RELEASE-p3 FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:07:27 UTC 2011 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 >> >> >> Freebsd-update does not work: >> >> waldo# freebsd-update upgrade -r 11.1-RELEASE >> Looking up update.FreeBSD.org mirrors... none found. >> Fetching metadata signature for 8.2-RELEASE from update.FreeBSD.org... failed. >> No mirrors remaining, giving up. >> waldo# freebsd-update fetch >> Looking up update.FreeBSD.org mirrors... none found. >> Fetching metadata signature for 8.2-RELEASE from update.FreeBSD.org... failed. >> No mirrors remaining, giving up. >> >> Is there a way to make that work? > > For such a high delta (8.2 -> 11.1), I'd say that a re-installation > from scratch is perhaps the easier way to go. Depending on how this > particular system can be accessed, preparing tarballs could be an > option, or remote-booting an installation media. While freebsd-update > was already available on 8.2, it probably cannot directly update to > 11.1 as there are way too many architectural changes on the way. > > > > PS. > FreeBSD 8.2-STABLE #1: Wed Aug 24 10:25:44 CEST 2011 :-) Unfortunately, re-installation is not possible. Its just not accessible except via ssh. However, I found the problem. DNS was not configured properly. Now I am able to at least start the upgrade process. I will jump to 9.3 first. However, I have to go and fix the issue with the failed integrity check first. Fortunately I saved the patch for that. Now I just have to find it ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A2B4E9EC-9B0E-4FC0-891A-7C402C8DCE87>