From nobody Mon Sep 16 22:39:53 2024 X-Original-To: stable@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 4X70Gr2fVbz5W2Vr for ; Mon, 16 Sep 2024 22:40:04 +0000 (UTC) (envelope-from pete@twisted.org.uk) Received: from toybox.twisted.org.uk (toybox.twisted.org.uk [178.250.76.50]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X70Gq3WF5z4PL7 for ; Mon, 16 Sep 2024 22:40:03 +0000 (UTC) (envelope-from pete@twisted.org.uk) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=twisted.org.uk header.s=tbx-short header.b=JR0LSKZa; dmarc=pass (policy=none) header.from=twisted.org.uk; spf=pass (mx1.freebsd.org: domain of pete@twisted.org.uk designates 178.250.76.50 as permitted sender) smtp.mailfrom=pete@twisted.org.uk DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=twisted.org.uk; s=tbx-short; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:To:Subject:MIME-Version:Date:Message-ID:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=XjcAIup3BL59uncUfYVHzWM6qmzCKAO8tfb3cBR8CyA=; t=1726526403; x=1727390403; b=JR0LSKZa73FosAUSCi9bVDtUOgkhKkiMcJqbSi7lfkeO02On9gPGGSRpyWozOEJEI+8YdAcqnoU qPkUfO++YcimFT3AtYj556jMj0x4sBTXDJU4T0/64eCTt8BKiHg76bTH7s42cRNrYm27QUvc5o34/ RNyP6e4/jtCqZViWejU=; Received: from mailnull by toybox.twisted.org.uk with spamc-scanned (Exim 4.96.2 (FreeBSD)) (envelope-from ) id 1sqKNu-000PKZ-0J for stable@freebsd.org; Mon, 16 Sep 2024 22:39:54 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on toybox.twisted.org.uk X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=4.0.0 X-Spam-Score: -1.0 () Received: from balta.twisted.org.uk ([2001:470:6cc4:1::57]) by toybox.twisted.org.uk with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.96.2 (FreeBSD)) (envelope-from ) id 1sqKNt-000PKU-3B for stable@freebsd.org; Mon, 16 Sep 2024 22:39:54 +0000 Message-ID: Date: Mon, 16 Sep 2024 23:39:53 +0100 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: 13.3R's installworld killed system--please help! To: stable@freebsd.org References: <202409150523.48F5NNVj003365@sdf.org> Content-Language: en-GB From: Pete French In-Reply-To: <202409150523.48F5NNVj003365@sdf.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-spamc-toybox: true X-transport-toybox: lookuphost X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.987]; DMARC_POLICY_ALLOW(-0.50)[twisted.org.uk,none]; R_SPF_ALLOW(-0.20)[+ip4:178.250.76.50/32]; R_DKIM_ALLOW(-0.20)[twisted.org.uk:s=tbx-short]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; SUBJECT_ENDS_EXCLAIM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12290, ipnet:178.250.72.0/21, country:GB]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[stable@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[twisted.org.uk:+] X-Rspamd-Queue-Id: 4X70Gq3WF5z4PL7 On 15/09/2024 06:23, Scott Bennett wrote: > Thank you very much for this suggestion! It hadn't crossed my mind, > likely because I thought I had thrown all those old CD-Rs and DVD+/-Rs away > when I moved to a different apartment in February. After seeing your message, > though, I went looking. In the very first place I checked, lo and behold, I > found a DVD-R I had labeled "PC-BSD 8.2 (64-bit) Installer, LiveCD, and Repair > Disk" and "PCBSD8.2-x64-DVD.iso Disk 1 of 1". 8-D So I then did as you > suggested. Unfortunately, it made no change in the resulting boot behavior. > :-( At least I now know I have such a disk at hand to try such things. Am gald you found the disc - I was also going to say that I am quite happy to burn one for you and post it, though thats a slow method of acquiring a CD! I remember posting someone in the US a copy of Minix on 5.25 floppies back in 1989, and it took a while to get there, but did indeed boot on arrival. Am dissapointed that the updated boot sectors didnt help though. I would have bet money on that being the issue (and lost the bet!) > Thank you both for that reassuring information. After all this, it is > now clear that the boot code was not the problem and that I *still* have no > idea what went wrong. I do not remember ever having an upgrade from source > actually fail before this experience. Even the trickiest one many years ago-- > a merged procedure to upgrade from i386 to amd64 in place and from, I *think*, > 9.x to 10.x, went well. (Trust me, I was as nervous as I would be on a > non-precision approach in nighttime IMC in a non-radar, mountainous environment > with flashes of light around me (yes, that happened to me once), but I had > planned all the steps carefully, and my combined procedure was successful.) !!!! umm, yeah, I really would not like to try that! not that I would, never having got an IMC rating, but the little bits I did with foggles on convinced me that this was not the kind of flying I wanted to do ;) i386 -> amd64, however, I did that, and that worked fine, despite also being very nervous. I;ve only ever done source upgrades, going right back to FreeBSD 3, and the only times it failed to boot were when I forgot to upgrade the boot code for a newer ZFS pool. > rolled every file system back to that snapshot. After reinserting the drives > into the tower, I booted it and ... my 12.4-RELEASE-p2 system was up and > running again. What a relief! Aha! Fantastic! OK, so, you rolled back the filesystems .... but left the boot code intact ? So this is now running your old filesystems but booting using the updated 14.2 code that you wrote using PC-BSD, yes ? > So I'm back to where I was before attempting the upgrade. It's a good > system, but it is out of support, so thank you very much to everyone who > responded anyway. I am pondering what my next step should be. OK, I have forgotten the start of this thread, but you went from the last version of 12 to a build of 13.0 release, which you compiled under the installed 12? How far did it get in the boot process - did it even find the pool and try and load the kernel, or not even that far? If it is now booting off the installed latest boot code, then we know it can run code which should find the pool. Do you have the 'bootfs' property set on the pool ? This is a puzzle - I've done this repeatedly, going from 3 all the way to 14, and its always worked. -pete.