From nobody Wed Nov 8 07:25:36 2023 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 4SQGpK2Rbqz50GV4 for ; Wed, 8 Nov 2023 07:25:45 +0000 (UTC) (envelope-from SRS0=284H=GV=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 4SQGpK0Ffhz4JLk for ; Wed, 8 Nov 2023 07:25:44 +0000 (UTC) (envelope-from SRS0=284H=GV=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Wed, 8 Nov 2023 08:25:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1699428337; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ZKrVwhkIRykhkO4eFzJOjNDtZY6gCAhzYXAzy1Zv/k4=; b=mwCC68RaJY3x2LM5yccgOXzH1vz0XCgPaLsLCKgiGeFZipAj9qdVZj/zhHQmUISZRM9bPB U4plPteGAtVFQS/V4HucntF8eFMAsg0SdL3R0rrr9XwU/n9ltSMy8mU1heninMWX4pZ2Eh Z2ghzjKsAxeUtMK6pZFwop6o5Bz4/Fsk46/diQsps1lLbKB8uU2SHyjEyQIVogtLWYoku4 SPvMGTS+phIlKuIwrqsk0c8rNEjO4i5qBPX/W0Fo0zhlLLr63EjGBP1t06YSFk4VJg4Bz8 5SovaMtwSKsb41ySzJNq5iEIk8Ea/EP7yOtwa6UhOhhbYc6tchi3K07tPRYrsQ== From: Ronald Klop To: Jason Tubnor Cc: Freebsd-stable List Message-ID: <1625115570.9056.1699428336994@localhost> In-Reply-To: <20231107213423.Horde.vBiRSZqTTo69qkWRAQkCTCG@drive.tubnor.net> References: <1964125924.4915.1699386725365@localhost> <20231107213423.Horde.vBiRSZqTTo69qkWRAQkCTCG@drive.tubnor.net> Subject: Re: failed 13.2 -> 14-RC4 upgrade on RPI3 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: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9055_987433704.1699428336925" X-Mailer: Realworks (679.137) Importance: Normal X-Priority: 3 (Normal) 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:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4SQGpK0Ffhz4JLk ------=_Part_9055_987433704.1699428336925 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Van: Jason Tubnor Datum: dinsdag, 7 november 2023 22:34 Aan: Freebsd-stable List , Ronald Klop Onderwerp: Re: failed 13.2 -> 14-RC4 upgrade on RPI3 >=20 > =20 >=20 > =20 >=20 > "Ronald Klop" ronald-lists@klop.ws =E2=80=93 8 November 2023 6:52 AM > =20 >>=20 >> Hi, >>=20 >> Tried to update my RPI3-on-UFS from 13.2-RELEASE to 14-RC4. >>=20 >>=20 >> comm: INDEX-NEW: No such file or directory >> rm: modifiedfiles: No such file or directory >> rm: INDEX-PRESENT: No such file or directory >>=20 >> No updates needed to update system to 14.0-RC4-p0. >> touch: f465c3739385890c221dff1a05e578c6cae0d0430e46996d319db7439f884336-= install/kernelfirst: No such file or directory >> To install the downloaded upgrades, run "/usr/sbin/freebsd-update instal= l". >> [root@rpi3 ~]# freebsd-update install >> No updates are available to install. >> Run '/usr/sbin/freebsd-update fetch' first. >> [root@rpi3 ~]# >>=20 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>=20 >> Does this make sense to anybody? >> Do I have old cruft lying around in some directory which conflicts with = the upgrade? >> It didn't give an error while downloading all 55000+ patches. >>=20 >> Regards, >> Ronald. >> =20 >=20 > =20 >=20 > Did you: >=20 > =20 >=20 > freebsd-update fetch install && shutdown -r now=20 >=20 > =20 >=20 > Before you ran the 14 upgrade process? There were some recent errata that= corrected issues in preparation of 14 upgrades. >=20 > =20 >=20 > Cheers, >=20 > =20 >=20 > Jason. >=20 > =20 >=20 Hi, I think I know what happened. I have this line in cron which I forgot to di= sable: "@daily freebsd-update cron && freebsd-update updatesready > /dev/null && f= reebsd-update install" On my RPI3 a full upgrade takes a while so I let it run overnight. Last nig= ht I tried again and the cron job now gave me error mails. That is how I fo= und out. Now running an upgrade with this line commented out. Regards, Ronald. =20 ------=_Part_9055_987433704.1699428336925 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Van: Jason Tubnor <jason@tubnor.net>
Datum: dinsdag, 7 november 2023 22:34
Aan: Freebsd-stable List <stable@freebsd.org>, Ronal= d Klop <ronald-lists@klop.ws>
Onderwerp: Re: failed 13.2 -> 14-RC4 upgrade on RPI3

 

 

"Ronald Klop" ronald-lists@klop.ws =E2=80=93 8 Novem= ber 2023 6:52 AM
 

Hi,

Tried to update my RPI3-on-UFS from 13.2-RELEASE to 14-RC4.


comm: INDEX-NEW: No such file or directory
rm: modifiedfiles: No such file or directory
rm: INDEX-PRESENT: No such file or directory

No updates needed to update system to 14.0-RC4-p0.
touch: f465c3739385890c221dff1a05e578c6cae0d0430e46996d319db7439f884336-ins= tall/kernelfirst: No such file or directory
To install the downloaded upgrades, run "/usr/sbin/freebsd-update install".=
[root@rpi3 ~]# freebsd-update install
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.
[root@rpi3 ~]#

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Does this make sense to anybody?
Do I have old cruft lying around in some directory which conflicts with the= upgrade?
It didn't give an error while downloading all 55000+ patches.

Regards,
Ronald.
 

 

Did you:

 

freebsd-update fetch install && shutdown -r = now 

 

Before you ran the 14 upgrade process? There were so= me recent errata that corrected issues in preparation of 14 upgrades.

 

Cheers,

 

Jason.

 



Hi,

I think I know what happened. I have this line in cron which I forgot to di= sable:
"@daily freebsd-update cron && freebsd-update updatesready > /de= v/null && freebsd-update install"

On my RPI3 a full upgrade takes a while so I let it run overnight. Last nig= ht I tried again and the cron job now gave me error mails. That is how I fo= und out.

Now running an upgrade with this line commented out.

Regards,
Ronald.
  ------=_Part_9055_987433704.1699428336925--