From nobody Tue Nov 21 20:30:38 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SZbcD55Kxz52F64 for ; Tue, 21 Nov 2023 20:30:52 +0000 (UTC) (envelope-from 4250.82.1d5060005c96531.501981784d93cf91648cf5a2a4fed182@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (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 4SZbcD3Chqz3Nqc for ; Tue, 21 Nov 2023 20:30:52 +0000 (UTC) (envelope-from 4250.82.1d5060005c96531.501981784d93cf91648cf5a2a4fed182@email-od.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1700598652; x=1703190652; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info:subject:to:from:cc:reply-to; bh=ZLWZgcyn4UtmP+p8+q5To8ROhChsE0rGUYdpwSWTw5U=; b=rDQoG22fClNYX2cViPYLmtRMkmu+X2wQU1LKoDlrr8HHPIOifHQMC+5H/cQgWEWFjkw7HWwsIcNubhYRfdjdBHPnzw04mWKV+ydzxOIGV+Cmz6XWEBl493gKEKFH0oUwypnIe7Jvf2aFwvW7Bc2+0SOgBYGVD63pqCkACitJRog= X-Thread-Info: NDI1MC4xMi4xZDUwNjAwMDVjOTY1MzEuZnJlZWJzZC1xdWVzdGlvbnM9ZnJlZWJzZC5vcmc= Received: from r1.us-west-2.aws.in.socketlabs.com (r1.us-west-2.aws.in.socketlabs.com [142.0.190.1]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Tue, 21 Nov 2023 15:30:42 -0500 Received: from smtp.lan.sohara.org (EMTPY [185.202.17.215]) by r1.us-west-2.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Tue, 21 Nov 2023 15:30:40 -0500 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.95 (FreeBSD)) (envelope-from ) id 1r5XOI-000OaU-IR; Tue, 21 Nov 2023 20:30:38 +0000 Date: Tue, 21 Nov 2023 20:30:38 +0000 From: Steve O'Hara-Smith To: iio7@tutanota.com Cc: Freebsd Questions Subject: Re: I am sick and tired of the poor quality of documentation on FreeBSD Message-Id: <20231121203038.9484f62455034022a4689468@sohara.org> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.1) X-Clacks-Overhead: "GNU Terry Pratchett" List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7381, ipnet:142.0.176.0/22, country:US] X-Rspamd-Queue-Id: 4SZbcD3Chqz3Nqc On Tue, 21 Nov 2023 20:51:01 +0100 (CET) iio7@tutanota.com wrote: > Take a look at how it's done on OpenBSD! Take a look at have it's done on > Arch Linux! > > When there is something that is going to break something during an > upgrade, you get timely information and a step by step instruction in > what to do - BEFORE you do it! You did of course read the release notes right ? The rather good documentation provided by the FreeBSD project for each new release. Specifically this section that tells you exactly what to do and why. https://www.freebsd.org/releases/14.0R/relnotes/#upgrade Documentation is only useful if you read it! BEFORE you do things. > Something like this doesn't help! >   Pool 'zroot' has the bootfs property set, you might need to update the > boot code. See gptzfsboot(8) and loader.efi(8) for details. It's a warning not documentation, heeding it could have saved you much trouble. > I might need to update the boot code!? WTF does that even mean? It seems pretty clear that you should make sure you understand it and do what is necessary *before* you reboot. The boot code is (as the name implies) the code used to boot the system which has to be able to read the filesystem containing the OS, which it can't if that filesystem has been updated with features that the existing boot code does not support. > I never touched any boot code during installation so I don't even know > what that is! And reading those man pages did NOT help me in any way. If you had read the release notes you would know what to do, and surely the name "boot code" is sufficiently descriptive as to what it is. > So now I got a box that's borked with this beautiful message after > updating the zroot pool: AND rebooting without updating the boot code right ? > ZFS: unsupported feature: com.delphix:head_errlog > ZFS: pool zroot is not supported > Can't find /boot/zfsloader > Can't find /boot/loader > Can't find /boot/kernel/kernel Now you're going to need this article in the forums which a search would have found for you in a few seconds: You might want to thank T-Aoki and note the rather more polite way someone else who got themselves into this mess asked for help. -- Steve O'Hara-Smith