From owner-freebsd-stable@freebsd.org Fri Jul 28 20:49:12 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 F30C9DCEA43 for ; Fri, 28 Jul 2017 20:49:11 +0000 (UTC) (envelope-from 0100015d8af5c5ca-71188b3f-2346-41c2-ba07-0a1265b5f583-000000@amazonses.com) Received: from a8-13.smtp-out.amazonses.com (a8-13.smtp-out.amazonses.com [54.240.8.13]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A47FC703BC for ; Fri, 28 Jul 2017 20:49:11 +0000 (UTC) (envelope-from 0100015d8af5c5ca-71188b3f-2346-41c2-ba07-0a1265b5f583-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ae7m2yrxjw65l2cqdpjxuucyrvy564tn; d=tarsnap.com; t=1501274949; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=wlw25V2dOm/1blNsGQJWoJEXdgSDZsGNZPo+hurn99c=; b=pn7KzkbcpwYiw7QJXQRAOe3GPfIP426ccxUf1eZ1HWheW0mlag1Y/jfhqhUwHoMI arMYysoNG030cgxNAsSPM52QFHETVs8epji0Zj1P5eEi42J32iq+hujGDlTjShkET01 3vn20rBEsDTqOBtGVy/GOPecvi71NzztE9HTUqyQ= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1501274949; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=wlw25V2dOm/1blNsGQJWoJEXdgSDZsGNZPo+hurn99c=; b=fjRO9fX+VYvgaOLhdvE4/5L+ahNe692q4uO4CfX4QIboE70v+YRIRLA0Og1l/RjY JlHYq9fSiEwlcKF77yvSOCbVduo30OkLwDbaVlE8KSkYCwEM0gxSzbMqjg7qJ+1jJlT Uguq105SQAEUNB+6s42G+ErHcyO2v2NCY07Ct8x8= Subject: Re: Upgrade to 11.1-RELEASE fails to boot on aws EC2. To: =?UTF-8?Q?Peter_Ankerst=c3=a5l?= , FreeBSD Stable References: From: Colin Percival Message-ID: <0100015d8af5c5ca-71188b3f-2346-41c2-ba07-0a1265b5f583-000000@email.amazonses.com> Date: Fri, 28 Jul 2017 20:49:09 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-SES-Outgoing: 2017.07.28-54.240.8.13 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES 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: Fri, 28 Jul 2017 20:49:12 -0000 On 07/28/17 03:41, Peter Ankerst�l wrote: > It seems that FreeBSD 11.1-RELEASE also breaks on EC2 in some cases. I had this problem before when upgrading to 11.0. This problem was noticed in the ERRATA: https://www.freebsd.org/releases/11.0R/errata.html#open-issues > and later said to have been resolved with a EN: https://www.freebsd.org/security/advisories/FreeBSD-EN-16:18.loader.asc > > Today I tried to upgrade a 11.0-RELEASE-p7 system to 11.1-RELEASE using the good old build world method as described in the handbook. But after reboot the machine hangs > in the loader. Do you know what version of FreeBSD this system was originally running? It may be that there are other oddities in the old partitioning which cause problems for the newer loader code. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid