From owner-freebsd-current@freebsd.org Fri Mar 3 05:14:33 2017 Return-Path: Delivered-To: freebsd-current@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 191C6CF607B for ; Fri, 3 Mar 2017 05:14:33 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC9C11E8F for ; Fri, 3 Mar 2017 05:14:32 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v235G65L082993 for ; Thu, 2 Mar 2017 21:16:12 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: From: "Chris H" Subject: Re: Boot failure - svn up from this morning Date: Thu, 02 Mar 2017 21:16:12 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 05:14:33 -0000 On Thu, 2 Mar 2017 21:56:38 -0500 (EST) AN wrote > Hi: > > I'm having a major problem after updating a 12-current machine today. > After buildworld/kernel/install cycle on reboot I'm getting the following > failure: > > "/boot/kernel/kernel text=0xb7716f data=0x100548+0x398358 > elf64_loadimage: read failed > can't load file '/boot/kernel/kernel': input/output error > can't load file '/boot/kernel/kernel': input/output error > > OK boot kernel.old > elf64_loadimage: read failed > can't load file '/boot/kernel.old/kernel': input/output error > can't load file '/boot/kernel.old/kernel': input/output error" > > I have never experienced this failure before, and don't know how to > proceed. Any help recovering from this would be greatly appreciated. > Thanks in advance. I don't suppose you could post the output of uname -a and maybe a copy of dmesg(8) could you? --Chris