Date: Sat, 1 Dec 2018 16:50:56 -0500 (EST) From: CenturyLink Customer <cksalexander@q.com> To: freebsd-stable <freebsd-stable@FreeBSD.org> Cc: cksalexander <cksalexander@q.com> Subject: FreeBSD-12.0-RC3-i386-disc1.iso does not boot Message-ID: <1744424063.31566579.1543701056566.JavaMail.zimbra@q.com>
next in thread | raw e-mail | index | archive | help
Hello all:Sorry, this old Pentium 4 refurbished test machine has been obstinate during ALPHA, BETA, and now RC.I had a workaround using the BTX bootloader from ALPHA8 and pasted it into BETA3; meanwhile,remastering the .iso disk afterwards. I was able to boot that, and setup a minimal system, as test.I don't know if I can devote much more testing; but I thought you all would like to hear feedback anyway.BTW, I have a Thinkpad laptop running 11.2-RELEASE-p5 for my main system; works very well, THX.Very Sincerely Yours,cksalexander@q.com From owner-freebsd-stable@freebsd.org Sat Dec 1 23:11:13 2018 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@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 2C2C6132B1BE; Sat, 1 Dec 2018 23:11:13 +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 0B99B7847D; Sat, 1 Dec 2018 23:11:11 +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 436n7K58JPzZFF; Sun, 2 Dec 2018 00:11:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla4; t=1543705866; x=1546297867; bh=Duc bRKcENv+/617GHw+wfEPFYLW1v6OSY1/QNJwKE4k=; b=YfzE7f1CZE5MkzQtO6e kqZaQVfjJdtIJZbYrcImNksAzPhtf/Oxy75Hj4cxLtmOhSD0iyCDxbz2lpmaCrWY Tal5uPYmXRv8wymw0VAtXSseMWVEzfF8n3UvbpkDYgwvySrm2XIeHlZ7+FmPRyMD K0XHO/ZzmgDxJ83Qm910YUtA= 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 fal9GYEdcwId; Sun, 2 Dec 2018 00:11:06 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 436n7F3rj8zZFD; Sun, 2 Dec 2018 00:11:05 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 436n7F0kJtzMF; Sun, 2 Dec 2018 00:11:05 +0100 (CET) Received: from sleepy.ijs.si (2001:1470:ff80:e001::76) by webmail.ijs.si with HTTP (HTTP/1.1 POST); Sun, 02 Dec 2018 00:11:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sun, 02 Dec 2018 00:11:05 +0100 From: Mark Martinec <Mark.Martinec+freebsd@ijs.si> To: Toomas Soome <tsoome@me.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 Organization: Jozef Stefan Institute In-Reply-To: <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> References: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> Message-ID: <f2737ffb236d39761767aa10a603c084@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.1 X-Rspamd-Queue-Id: 0B99B7847D X-Spamd-Result: default: False [-2.88 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[ijs.si]; RCVD_COUNT_FIVE(0.00)[6]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2001:1470:ff80::25]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_SHORT(0.12)[0.123,0]; TO_DN_SOME(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[ijs.si:+]; DMARC_POLICY_ALLOW(-0.50)[ijs.si,none]; RCVD_IN_DNSWL_NONE(0.00)[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.0]; MX_GOOD(-0.01)[mail4.ijs.si,mail.ijs.si]; FREEMAIL_TO(0.00)[me.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(0.00)[country: SI(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-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 01 Dec 2018 23:11:13 -0000 2018-11-29 18:43, Toomas Soome wrote: > I just did push biosdisk updates to stable/12, I wonder if you could > test those bits… Thank you! I haven't tried it yet, but I wonder whether this fix was already incorporated into 12.0-RC3, which would make my rescue easier. Otherwise I can build a stable/12 on another host and transplant the problematic file(s) to the affected host - if I knew which files to copy. I wonder also, if the today's posting by cksalexander@q.com on the freebsd-stable ML titled "FreeBSD-12.0-RC3-i386-disc1.iso does not boot" could be describing the same problem? Mark >> On 29 Nov 2018, at 17:01, Mark Martinec <Mark.Martinec+freebsd@ijs.si> >> wrote: >> >> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1744424063.31566579.1543701056566.JavaMail.zimbra>