Date: Fri, 17 Mar 2023 19:04:23 -0700 From: Mark Millard <marklmi@yahoo.com> To: Colin Percival <cperciva@freebsd.org> Cc: =?utf-8?Q?T=C4=B3l_Coosemans?= <tijl@FreeBSD.org>, Current FreeBSD <freebsd-current@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, Baptiste Daroussin <bapt@FreeBSD.org> Subject: Re: I just updated to main-n261544-cee09bda03c8 based (via source) and now /etc/machine-id and /var/db/machine-id disagree ; more Message-ID: <91950753-BDE0-45D5-B0B9-42782BD75C47@yahoo.com> In-Reply-To: <D8F42EA8-6105-4E0A-961F-916D61589B98@yahoo.com> References: <DCAD189B-1CBA-4D5B-B6DB-948A77AC723D.ref@yahoo.com> <DCAD189B-1CBA-4D5B-B6DB-948A77AC723D@yahoo.com> <2cf7d953-2493-9673-5ea3-fba22c694015@freebsd.org> <20230317181547.4d75e897@hal.tijl.coosemans.org> <C18AED00-6CCF-4140-A0AE-B947521E422A@yahoo.com> <D8F42EA8-6105-4E0A-961F-916D61589B98@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 17, 2023, at 18:24, Mark Millard <marklmi@yahoo.com> wrote: > The 13.1-RELEASE (snapshot) to 13.2-RC3 freebsd-update's > upgrade sequence did not go well relative to my being > prompted to do the right thing to establish /etc/machine-id . > After the last reboot (kernel upgrade, presumably) it had me > continue with. . . >=20 > # /usr/sbin/freebsd-update install > src component not installed, skipped > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > Installing updates... > install: ///var/db/etcupdate/current/etc/rc.d/growfs_fstab: No such = file or directory > install: ///var/db/etcupdate/current/etc/rc.d/var_run: No such file or = directory > install: ///var/db/etcupdate/current/etc/rc.d/zpoolreguid: No such = file or directory > Scanning //usr/share/certs/blacklisted for certificates... > Scanning //usr/share/certs/trusted for certificates... > rmdir: ///usr/tests/usr.bin/timeout: Directory not empty > done. > root@generic:~ # cat /etc/hostid /etc/mach* > cat: No match. >=20 > It did not indicate the need for another reboot to > end up with a /etc/machine-id file. >=20 > I tried "shutdown -r now" anyway. It did establish > an /etc/machine-id file during the reboot: >=20 > # ls -Tld /etc/hostid /etc/machine-id=20 > -rw-r--r-- 1 root wheel 37 May 12 08:46:21 2022 /etc/hostid > -rw-r--r-- 1 root wheel 33 May 13 09:46:56 2022 /etc/machine-id >=20 > So the basic implementation is operational but just > lacks an indication of the need to reboot again. >=20 > The date/time is because it is a RPi4B context (no > time of its own) and time is not automatically being > established via ntp, apparently. (I did not make such > adjustments to the snapshot before starting the > upgrade.) >=20 > I do not know if any of the "install: ///var/db/etcupdate/ . . . " > lines or the rmdir line are important. >=20 > It earlier indicated 5708 patches were fetched and that 377 > files were as well. Using the likes of: = http://ftp3.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/13.2/FreeBSD-13.2-= RC3-arm64-aarch64-RPI.img.xz directly seems to produce installations with a constant: kenv -q smbios.system.uuid 30303031-3030-3030-3265-373238346338 that ends up being what is used for /etc/hostid . It looks like this traces back to the U-Boot involvement in the boot sequence: # kenv | grep smbios hint.smbios.0.mem=3D"0x39c2b000" smbios.bios.reldate=3D"10/01/2022" smbios.bios.revision=3D"22.10" smbios.bios.vendor=3D"U-Boot" smbios.bios.version=3D"2022.10" smbios.chassis.maker=3D"Unknown" smbios.chassis.type=3D"Desktop" smbios.planar.maker=3D"Unknown" smbios.planar.product=3D"Unknown Product" smbios.socket.enabled=3D"1" smbios.system.maker=3D"Unknown" smbios.system.product=3D"Unknown Product" smbios.system.serial=3D"REDACTED" smbios.system.uuid=3D"30303031-3030-3030-3265-373238346338" smbios.version=3D"3.0" =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91950753-BDE0-45D5-B0B9-42782BD75C47>