Date: Mon, 05 Sep 2022 06:48:15 +1000 From: Ian Smith <smithi@nimnet.asn.au> To: Doug Denault <doug@safeport.com>,freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD 12.2 can not be upgraded Message-ID: <0C6B8CFB-74A8-4547-8E17-32F264B4ECE7@nimnet.asn.au> In-Reply-To: <alpine.BSF.2.00.2209041200310.67914@bucksport.safeport.com> References: <alpine.BSF.2.00.2209041200310.67914@bucksport.safeport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 September 2022 3:05:03 am AEST, Doug Denault <doug@safeport=2Ecom> wro= te: > There was a long thread on this=2E My observations and questions are > more=20 > about how to update production systems=2E My long standing update path > is to=20 > update my FreeBSD workstations=2E If that goes okay we some servers on > out=20 > LAN that we update next=2E >=20 > I ran `freebsd-update -r 12=2E3-RELEASE upgrade` which converted my > laptop=20 > essentially into a paperweight by the introduction a bad copy of=20 > ld-elf=2Eso=2E1=2E The system would boot, but most useful commands (thi= nk > cp)=20 > exited with an error=2E This is all documented via google with no > successful=20 > work arounds that I could fine=2E What you can not do is > `freebsd-update=20 > rollback`=2E I though I could maybe fix this by going to single user > and=20 > overwriting ld-elf=2Eso=2E1=2E This can not be done as all commands dep= end > on=20 > this file=2E >=20 > I created image files from: >=20 > FreeBSD-12=2E3-RELEASE-amd64-dvd1=2Eiso (4+GB) > FreeBSD-12=2E3-RELEASE-amd64-memstick=2Eimg ~1GB >=20 > Neither of these images are self contained=2E Both install 12=2E3 > correctly but=20 > by downloading the OS from a mirror site of your choosing=2E No Doug, I installed 12=2E3-R from the dvd1 image, deliberately without an= y network connection=2E The install itself went fine, including the source= and ports tree at that time=2E > Is there a path=20 > thought the dvd1 install that does something with the extra 3GB of > data? Sadly, the 2=2E6GB of packages is initially inaccessible, firstly due to a= broken symlink on the image, and subsequently due to needing three patches= to bsdconfig=2E I have got it working but need to run another install to = verify; that's another story=2E > Does the dvd1=2Eiso image have to be burned to a DVD? No, as advertised on the release announcement page, the image can be simpl= y dd'd to a USB memstick=2E https://www=2Efreebsd=2Eorg/releases/12=2E3R/announce/ The "livefs" mode works fine, maybe you can sort out your broken bits havi= ng booted into that and then mounting your disk/s? > My am not sure what is the philosophy of deleting the supporting > files so=20 > quickly=2E Other than making a system from backup is there a way to > install=20 > an older version? Not sure what you mean=2E I don't think older installation images are mis= sing, are they? There's been discussion on forums about EOL package reposi= tories being deleted, due to insufficient diskspace maybe? > And lastly does 12=2E2 --> 13=2Ex work? Haven't tried=2E 12=2E4 is coming and I'm hoping to help get the broken d= vd1 packages installation fixed by then=2E > If intent if all this is to protect me from myself, what protects me > from=20 > the developers? There is certainly no Joy in this=2E I understand frustration =2E=2E=2E I can say that clearly nobody tested tr= ying to install the 12=2E3-R dvd1 packages using bsdconfig with no network= =2E cheers, Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0C6B8CFB-74A8-4547-8E17-32F264B4ECE7>