From owner-freebsd-current@freebsd.org Thu Nov 29 15:01:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B7B7113FCCA; Thu, 29 Nov 2018 15:01:34 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 949066F561; Thu, 29 Nov 2018 15:01:33 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 435LMH1dpCzCkZ; Thu, 29 Nov 2018 16:01:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received:received:received; s=jakla4; t= 1543503682; x=1546095683; bh=miBIGgUC7lxC/C9O1XQlpUPwXcTtdriIGwF KKjGOQK4=; b=opmV6RRjBQUVMr4wc2wwrl0fp333IqrnWYdkAPakPGcHPG3Ei6z FZSIUCqCtllPorIvU1u+rbiuV1T8GzUKt4Z6OMfIufdSB9AICNmcDXUbrOyKKRQj FgrwrDzP5Yl7XnJHL1L16GHV9k0VBDyBqq6GACbyEHXL6fFCWv8sSec8= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id gD_VksAB55be; Thu, 29 Nov 2018 16:01:22 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 435LM61TNnzCkT; Thu, 29 Nov 2018 16:01:21 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 435LM55f3nzBs; Thu, 29 Nov 2018 16:01:21 +0100 (CET) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by nabiralnik.ijs.si with HTTP (HTTP/1.1 POST); Thu, 29 Nov 2018 16:01:21 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 29 Nov 2018 16:01:21 +0100 From: Mark Martinec To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 Organization: Jozef Stefan Institute Message-ID: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.1 X-Rspamd-Queue-Id: 949066F561 X-Spamd-Result: default: False [-3.86 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; R_DKIM_ALLOW(-0.20)[ijs.si]; RCVD_COUNT_FIVE(0.00)[6]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:1470:ff80::25]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; HAS_ORG_HEADER(0.00)[]; IP_SCORE(0.00)[country: SI(0.00)]; DKIM_TRACE(0.00)[ijs.si:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[ijs.si,none]; MX_GOOD(-0.01)[mail4.ijs.si,mail.ijs.si]; NEURAL_HAM_SHORT(-0.76)[-0.758,0]; RCVD_IN_DNSWL_LOW(-0.10)[5.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.f.f.0.7.4.1.1.0.0.2.list.dnswl.org : 127.0.11.1]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:2107, ipnet:2001:1470::/32, country:SI]; MID_RHS_MATCH_FROM(0.00)[]; TAGGED_FROM(0.00)[freebsd] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 29 Nov 2018 15:01:34 -0000 After successfully upgraded three hosts from 11.2-p4 to 12.0-RC2 (amd64, zfs, bios), I tried my luck with one of our production hosts, and ended up with a stuck loader after rebooting with a new kernel (after the first stage of upgrade). These were the steps, and all went smoothly and normally until a reboot: freebsd-update upgrade -r 12.0-RC2 freebsd-update install shutdown -r now While booting, the 'BTX loader' comes up, lists the BIOS drives, then the spinner below the list comes up and begins turning, stuttering, and after a couple of seconds it grinds to a standstill and nothing happens afterwards. At this point the ZFS and the bootstrap loader is supposed to come up, but it doesn't. This host has too zfs pools, the system pool consists of two SSDs in a zfs mirror (also holding a freebsd-boot partition each), the other pool is a raidz2 with six JBOD disks on an LSI controller. The gptzfsboot in both freebsd-boot partitions is fresh from 11.2, both zpool versions are up-to-date with 11.2. The 'zpool status -v' is happy with both pools. After rebooting from an USB drive and reverting the /boot directory to a previous version, the machine comes up normally again with the 11.2-RELEASE-p4. I found a file init.core in the / directory, slightly predating the last reboot with a salvaged system - although it was probably not a cause of the problem, but a consequence of the rescue operation. It is unfortunate that this is a production host, so I can't play much with it. One or two more quick experiments I can probably afford, but not much more. Should I just first wait for the official 12.0 release? Should I try booting with a 12.0 on USB and try to import pools? Suggestions welcome. Now that the /boot has been manually restored to the 11.2 state, A SECOND QUESTION is about freebsd-update, which still thinks we are in the middle of an upgrade procedure. Trying now to just update the 11.2-RELEASE-p4 to 11.2-RELEASE-p5, the fetch complains: # uname -a FreeBSD xxx 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 # # freebsd-version 11.2-RELEASE-p4 # # freebsd-update fetch src component not installed, skipped You have a partially completed upgrade pending Run '/usr/sbin/freebsd-update install' first. Run '/usr/sbin/freebsd-update fetch -F' to proceed anyway. So what is the right way to get rid of all traces of the unsuccessful upgrade, and let freebsd-update believe we are cleanly at 11.2-p4 ? Removing /var/db/freebsd-update did not help. Mark