From owner-freebsd-stable@freebsd.org Sun Oct 8 22:34:22 2017 Return-Path: Delivered-To: freebsd-stable@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 19791E41858 for ; Sun, 8 Oct 2017 22:34:22 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from mail.truespeed.com (mail.truespeed.com [31.210.26.210]) by mx1.freebsd.org (Postfix) with ESMTP id 5342A82954; Sun, 8 Oct 2017 22:34:20 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from unnamed-75.karthauser.co.uk (unnamed-75.karthauser.co.uk [90.155.77.75]) (Authenticated sender: joe@truespeed.com) by mail.truespeed.com (Postfix) with ESMTPSA id 2200A292E41; Sun, 8 Oct 2017 22:34:19 +0000 (UTC) Subject: Re: 10.4 release - is the binary update corrupt? Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: text/plain; charset=utf-8 From: Dr Josef Karthauser In-Reply-To: <17d76f7d-4b9a-6a3e-ffae-ee3c2ffd27b0@FreeBSD.org> Date: Sun, 8 Oct 2017 23:34:18 +0100 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <44BD1E61-E17A-4AD0-8E19-415CDC21B0A2@tao.org.uk> References: <201710081227.35629.dr.klepp@gmx.at> <17d76f7d-4b9a-6a3e-ffae-ee3c2ffd27b0@FreeBSD.org> To: Matthew Seaman X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 08 Oct 2017 22:34:22 -0000 > On 8 Oct 2017, at 12:04, Matthew Seaman wrote: >=20 >> Am Sonntag, 8. Oktober 2017 schrieb Dr Josef Karthauser: >>> Hi, >>>=20 >>> I=E2=80=99m having trouble upgrading a 10.3 machine to 10.4: looks = like something is corrupt: >>>=20 >>> Fetching metadata signature for 10.4-RELEASE from = update4.freebsd.org... done. >>> Fetching metadata index... done. >>> Fetching 1 metadata patches. done. >>> Applying metadata patches... done. >>> Fetching 1 metadata files... done. >>> Inspecting system... done. >>> Fetching files from 10.3-RELEASE for merging... done. >>> Preparing to download files... done. >>> Fetching 38573 = patches.....10....20....30....40....50....60....70....80....90....100....1= 10....120....130....140=E2=80=A6 >>> [cut] >>> Applying patches... done. >>> Fetching 9266 files... >>> gunzip: (stdin): unexpected end of file >>> efb4027db1ae440353955aa1bcfc9c69d1cafbdb53b4bfc6584d64b1e1bfd209 has = incorrect hash. >>>=20 >>> Has anyone else also seen this? >>>=20 >=20 > With luck you've only got a problem with that one patch file, but if = the > corruption is much wider, then moving aside your existing > /var/db/freebsd-update and starting again from scratch is probably a > good idea. >=20 > If you consistently get broken patch files from whichever of the = update > servers you get directed to, that probably means that update server > needs some TLC. Please do report that to clusteradm@... While waiting > for them to sort out the problems, you can play with the 'ServerName' > parameter in /etc/freebsd-update.conf to point yourself towards some > other server. I=E2=80=99ve upgrade from 10.1 today to 10.2, then 10.3; and only had = this problem moving to 10.4. I can=E2=80=99t see how a file could have become corrupt = in transit - TCP protects against that kind of thing. :) I=E2=80=99ll try moving the damaged file aside and see if that fixes = anything and report back. Cheers, Joe=