From owner-freebsd-questions@freebsd.org Sat Nov 11 09:54:28 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 62471E66DCA for ; Sat, 11 Nov 2017 09:54:28 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay13.qsc.de (mailrelay13.qsc.de [212.99.187.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDCC97B98C for ; Sat, 11 Nov 2017 09:54:27 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay13.qsc.de; Sat, 11 Nov 2017 10:54:18 +0100 Received: from r56.edvax.de (port-92-195-23-159.dynamic.qsc.de [92.195.23.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id A9A713CBF9; Sat, 11 Nov 2017 10:54:17 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id vAB9sGrv002017; Sat, 11 Nov 2017 10:54:16 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Sat, 11 Nov 2017 10:54:16 +0100 From: Polytropon To: Doug Hardie Cc: "freebsd-questions@freebsd.org" Subject: Re: Upgrade old System Message-Id: <20171111105416.9c74b061.freebsd@edvax.de> In-Reply-To: References: <20171111093555.a28a5692.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay13.qsc.de with 2A847683472 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1508 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, 11 Nov 2017 09:54:28 -0000 On Sat, 11 Nov 2017 00:46:59 -0800, Doug Hardie wrote: > > On 11 November 2017, at 00:35, Polytropon 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. Okay, this is limiting your options. Maybe you can use source update, but not directly from 8.2 to 11.1, but instead to 9.0, 10.0, 11.0; it's possible that you also need to upgrade each of the major versions to the maximum minor version first, then make the switch to the next major version. Another option is to prepare tarballs from a verified (!) new system version, scp them over, and then use them to overwrite the existing system binaries. This system has to be preconfigured so when you reboot, all neccessary settings are already in place. > 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 ;-) Yes; from 9.2, you should be able to get at least to 10.0, and then to 11.1 using freebsd-update directly. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...