From owner-freebsd-stable@freebsd.org Tue Dec 10 14:18:28 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CFFE41DA9D7 for ; Tue, 10 Dec 2019 14:18:28 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47XMc335nVz4vHF for ; Tue, 10 Dec 2019 14:18:27 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 47XMbz34yFzkQ3 for ; Tue, 10 Dec 2019 15:18:23 +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=1575987499; x=1578579500; bh=LqO u37iF6d+6oLlUGES1xW5IzLyKoEJpCeYCvSingPE=; b=kclWRD66m25Ohls7w57 n76mAmBO/77aB1ip+etPdPm1Tp4g7ilNDLHiIkTsgTFGXtqp15BsabE54YRPan82 hq7uVEKmnHMRk8IDpmjMdEBiD+1vHUiGfrRi4cheMbzcRO2s4oMDWb+l0RGllEQL Siyld6bRzazGLD04xVXCz5Bw= 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 XL3OCYJ0_GOs for ; Tue, 10 Dec 2019 15:18:19 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 47XMbv6x7wzkQ2 for ; Tue, 10 Dec 2019 15:18:19 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 47XMbv1nxWzs6 for ; Tue, 10 Dec 2019 15:18:19 +0100 (CET) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by webmail.ijs.si with HTTP (HTTP/2.0 POST); Tue, 10 Dec 2019 15:18:19 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 10 Dec 2019 15:18:19 +0100 From: Mark Martinec To: 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: <53ceda24-fa1b-8546-3511-bd500b440dfe@digiware.nl> References: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> <0F5FCC70-EADB-4F9E-A391-F1A73BE5608F@me.com> <1543954753.1860.243.camel@freebsd.org> <53ceda24-fa1b-8546-3511-bd500b440dfe@digiware.nl> Message-ID: <4c4019102b63054f8de93324dba0e776@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.1 X-Rspamd-Queue-Id: 47XMc335nVz4vHF X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ijs.si header.s=jakla4 header.b=kclWRD66; dmarc=pass (policy=none) header.from=ijs.si; spf=pass (mx1.freebsd.org: domain of Mark.Martinec@ijs.si designates 2001:1470:ff80::25 as permitted sender) smtp.mailfrom=Mark.Martinec@ijs.si X-Spamd-Result: default: False [-3.48 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[ijs.si:s=jakla4]; 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]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; IP_SCORE(-0.48)[asn: 2107(-2.43), country: SI(0.01)]; 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]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; 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]; DWL_DNSWL_NONE(0.00)[ijs.si.dwl.dnswl.org : 127.0.11.0] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2019 14:18:28 -0000 Commenting on a thread from 2018-12 and from 2019-09-20, with my solution to the boot problem at the end, in case anyone is still interested. ======= On 2018-11-29 myself wrote: (after upgrading from 11.2 to 12.0): > 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. [...] (on 2018-12-04): > The situation has not changed: the BTX loader lists all BIOS drives > C..J (disk0..disk7), then a spinner starts and gets stuck forever. > It never reaches the 'BIOS 635kB/3537856kB available memory' line. > > While trying to restore the old /boot from 11.2, I tried booting > a live image from a 12.0-RC3 memory stick - and the loader got > stuck again, same as when booting from a disk. > So I had to boot from an 11.2 memstick to be able to regain control. ======= 2018-12-04, Ian Lepore writes: > Toomas Soome wrote: > | ok, if you could perform 2 tests: > | 1. from loader prompt enter 0x413 0xa000 - @w . cr > | 2. on first spinner, press space and type on boot: prompt: > | /boot/loader_4th and see if that will do better > | thanks, toomas > I don't think that will be an option. If it hasn't gotten to the point > of saying how much BIOS available memory there is, it's only halfway > through loader main() and has hung before getting to interact(). > > In fact, if that line hasn't printed, but some disk drives have been > listed, it pretty much has to be hung in the "March through the device > switch probing for things" loop. If all the disks are listed, then it > got through that entry in the devsw, and is likely hanging in the > dv_init calls for either the pxedisk or zfsdev devices. ======= 2018-12-07 19:08, Willem Jan Withagen wrote: > Ended up more or less in the same situation this afternoon with > freebsd-upgrade to [12.0]-RC3 > Boot stops after listing all DOS disks, in a spinner. > So that is no fix. > > I booted from USB 11.2 and replaced the /boot/zfs{boot,loader} by the > 11.2 ones. > That makes my server again happy. =======are 2019-09-19 16:02, Kurt Jaeger wrote: Subject: Re: Lockdown adaX numbers to allow booting ? > | Kurt Jaeger writes: > | The problem is that if all 10 disks are connected, the system > | looses track from where it should boot and fails to boot (serial > boot log): > | > | Consoles: internal video/keyboard serial port > | BTX loader 1.00 BTX version is 1.02 > | Consoles: internal video/keyboard serial port > | BIOS drive C: is disk0 > | BIOS drive D: is disk1 > | BIOS drive E: is disk2 > | BIOS drive F: is disk3 > | BIOS drive G: is disk4 > | BIOS drive H: is disk5 > | BIOS drive I: is disk6 > | BIOS drive J: is disk7 > | BIOS drive K: is disk8 > | BIOS drive L: is disk9 > | // > | [...] > | The solution right now is this to unplug all disks of the 'bck' > pool, > | reboot, and re-insert the data disks after the boot is finished. > | [...] > | No gpart on the bck pool, raw drives. 2019-09-20 17:27, Mark Martinec wrote: Subject: Re: Lockdown adaX numbers to allow booting ? > > This sounds very much like my experience: > > 2018-11-29, Boot loader stuck after first stage upgrading 11.2 to > 12.0-RC2 > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-November/090129.html > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090159.html > > I now have three SuperMicro machines which are unable to boot after > upgrading 11.2 to 12.0. After unsuccessfully fiddling with boot > loaders, > I have reverted two back to 11.2 (which boots and works fine again), > and the third one is now at 12.0 but needs the boot hack as described > by Kurt, i.e. pull out half the disks (of the 'data' pool), boot the > system, plug the disks back in and zfs mount the remaining pool. > > Considering that the 11.2 boots and works fine on these machines, > I consider it a btx loader failure and not a BIOS issue. > > What is common with these three machines is that they have one pool > on raw devices for historical reasons (not on gpt partitions). > My guess is that the new loader gets confused by these raw disks. ======= Ok, now to my current situation and solution/workaround. What was common with these hosts (and similar) is that a machine has more than a couple of disks, with a zfs pool (non-root) on raw devices (for historical reasons), not on gpt partitions. Three workarounds seem possible: - replace a boot loader with the one from 11.2, or - using a default loader from 12, disconnect a sufficient number of data disks, boot, then reconnect disks and zfs attach the pool, - or my current solution: zfs offline one disk at a time from a data pool, wipe it, set up a gpt partition on it and put it back to the pool by 'zfs replace', letting it resilver. It was a painful and slightly risky procedure (9 hours of resilvering each of the seven disks), but this procedure has now salvaged our remaining hosts which could not be upgraded from 11.2 to 12. Mark From owner-freebsd-stable@freebsd.org Tue Dec 10 15:14:17 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A70FB1DBDA6 for ; Tue, 10 Dec 2019 15:14:17 +0000 (UTC) (envelope-from nikolay.kostirya@i11.co) Received: from mx.i11.co (mx.i11.co [159.69.78.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47XNrS3tpbz3Fys for ; Tue, 10 Dec 2019 15:14:16 +0000 (UTC) (envelope-from nikolay.kostirya@i11.co) Received: from [82.207.42.188] (helo=thinkpad) by mx.i11.co with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iehDF-0006WY-4I for freebsd-stable@freebsd.org; Tue, 10 Dec 2019 15:14:09 +0000 Date: Tue, 10 Dec 2019 17:14:07 +0200 From: Nick Kostirya To: freebsd-stable@freebsd.org Subject: FreeBSD 12 and PS/2 trackpoint Message-ID: <20191210171407.02ea4de5@thinkpad> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; i386-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47XNrS3tpbz3Fys X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.49 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[i11.co:s=omicron]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:159.69.78.69]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-1.99)[ip: (-9.46), ipnet: 159.69.0.0/16(1.12), asn: 24940(-1.59), country: DE(-0.01)]; DKIM_TRACE(0.00)[i11.co:+]; DMARC_POLICY_ALLOW(-0.50)[i11.co,reject]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2019 15:14:17 -0000 Hello. I have thinkpad laptop. PS/2 trackpoint is worked on FreeBSD 11. But it is not worked on FreeBSD 12 (12.1-RELEASE-p1 i386). > dmesg -a | grep psm psm0: failed to get status. psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 psm0: failed to enable the device (doopen). Please tell me how I can fix this. Nick. From owner-freebsd-stable@freebsd.org Tue Dec 10 15:36:36 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3A00D1DC742 for ; Tue, 10 Dec 2019 15:36:36 +0000 (UTC) (envelope-from marcnarc@gmail.com) Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47XPLC33Fzz3HGV for ; Tue, 10 Dec 2019 15:36:35 +0000 (UTC) (envelope-from marcnarc@gmail.com) Received: by mail-qt1-x82d.google.com with SMTP id s8so3171019qte.2 for ; Tue, 10 Dec 2019 07:36:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=6bdH89o3ULMS3r/3ah13JNbqoXRupKKjKIyY/9vutok=; b=RO/fS56q1fvAICzt7o2js5hx37RCO8CZwZhN/7uXKLp/8KQALAUKJtczSnc0qkg94T pIG6J5TIBhpBFykF03f2G2WEB/LbgcuOlwZgj9UABv6lWleA6/fhOCMmz0UvTDEDvHZg Wq8w+gaecZnMfIJxlQBPprRo77PDRAqkGqSXpCmpuADi+wUadCBsZljBs8TAJOY2vBie JeQYwoyxXF3H/cnFq4nzmTPZS74nD7bPKqUyB5Ww7LJod9b0daNFRCogFZwuIs8PKC8N 2zWcBUdygNMJqtF41H9sTJTBNHgJcaq2iSSRh5TKuM8S4oPJb1W+uKr59LJpAtRzClCh y+dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6bdH89o3ULMS3r/3ah13JNbqoXRupKKjKIyY/9vutok=; b=jMnUX0PePJsI7p8a/80uozvgLwr/357qPL0Wc7budBWPz2kZi0tlv9rGcfdFCAJ2OD QgvnufQIrOp+bq53/0e7t6ERl/f6EtRnAttEK3RfFjjEuEg6tqEoWmvNjHkRsKLODLlH 1jpR5kY3utXi/jzTjwgRcaTLNz7h3k++w7VhntM0KkDPX2KPlCQEzJlw/YJyn1hMWUlU aDrHWHpMqtCgJ8KOqGYvcBU9Lh/Yqa04LpzYoFBcJpKApZOMRbZS2Q1lqWrmof47Qz3L 4cvaD4IBH4QrAgAXZF9wNaL6njCwKPBLjdxVm2nQybggo7o/UZvchc31tc9wMZkj53Hq T2UQ== X-Gm-Message-State: APjAAAXhFBObmS+YMfJsBmO3acXoGuaWgUG/6RF1k+vRhjYTfMp8DcEB BpOJBdMyCFAXPUsTHXVRDGw= X-Google-Smtp-Source: APXvYqw4z4ceH9G2MhVkG/y4DBQwlakA9lGg+tRYfW55ebZKyLP36AvcxV0uqYz8oAiEtpjCe9tCNw== X-Received: by 2002:aed:20e5:: with SMTP id 92mr16509549qtb.294.1575992193781; Tue, 10 Dec 2019 07:36:33 -0800 (PST) Received: from [10.10.1.32] ([192.252.130.194]) by smtp.gmail.com with ESMTPSA id s34sm1230809qtb.73.2019.12.10.07.36.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 10 Dec 2019 07:36:33 -0800 (PST) Subject: Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 To: Mark Martinec , freebsd-stable@freebsd.org References: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> <0F5FCC70-EADB-4F9E-A391-F1A73BE5608F@me.com> <1543954753.1860.243.camel@freebsd.org> <53ceda24-fa1b-8546-3511-bd500b440dfe@digiware.nl> <4c4019102b63054f8de93324dba0e776@ijs.si> From: Marc Branchaud Message-ID: Date: Tue, 10 Dec 2019 10:35:26 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <4c4019102b63054f8de93324dba0e776@ijs.si> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 47XPLC33Fzz3HGV X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=RO/fS56q; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of marcnarc@gmail.com designates 2607:f8b0:4864:20::82d as permitted sender) smtp.mailfrom=marcnarc@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.36), ipnet: 2607:f8b0::/32(-2.22), asn: 15169(-1.92), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[d.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2019 15:36:36 -0000 On 2019-12-10 9:18 a.m., Mark Martinec wrote: > Commenting on a thread from 2018-12 and from 2019-09-20, with my solution > to the boot problem at the end, in case anyone is still interested. Thank you very much for this. A couple of questions: (1) Why do you say "raw devices for historical reasons"? Glancing through the zpool man page and the Handbook, I see nothing recommending or requiring GPT partitions. (2) Just to be 100% clear, my 11.3 non-root zpool looks like this: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada4 ONLINE 0 0 0 ada5 ONLINE 0 0 0 ada6 ONLINE 0 0 0 ada7 ONLINE 0 0 0 So this is using raw devices. Are you saying that if I upgrade this machine to 12 that it won't be able to boot? Thanks again! M. > ======= > > On 2018-11-29 myself wrote: > (after upgrading from 11.2 to 12.0): >> 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. > [...] (on 2018-12-04): >> The situation has not changed: the BTX loader lists all BIOS drives >> C..J (disk0..disk7), then a spinner starts and gets stuck forever. >> It never reaches the 'BIOS 635kB/3537856kB available memory' line. >> >> While trying to restore the old /boot from 11.2, I tried booting >> a live image from a 12.0-RC3 memory stick - and the loader got >> stuck again, same as when booting from a disk. >> So I had to boot from an 11.2 memstick to be able to regain control. > > ======= > > 2018-12-04, Ian Lepore writes: >>   Toomas Soome wrote: >> |    ok, if you could perform 2 tests: >> |    1. from loader prompt enter 0x413 0xa000 - @w . cr >> |    2. on first spinner, press space and type on boot: prompt: >> |    /boot/loader_4th and see if that will do better >> |    thanks, toomas >> I don't think that will be an option.  If it hasn't gotten to the point >> of saying how much BIOS available memory there is, it's only halfway >> through loader main() and has hung before getting to interact(). >> >> In fact, if that line hasn't printed, but some disk drives have been >> listed, it pretty much has to be hung in the "March through the device >> switch probing for things" loop. If all the disks are listed, then it >> got through that entry in the devsw, and is likely hanging in the >> dv_init calls for either the pxedisk or zfsdev devices. > > ======= > > 2018-12-07 19:08, Willem Jan Withagen wrote: >> Ended up more or less in the same situation this afternoon with >> freebsd-upgrade to [12.0]-RC3 >> Boot stops after listing all DOS disks, in a spinner. >> So that is no fix. >> >> I booted from USB 11.2 and replaced the /boot/zfs{boot,loader} by the >> 11.2 ones. >> That makes my server again happy. > > =======are > > 2019-09-19 16:02, Kurt Jaeger wrote: > Subject: Re: Lockdown adaX numbers to allow booting ? >> |  Kurt Jaeger writes: >> |    The problem is that if all 10 disks are connected, the system >> |    looses track from where it should boot and fails to boot (serial >> boot log): >> | >> |    Consoles: internal video/keyboard  serial port >> |    BTX loader 1.00  BTX version is 1.02 >> |    Consoles: internal video/keyboard  serial port >> |    BIOS drive C: is disk0 >> |    BIOS drive D: is disk1 >> |    BIOS drive E: is disk2 >> |    BIOS drive F: is disk3 >> |    BIOS drive G: is disk4 >> |    BIOS drive H: is disk5 >> |    BIOS drive I: is disk6 >> |    BIOS drive J: is disk7 >> |    BIOS drive K: is disk8 >> |    BIOS drive L: is disk9 >> |    // >> |    [...] >> |    The solution right now is this to unplug all disks of the 'bck' >> pool, >> |    reboot, and re-insert the data disks after the boot is finished. >> |    [...] >> |    No gpart on the bck pool, raw drives. > > 2019-09-20 17:27, Mark Martinec wrote: > Subject: Re: Lockdown adaX numbers to allow booting ? >> >> This sounds very much like my experience: >> >>   2018-11-29, Boot loader stuck after first stage upgrading 11.2 to >> 12.0-RC2 >> https://lists.freebsd.org/pipermail/freebsd-stable/2018-November/090129.html >> >> https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090159.html >> >> >> I now have three SuperMicro machines which are unable to boot after >> upgrading 11.2 to 12.0. After unsuccessfully fiddling with boot loaders, >> I have reverted two back to 11.2 (which boots and works fine again), >> and the third one is now at 12.0 but needs the boot hack as described >> by Kurt, i.e. pull out half the disks (of the 'data' pool), boot the >> system, plug the disks back in and zfs mount the remaining pool. >> >> Considering that the 11.2 boots and works fine on these machines, >> I consider it a btx loader failure and not a BIOS issue. >> >> What is common with these three machines is that they have one pool >> on raw devices for historical reasons (not on gpt partitions). >> My guess is that the new loader gets confused by these raw disks. > > ======= > > Ok, now to my current situation and solution/workaround. > > What was common with these hosts (and similar) is that a machine > has more than a couple of disks, with a zfs pool (non-root) on > raw devices (for historical reasons), not on gpt partitions. > > Three workarounds seem possible: > > - replace a boot loader with the one from 11.2, or > > - using a default loader from 12, disconnect a sufficient number >   of data disks, boot, then reconnect disks and zfs attach the pool, > > - or my current solution: zfs offline one disk at a time from >   a data pool, wipe it, set up a gpt partition on it and >   put it back to the pool by 'zfs replace', letting it resilver. >   It was a painful and slightly risky procedure (9 hours of >   resilvering each of the seven disks), but this procedure >   has now salvaged our remaining hosts which could not be >   upgraded from 11.2 to 12. > > Mark > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Tue Dec 10 16:09:07 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5DF2C1DD3D8 for ; Tue, 10 Dec 2019 16:09:07 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47XQ3j6XkWz3Jrm for ; Tue, 10 Dec 2019 16:09:05 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 47XQ3d6tLlzm46; Tue, 10 Dec 2019 17:09:01 +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=1575994138; x=1578586139; bh=wdq bMNaFYZibkabxBCaNm/iemWN30ypgPU52UOL1qdg=; b=b20ajeEz2Xax6gUtcPb Y256Xsi3AJ5H9bLaJi0GIRrK8x/9o3eedhYYyP7jhdI/A49wYTM78Je9or+CULla fRZTCnSY91ZKxGSusP4375lDZR5l/gFJZiEtECJQ7xzIq8WQPYzuHaXiPUC4Ka9Q O5pKLUEPRh8TyQIQpFYGL8Z4= 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 qCKlhnTzPHR9; Tue, 10 Dec 2019 17:08:58 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 47XQ3Z50BPzm43; Tue, 10 Dec 2019 17:08:58 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 47XQ3Z4j7zzNc; Tue, 10 Dec 2019 17:08:58 +0100 (CET) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by webmail.ijs.si with HTTP (HTTP/2.0 POST); Tue, 10 Dec 2019 17:08:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 10 Dec 2019 17:08:58 +0100 From: Mark Martinec To: freebsd-stable@freebsd.org Cc: Marc Branchaud Subject: Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 Organization: Jozef Stefan Institute In-Reply-To: References: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> <0F5FCC70-EADB-4F9E-A391-F1A73BE5608F@me.com> <1543954753.1860.243.camel@freebsd.org> <53ceda24-fa1b-8546-3511-bd500b440dfe@digiware.nl> <4c4019102b63054f8de93324dba0e776@ijs.si> Message-ID: X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.1 X-Rspamd-Queue-Id: 47XQ3j6XkWz3Jrm X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ijs.si header.s=jakla4 header.b=b20ajeEz; dmarc=pass (policy=none) header.from=ijs.si; spf=pass (mx1.freebsd.org: domain of Mark.Martinec@ijs.si designates 2001:1470:ff80::25 as permitted sender) smtp.mailfrom=Mark.Martinec@ijs.si X-Spamd-Result: default: False [-3.51 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[ijs.si:s=jakla4]; RCVD_COUNT_FIVE(0.00)[6]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:1470:ff80::25]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DWL_DNSWL_NONE(0.00)[ijs.si.dwl.dnswl.org : 127.0.11.0]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[ijs.si:+]; RCPT_COUNT_TWO(0.00)[2]; 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]; DMARC_POLICY_ALLOW(-0.50)[ijs.si,none]; IP_SCORE(-0.51)[asn: 2107(-2.55), country: SI(0.01)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; 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]; FREEMAIL_CC(0.00)[gmail.com] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2019 16:09:07 -0000 2019-12-10 16:35, Marc Branchaud wrote: > On 2019-12-10 9:18 a.m., Mark Martinec wrote: >> Commenting on a thread from 2018-12 and from 2019-09-20, with my >> solution >> to the boot problem at the end, in case anyone is still interested. > > Thank you very much for this. A couple of questions: > > (1) Why do you say "raw devices for historical reasons"? Glancing > through the zpool man page and the Handbook, I see nothing > recommending or requiring GPT partitions. Apparently using raw devices for zpool is now discouraged, although I don't think it has ever become officially unsupported. > (2) Just to be 100% clear, my 11.3 non-root zpool looks like this: > NAME STATE READ WRITE CKSUM > storage ONLINE 0 0 0 > raidz2-0 ONLINE 0 0 0 > ada2 ONLINE 0 0 0 > ada3 ONLINE 0 0 0 > ada4 ONLINE 0 0 0 > ada5 ONLINE 0 0 0 > ada6 ONLINE 0 0 0 > ada7 ONLINE 0 0 0 > > So this is using raw devices. Are you saying that if I upgrade this > machine to 12 that it won't be able to boot? It is possible it won't boot under 12, although not necessary. Try booting from a 12.0 (or 12.0) memory stick - it that boots, it is probably a safe bet that it will survive an upgrade. Of the bunch of machines that I have upgraded from 11.2 to 12, only three failed to boot under 12.0 loader. There were a couple of others which upgraded and booted fine even though they had a zfs pool on raw devices. I never had a problem of booting on hosts that had zfs pool on a gpt partition. So it's a lottery: a few raw devices in a zpool seem to do fine, while many raw devices in a zpool is asking for trouble under 12.0 and later. Mark From owner-freebsd-stable@freebsd.org Tue Dec 10 21:18:12 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2C9851E4B92; Tue, 10 Dec 2019 21:18:12 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47XXwN0NpZz4HJS; Tue, 10 Dec 2019 21:18:12 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1129) id DD414FEB3; Tue, 10 Dec 2019 21:18:11 +0000 (UTC) Date: Tue, 10 Dec 2019 21:18:11 +0000 From: Li-Wen Hsu To: freebsd-testing@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD CI Weekly Report 2019-12-08 Message-ID: <20191210211811.GA76610@freefall.freebsd.org> Reply-To: freebsd-testing@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.11.4 (2019-03-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2019 21:18:12 -0000 (Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2019-12-08 =================================== Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-12-02 to 2019-12-08. During this period, we have: * 2463 builds (95% (-1.3) passed, 5% (+1.3) failed) of buildworld and buildkernel (GENERIC and LINT) were executed on aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11 branches. * 353 test runs (98% (+0.5) passed, 1.7% (-0.8) unstable, 0.3% (+0.3) exception) were executed on amd64, i386, riscv64 architectures for head, stable/12, stable/11 branches. * 42 doc builds (100% (0) passed) Test case status (on 2019-12-08 23:59): | Branch/Architecture | Total | Pass | Fail | Skipped | | ------------------- | ---------- | --------- | ----- | ------- | | head/amd64 | 7632 (+12) | 7563 (+9) | 0 (0) | 69 (+3) | | head/i386 | 7630 (+12) | 7557 (+9) | 0 (0) | 73 (+3) | | 12-STABLE/amd64 | 7488 (+5) | 7437 (+5) | 0 (0) | 51 (0) | | 12-STABLE/i386 | 7486 (+5) | 7428 (+2) | 0 (0) | 58 (+3) | | 11-STABLE/amd64 | 6858 (+5) | 6811 (+5) | 0 (0) | 47 (0) | | 11-STABLE/i386 | 6856 (+5) | 6804 (+2) | 0 (0) | 52 (+3) | (The statistics from experimental jobs are omitted) If any of the issues found by CI are in your area of interest or expertise please investigate the PRs listed below. The latest web version of this report is available at https://hackmd.io/@FreeBSD-CI/report-20191208 and archive is available at https://hackmd.io/@FreeBSD-CI/, any help is welcome. ## News * Experimental "Hardware test lab" result is available at: https://ci.freebsd.org/hwlab/ , more hardware support is welcomed! ## Failing and Flaky Tests (from experimental jobs) * https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/ * cddl.usr.sbin.dtrace.common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237641 * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/ * There are ~13 failing and ~109 skipped cases, including flakey ones, see https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/ for more details * Work for cleaning these failing cass are in progress ## Disabled Tests * sys.fs.tmpfs.mount_test.large https://bugs.freebsd.org/212862 * sys.fs.tmpfs.link_test.kqueue https://bugs.freebsd.org/213662 * sys.kqueue.libkqueue.kqueue_test.main https://bugs.freebsd.org/233586 * sys.kern.ptrace_test.ptrace__PT_KILL_competing_stop https://bugs.freebsd.org/220841 * lib.libc.regex.exhaust_test.regcomp_too_big (i386 only) https://bugs.freebsd.org/237450 * sys.netinet.socket_afinet.socket_afinet_bind_zero https://bugs.freebsd.org/238781 * sys.netpfil.pf.names.names * sys.netpfil.pf.synproxy.synproxy https://bugs.freebsd.org/238870 * sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger https://bugs.freebsd.org/239292 * sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger https://bugs.freebsd.org/239397 * sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger https://bugs.freebsd.org/239399 * sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger https://bugs.freebsd.org/239425 * lib.libc.gen.getmntinfo_test.getmntinfo_test https://bugs.freebsd.org/240049 * sys.sys.qmath_test.qdivq_s64q https://bugs.freebsd.org/240219 * sys.kern.ptrace_test.ptrace__getppid https://bugs.freebsd.org/240510 * lib.libc.sys.stat_test.stat_socket https://bugs.freebsd.org/240621 * lib.libarchive.functional_test.test_write_filter_zstd https://bugs.freebsd.org/240683 * lib.libcasper.services.cap_dns.dns_test.main https://bugs.freebsd.org/241435 * local.kyua.* (31 cases) & local.lutok.* (3 cases) on 11-i386 https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/2278/testReport/ ## Issues ### Cause build fails * https://bugs.freebsd.org/233735 Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory * https://bugs.freebsd.org/233769 Possible build race: ld: error: unable to find library -lgcc_s ### Cause kernel panics * https://bugs.freebsd.org/238870 sys.netpfil.pf.names.names and sys.netpfil.pf.synproxy.synproxy cause panic Patch exists: * https://reviews.freebsd.org/D20868 * https://reviews.freebsd.org/D20869 ### Open * https://bugs.freebsd.org/237403 Tests in sys/opencrypto should be converted to Python3 * https://bugs.freebsd.org/237641 Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d * https://bugs.freebsd.org/237656 "Freed UMA keg (rtentry) was not empty (18 items). Lost 1 pages of memory." seen when running sys/netipsec tests * https://bugs.freebsd.org/238781 sys.netinet.socket_afinet.socket_afinet_bind_zero does not work when mac_portacl(4) loaded * https://bugs.freebsd.org/239292 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger * https://bugs.freebsd.org/239397 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger * https://bugs.freebsd.org/239399 Flakey test case: sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger * https://bugs.freebsd.org/239425 Flakey test case: sys.kern.ptrace_test.ptrace__follow_fork_parent_detached_unrelated_debugger * https://bugs.freebsd.org/241662 Flakey test case: lib.libarchive.functional_test.test_fuzz_iso9660 ### Others * [Tickets related to testing@](https://preview.tinyurl.com/y9maauwg) From owner-freebsd-stable@freebsd.org Wed Dec 11 03:16:41 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3CD051CAFD4 for ; Wed, 11 Dec 2019 03:16:41 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Xhsz5lFxz4bdH for ; Wed, 11 Dec 2019 03:16:39 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13:0:0:0:5]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id xBB3GO0Y059637 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 11 Dec 2019 03:16:25 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: Mark.Martinec+freebsd@ijs.si Received: from [10.58.0.4] (dadv@[10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id xBB3GMxt041044 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 11 Dec 2019 10:16:22 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 To: Mark Martinec , freebsd-stable@freebsd.org References: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> <0F5FCC70-EADB-4F9E-A391-F1A73BE5608F@me.com> <1543954753.1860.243.camel@freebsd.org> <53ceda24-fa1b-8546-3511-bd500b440dfe@digiware.nl> <4c4019102b63054f8de93324dba0e776@ijs.si> Cc: Marc Branchaud From: Eugene Grosbein Message-ID: <998f886a-7498-7268-75cf-4e767835db82@grosbein.net> Date: Wed, 11 Dec 2019 10:16:18 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record * -0.0 SPF_PASS SPF: sender matches SPF record * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on hz.grosbein.net X-Rspamd-Queue-Id: 47Xhsz5lFxz4bdH X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=permerror (mx1.freebsd.org: domain of eugen@grosbein.net uses mechanism not recognized by this client) smtp.mailfrom=eugen@grosbein.net X-Spamd-Result: default: False [-2.74 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; R_BAD_CTE_7BIT(1.05)[7bit,utf8]; DMARC_NA(0.00)[grosbein.net]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_PERMFAIL(0.00)[]; IP_SCORE(-1.69)[ip: (-4.46), ipnet: 2a01:4f8::/29(-2.40), asn: 24940(-1.59), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; FREEMAIL_CC(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2019 03:16:41 -0000 10.12.2019 23:08, Mark Martinec пишет: > 2019-12-10 16:35, Marc Branchaud wrote: > >> On 2019-12-10 9:18 a.m., Mark Martinec wrote: >>> Commenting on a thread from 2018-12 and from 2019-09-20, with my solution >>> to the boot problem at the end, in case anyone is still interested. >> >> Thank you very much for this. A couple of questions: >> >> (1) Why do you say "raw devices for historical reasons"? Glancing >> through the zpool man page and the Handbook, I see nothing >> recommending or requiring GPT partitions. > > Apparently using raw devices for zpool is now discouraged, > although I don't think it has ever become officially unsupported. Loader bugs do not mean that "using raw devices for zpool is now discouraged". From owner-freebsd-stable@freebsd.org Wed Dec 11 16:30:28 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3BF5A1DA32E for ; Wed, 11 Dec 2019 16:30:28 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-il1-f180.google.com (mail-il1-f180.google.com [209.85.166.180]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Y2Tv1zT6z4JVG for ; Wed, 11 Dec 2019 16:30:26 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-il1-f180.google.com with SMTP id t17so19920792ilm.13 for ; Wed, 11 Dec 2019 08:30:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=iW+NhvLEkdBcRxJymjM3txiRIcIdPSJVgMcRBUWH4XU=; b=HQngF3SlYmk2DvoqdrKTFG7428BB3Q6BtsQpAhQxXh5CbqedZl00wSOag+kbhEhJEV zd4Nypf0oxxWCaDyFSn2B7hl8vK8Ah7Q8nkzhqQIdfd2IlL5jlMWBYpewoi/wNBE38lW GvKoOFCCa1v/9xqAdxEWV35rhjRi/OxhsgtODomQ4cPeUM3lTqsvuBsXXoLAEQt1NMqC HJswQwXzmE9VPH6ws/d6jQYu8Yig6wpC/3BcjdEY2AoGp84NHsclte/thrjOX69xwjXT YTZYWSrHoPc09g1GVHioZL3q3jrb3EONIRRwRWHcPmubmS2s2GX+XtYgxZM8wZyT3SeK lNnQ== X-Gm-Message-State: APjAAAVfHCZ8Rt6ePfRtmEmAwSVzxB2cOEkbQEr0nBeZJE/T4ns8ZU/5 UXhzXlWuLQvJvqtM4O4TS/mT5PLyrmLeEzWhWPR6kVS0 X-Google-Smtp-Source: APXvYqwAlQuPK3LVRIHXI4xrptKDfcbaqIz1zQsY6LPdrZp25WODJqhfXKgWzHr1OWXLxl/iz/UaJlir5vqsTPZ8CrQ= X-Received: by 2002:a92:cbd2:: with SMTP id s18mr2352232ilq.98.1576081826083; Wed, 11 Dec 2019 08:30:26 -0800 (PST) MIME-Version: 1.0 References: <20191206142221.GL2744@kib.kiev.ua> In-Reply-To: From: Ed Maste Date: Wed, 11 Dec 2019 07:44:00 -0500 Message-ID: Subject: Re: Disabling speculative execution mitigations To: "O'Connor, Daniel" , freebsd-stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47Y2Tv1zT6z4JVG X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.180 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-4.33 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[180.166.85.209.list.dnswl.org : 127.0.5.0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-2.33)[ip: (-6.54), ipnet: 209.85.128.0/17(-3.14), asn: 15169(-1.92), country: US(-0.05)]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[180.166.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2019 16:30:28 -0000 On Fri, 6 Dec 2019 at 22:54, O'Connor, Daniel wrote: > > With respect to the man page, I find it difficult to know what a given value for each sysctl will do, as evidenced by my confusion above about IBRS. scottl recently moved these sysctls to machdep.mitigations in r355436, but they've kept the existing names and sense. So, some still have an enable control while some are disable, some report "state: inactive" while others report "active: 0". Work is ongoing now to rationalize these so that the sense is true for mitigation enabled. Backwards compatibility will be maintained for the sysctl paths in stable (e.g. hw.ibrs*) but not the interim names (machdep.mitigations.*) From owner-freebsd-stable@freebsd.org Thu Dec 12 01:44:47 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6E5821E6EA2 for ; Thu, 12 Dec 2019 01:44:47 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [208.111.40.118]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47YGnV2XrQz3Qt2 for ; Thu, 12 Dec 2019 01:44:46 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (65-100-43-2.dia.static.qwest.net [65.100.43.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "chombo.houseloki.net", Issuer "brtsvcs.net CA" (verified OK)) by echo.brtsvcs.net (Postfix) with ESMTPS id 9069438D36 for ; Thu, 12 Dec 2019 01:44:32 +0000 (UTC) Received: from [IPv6:2602:41:642b:630:c53:4c47:dd0:fea7] (unknown [IPv6:2602:41:642b:630:c53:4c47:dd0:fea7]) by chombo.houseloki.net (Postfix) with ESMTPSA id 40BB72FC for ; Wed, 11 Dec 2019 17:44:27 -0800 (PST) To: freebsd-stable@freebsd.org From: Mel Pilgrim Subject: 11.3->12.1 upgrade, pwd db not rehashed after adding ntpd user? Message-ID: Date: Wed, 11 Dec 2019 17:44:27 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47YGnV2XrQz3Qt2 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of list_freebsd@bluerosetech.com designates 208.111.40.118 as permitted sender) smtp.mailfrom=list_freebsd@bluerosetech.com X-Spamd-Result: default: False [-4.38 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[bluerosetech.com]; IP_SCORE(-3.08)[ip: (-7.68), ipnet: 208.111.40.0/24(-3.84), asn: 36236(-3.84), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:36236, ipnet:208.111.40.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2019 01:44:47 -0000 I used freebsd-update to upgrade several 11.3-p5 systems to 12.1-p1. The etc update process added the ntpd/ntpd user/group. It showed the line changes in the plaintext passwd/group files, but the process appears to omit the pwd_mkdb step. After the upgrade, ntpd fails to start: # service ntpd start Starting ntpd. su: unknown login: ntpd /etc/rc.d/ntpd: WARNING: failed to start ntpd Running the usual pwd_mkdb command fixes the issue. From owner-freebsd-stable@freebsd.org Thu Dec 12 04:50:56 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BDEEE1EBAD8 for ; Thu, 12 Dec 2019 04:50:56 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::1]) (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 47YLwH4rX6z45KK for ; Thu, 12 Dec 2019 04:50:55 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 19A3A110219; Wed, 11 Dec 2019 22:50:47 -0600 (CST) Received: by mail.geeks.org (Postfix, from userid 1003) id E4C2011020A; Wed, 11 Dec 2019 22:50:46 -0600 (CST) Date: Wed, 11 Dec 2019 22:50:46 -0600 From: Doug McIntyre To: Mel Pilgrim Cc: freebsd-stable@freebsd.org Subject: Re: 11.3->12.1 upgrade, pwd db not rehashed after adding ntpd user? Message-ID: <20191212045046.GA87026@geeks.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 47YLwH4rX6z45KK X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of merlyn@geeks.org designates 2001:4980:3333:1::1 as permitted sender) smtp.mailfrom=merlyn@geeks.org X-Spamd-Result: default: False [0.81 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.63)[-0.627,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr]; NEURAL_HAM_LONG(-0.00)[-0.002,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[geeks.org]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:7753, ipnet:2001:4980::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.74)[asn: 7753(3.75), country: US(-0.05)] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2019 04:50:56 -0000 On Wed, Dec 11, 2019 at 05:44:27PM -0800, Mel Pilgrim wrote: > I used freebsd-update to upgrade several 11.3-p5 systems to 12.1-p1. > The etc update process added the ntpd/ntpd user/group. It showed the > line changes in the plaintext passwd/group files, but the process > appears to omit the pwd_mkdb step. > > After the upgrade, ntpd fails to start: > > # service ntpd start > Starting ntpd. > su: unknown login: ntpd > /etc/rc.d/ntpd: WARNING: failed to start ntpd > > Running the usual pwd_mkdb command fixes the issue. I've had varied results with the same thing from 11.2 to 12.1. Sometimes it works, oftentimes it does not. pwd_mkdb does fix it up, but would be nice to not have to do that. From owner-freebsd-stable@freebsd.org Thu Dec 12 10:15:33 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0A53A1CBEDF for ; Thu, 12 Dec 2019 10:15:33 +0000 (UTC) (envelope-from tomas.engin@teleservice.net) Received: from b-halon-backup.teleservice.net (b-halon-backup.teleservice.net [85.30.129.128]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47YV6p5gptz4MZ1 for ; Thu, 12 Dec 2019 10:15:30 +0000 (UTC) (envelope-from tomas.engin@teleservice.net) Received: from S-MAIL-2.internal.teleservice.net (unknown [85.30.129.6]) by b-halon-1.teleservice.net (Halon) with ESMTPS id 4fc7c424-1cc8-11ea-bf39-00505689b487; Thu, 12 Dec 2019 11:15:24 +0100 (CET) Received: from S-MAIL-2.internal.teleservice.net (192.168.101.8) by S-MAIL-2.internal.teleservice.net (192.168.101.8) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 12 Dec 2019 11:15:24 +0100 Received: from S-MAIL-2.internal.teleservice.net ([fe80::9971:9649:aa77:8416]) by S-MAIL-2.internal.teleservice.net ([fe80::9971:9649:aa77:8416%12]) with mapi id 15.00.1347.000; Thu, 12 Dec 2019 11:15:24 +0100 From: Tomas Engin To: "freebsd-stable@freebsd.org" Subject: Re: 11.3->12.1 upgrade, pwd db not rehashed after adding ntpd user? Thread-Topic: 11.3->12.1 upgrade, pwd db not rehashed after adding ntpd user? Thread-Index: AQHVsI3AgA0M7FpeoEqTXTrtykeXNKe13Y8AgABrFag= Date: Thu, 12 Dec 2019 10:15:23 +0000 Message-ID: <1576145930466.55454@teleservice.net> References: , <20191212045046.GA87026@geeks.org> In-Reply-To: <20191212045046.GA87026@geeks.org> Accept-Language: en-CA, sv-SE, en-US Content-Language: en-CA X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.168.219.66] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Rspamd-Queue-Id: 47YV6p5gptz4MZ1 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=teleservice.net; spf=pass (mx1.freebsd.org: domain of tomas.engin@teleservice.net designates 85.30.129.128 as permitted sender) smtp.mailfrom=tomas.engin@teleservice.net X-Spamd-Result: default: False [-1.80 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:85.30.129.128]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; DMARC_POLICY_ALLOW(-0.50)[teleservice.net,none]; RCVD_IN_DNSWL_NONE(0.00)[128.129.30.85.list.dnswl.org : 127.0.10.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; IP_SCORE(-0.01)[country: SE(-0.03)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:34244, ipnet:85.30.128.0/18, country:SE]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2019 10:15:33 -0000 I've had similar problems with 11.3 and 12.0 (unsure of patchlevel) when ad= ding users using Ansible. Had to add a step in our script that runs pwd_mkd= b after each user is added to make sure it is reliable. =0A= ________________________________________=0A= From: owner-freebsd-stable@freebsd.org o= n behalf of Doug McIntyre =0A= Sent: December 12, 2019 05:50=0A= To: Mel Pilgrim=0A= Cc: freebsd-stable@freebsd.org=0A= Subject: Re: 11.3->12.1 upgrade, pwd db not rehashed after adding ntpd user= ?=0A= =0A= On Wed, Dec 11, 2019 at 05:44:27PM -0800, Mel Pilgrim wrote:=0A= > I used freebsd-update to upgrade several 11.3-p5 systems to 12.1-p1.=0A= > The etc update process added the ntpd/ntpd user/group. It showed the=0A= > line changes in the plaintext passwd/group files, but the process=0A= > appears to omit the pwd_mkdb step.=0A= >=0A= > After the upgrade, ntpd fails to start:=0A= >=0A= > # service ntpd start=0A= > Starting ntpd.=0A= > su: unknown login: ntpd=0A= > /etc/rc.d/ntpd: WARNING: failed to start ntpd=0A= >=0A= > Running the usual pwd_mkdb command fixes the issue.=0A= =0A= I've had varied results with the same thing from 11.2 to 12.1.=0A= Sometimes it works, oftentimes it does not. pwd_mkdb does fix it=0A= up, but would be nice to not have to do that.=0A= _______________________________________________=0A= freebsd-stable@freebsd.org mailing list=0A= https://lists.freebsd.org/mailman/listinfo/freebsd-stable=0A= To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"= =0A= From owner-freebsd-stable@freebsd.org Fri Dec 13 20:59:30 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B6A371D6C09 for ; Fri, 13 Dec 2019 20:59:30 +0000 (UTC) (envelope-from marcnarc@gmail.com) Received: from mail-qk1-x744.google.com (mail-qk1-x744.google.com [IPv6:2607:f8b0:4864:20::744]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47ZNMP6qF4z4VjP for ; Fri, 13 Dec 2019 20:59:29 +0000 (UTC) (envelope-from marcnarc@gmail.com) Received: by mail-qk1-x744.google.com with SMTP id d202so377130qkb.1 for ; Fri, 13 Dec 2019 12:59:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=ObnD4pNZ3WNFaV6Eqi4FwpUjWtM0/18LIYRWXZHjEDE=; b=u+4f9oCu+FFJl1oW243aio7rQRs3bjyEV0zFxqrhJrw8zJtkAJvGZsxNpen/iTjU2v Q806mMAqeYDT7UZVOgRD44e1qcmkyBEi01qo6j3cocSXouXeiFBELTumSg2PDYvZtlGP BqFtY/4T2xYPXLP1b1ntDntpoxcb1AKRQHm1SBhrvlomFJSgmrxFZSFty+uAlHAekOP9 2cr/hYBqmuA19HnvuZFTsrkFYmUF/odI4qxBkh1fZehByKSw7oVUEqrpM5uhq9NYnxiJ LrDC4Pe93V996jsMkzzIfVQJ5/o0NnzL93O9+754Tq1qiWqfUIYF0la2G/hvweWA/1GH YDlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ObnD4pNZ3WNFaV6Eqi4FwpUjWtM0/18LIYRWXZHjEDE=; b=CxzY5425FMoWJOH52UjXHSZzLydLNbxXiRsBJiNlQYZukqCn/yEnNre3/Nc04dIhZg 7DEylIgszwwSRG5GHwGQVLImhKJy523gW8TBr3n5bWFqDdmf706hQ6EoG6WS2qPpfwSI ZxDehygvPEKF4pUng/qQCg/gn3K82n5PWW5RgeXtpax2NyG+RfLIttYuEto569w/r5zR p4XRz3BBIkuQDSwbHh0GKa+5zj66ISeAmRKTmRz6N/ZZB8WXlBb2GDijCx/zxA8j9TEi krpP6t3IAK+CxCdz+tYYQBaI+lOd6K1RgUQzmy07875e0L7isZlGycgoVv5trVY7ZBz6 O6zA== X-Gm-Message-State: APjAAAXulkdQ0ZEpjRMflz3FWhSOgB5lqNSyTrvmGaXrAQRpKJHPib0T 2zEGxGNgzeh/3pke9T6wf1t1Tv1V X-Google-Smtp-Source: APXvYqzcNEMrFwxWNYuZ9C/SG6jIWI2FCLQ61VVI/P2cGnsHUfNWzZ0iawXhDzns8zf5ReiGrGPkmg== X-Received: by 2002:a05:620a:1273:: with SMTP id b19mr15682264qkl.42.1576270768785; Fri, 13 Dec 2019 12:59:28 -0800 (PST) Received: from [10.10.1.32] ([192.252.130.194]) by smtp.gmail.com with ESMTPSA id 4sm3197768qki.51.2019.12.13.12.59.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 13 Dec 2019 12:59:27 -0800 (PST) From: Marc Branchaud Subject: Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 To: Eugene Grosbein , Mark Martinec , freebsd-stable@freebsd.org References: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> <0F5FCC70-EADB-4F9E-A391-F1A73BE5608F@me.com> <1543954753.1860.243.camel@freebsd.org> <53ceda24-fa1b-8546-3511-bd500b440dfe@digiware.nl> <4c4019102b63054f8de93324dba0e776@ijs.si> <998f886a-7498-7268-75cf-4e767835db82@grosbein.net> Message-ID: Date: Fri, 13 Dec 2019 15:58:20 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <998f886a-7498-7268-75cf-4e767835db82@grosbein.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 47ZNMP6qF4z4VjP X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=u+4f9oCu; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of marcnarc@gmail.com designates 2607:f8b0:4864:20::744 as permitted sender) smtp.mailfrom=marcnarc@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.28), ipnet: 2607:f8b0::/32(-2.20), asn: 15169(-1.91), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 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, 13 Dec 2019 20:59:30 -0000 On 2019-12-10 10:16 p.m., Eugene Grosbein wrote: > 10.12.2019 23:08, Mark Martinec пишет: >> 2019-12-10 16:35, Marc Branchaud wrote: >> >>> On 2019-12-10 9:18 a.m., Mark Martinec wrote: >>>> Commenting on a thread from 2018-12 and from 2019-09-20, with my solution >>>> to the boot problem at the end, in case anyone is still interested. >>> >>> Thank you very much for this. A couple of questions: >>> >>> (1) Why do you say "raw devices for historical reasons"? Glancing >>> through the zpool man page and the Handbook, I see nothing >>> recommending or requiring GPT partitions. >> >> Apparently using raw devices for zpool is now discouraged, >> although I don't think it has ever become officially unsupported. > > Loader bugs do not mean that "using raw devices for zpool is now discouraged". Glad to hear that! Should there be a PR for this issue? (A quick Bugzilla search for "zpool gpt boot" found nothing...) M. From owner-freebsd-stable@freebsd.org Sat Dec 14 01:29:52 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5D2081DD15C for ; Sat, 14 Dec 2019 01:29:52 +0000 (UTC) (envelope-from b@sashk.xyz) Received: from forward501o.mail.yandex.net (forward501o.mail.yandex.net [37.140.190.203]) (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 47ZVML3pqFz3JCQ for ; Sat, 14 Dec 2019 01:29:50 +0000 (UTC) (envelope-from b@sashk.xyz) Received: from mxback7j.mail.yandex.net (mxback7j.mail.yandex.net [IPv6:2a02:6b8:0:1619::110]) by forward501o.mail.yandex.net (Yandex) with ESMTP id 9291C1E800E5; Sat, 14 Dec 2019 04:29:47 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback7j.mail.yandex.net (mxback/Yandex) with ESMTP id nxclsCYb7d-TkrmiOn0; Sat, 14 Dec 2019 04:29:46 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sashk.xyz; s=mail; t=1576286986; bh=fViUyLS6YOuQdazLe7KyA6rQDmugaG5h1uMYZpcdWeA=; h=References:Date:Message-Id:Subject:In-Reply-To:To:From; b=pwFz8E0gfFi7I9PkJGFUzRPZOWpGaKXDpn56Noj/MOAIz/NZmZOTVaWZaxx6mpl5H Tpyutnh9mq03dBAVhHFek+o5SE91xfStK5UHLbL0L7saBsN7X2HABBdb6HmjYSIe69 qj+FezSA6W7gJV4ap8yau1mStYvIQcT/uYLGuYP4= Received: by iva8-03ad76494624.qloud-c.yandex.net with HTTP; Sat, 14 Dec 2019 04:29:46 +0300 From: sashk To: Marc Branchaud , Eugene Grosbein , Mark Martinec , "freebsd-stable@freebsd.org" In-Reply-To: References: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> <0F5FCC70-EADB-4F9E-A391-F1A73BE5608F@me.com> <1543954753.1860.243.camel@freebsd.org> <53ceda24-fa1b-8546-3511-bd500b440dfe@digiware.nl> <4c4019102b63054f8de93324dba0e776@ijs.si> <998f886a-7498-7268-75cf-4e767835db82@grosbein.net> Subject: Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 13 Dec 2019 20:29:46 -0500 Message-Id: <12248491576286986@iva8-03ad76494624.qloud-c.yandex.net> Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-Rspamd-Queue-Id: 47ZVML3pqFz3JCQ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=sashk.xyz header.s=mail header.b=pwFz8E0g; dmarc=none; spf=pass (mx1.freebsd.org: domain of b@sashk.xyz designates 37.140.190.203 as permitted sender) smtp.mailfrom=b@sashk.xyz X-Spamd-Result: default: False [-2.81 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[sashk.xyz:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:37.140.128.0/18]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sashk.xyz]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[sashk.xyz:+]; IP_SCORE(-1.71)[ipnet: 37.140.128.0/18(-4.79), asn: 13238(-3.78), country: RU(0.01)]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_IN_DNSWL_LOW(-0.10)[203.190.140.37.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13238, ipnet:37.140.128.0/18, country:RU]; RCVD_TLS_LAST(0.00)[]; SUSPICIOUS_RECIPS(1.50)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2019 01:29:52 -0000 I hit this issue about year ago and Toomas Soome was able to figure out what was causing this and fixed in the https://svnweb.freebsd.org/base?view=revision&revision=342151 I believe this got into 12.1. -Aleks 13.12.2019, 15:59, "Marc Branchaud" : > On 2019-12-10 10:16 p.m., Eugene Grosbein wrote: >>  10.12.2019 23:08, Mark Martinec пишет: >>>  2019-12-10 16:35, Marc Branchaud wrote: >>> >>>>  On 2019-12-10 9:18 a.m., Mark Martinec wrote: >>>>>  Commenting on a thread from 2018-12 and from 2019-09-20, with my solution >>>>>  to the boot problem at the end, in case anyone is still interested. >>>> >>>>  Thank you very much for this. A couple of questions: >>>> >>>>  (1) Why do you say "raw devices for historical reasons"? Glancing >>>>  through the zpool man page and the Handbook, I see nothing >>>>  recommending or requiring GPT partitions. >>> >>>  Apparently using raw devices for zpool is now discouraged, >>>  although I don't think it has ever become officially unsupported. >> >>  Loader bugs do not mean that "using raw devices for zpool is now discouraged". > > Glad to hear that! > > Should there be a PR for this issue? (A quick Bugzilla search for > "zpool gpt boot" found nothing...) > >                 M. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"