Date: Fri, 29 Dec 2023 13:30:32 +0100 From: "Alfonso S. Siciliano" <alfix86@gmail.com> To: freebsd-current@freebsd.org Subject: Re: Checksum Error on installer (3 iso images in CURRENT) Message-ID: <df1560d8-3f1f-4264-953a-46cb30a08719@gmail.com> In-Reply-To: <BN0PR20MB3750675AD9D7C7FF8B9E6A35A29DA@BN0PR20MB3750.namprd20.prod.outlook.com> References: <BN0PR20MB3750675AD9D7C7FF8B9E6A35A29DA@BN0PR20MB3750.namprd20.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29/12/2023 05:46, Christopher Davidson wrote: > Hi FreeBSD mailing list, > > I have recently started to look at the CURRENT isos, for installation in > a virtualbox, and while trying to install these images I have received > verification issues with the checksums. > > Problem: FreeBSD installer will error out of the installer upon > verification of checksums, they do not align with the checksum files in > the directory: > https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/ > <https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/150/>; > > Steps to replicate: > > 1. Create a virtualbox profile with freebsd > 2. Attach one of the below iso images > 3. Run the installation > 4. Select keymap > 5. Select partition setup (UFS) > 6. Select packages to install > 7. Program starts verifying the base package and comes back with the > error message > > I have confirmed this with some people on the liberachat IRC server, > under #freebsd and this is not an isolated event. > > The 3 iso images in question are: > > * FreeBSD-15.0-CURRENT-amd64-20231216-ca39f23347e1-266973-bootonly.iso > * FreeBSD-15.0-CURRENT-amd64-20231228-fb03f7f8e30d-267242-disc1.iso > * FreeBSD-15.0-CURRENT-amd64-20231223-dac33a65b965-267058-bootonly.iso > > Here are the respective checksums for each of these files: > > CHECKSUM.SHA256-FreeBSD-15.0-CURRENT-amd64-20231216-ca39f23347e1-266973 > > SHA256 > (CHECKSUM.SHA256-FreeBSD-15.0-CURRENT-amd64-20231216-ca39f23347e1-266973) = 827182ccbfbce984c969790e7aac43828dffc4a21d43e855c91bac03f29dc74e > > SHA256 > (FreeBSD-150-CURRENT-amd64-20231216-ca39f23347e1-266973-bootonly.iso) = > fdd8870549474f38d35665c330d209df7733aa8608630845471685b291c06746 > > CHECKSUM.SHA256-FreeBSD-15.0-CURRENT-amd64-20231223-dac33a65b965-267058 > > SHA256 > (CHECKSUM.SHA256-FreeBSD-15.0-CURRENT-amd64-20231223-dac33a65b965-267058) = 60f01c27aa02acb47cab7dec58119f34e7215c3656b8486854bc64217cdfe3bb > > SHA256 > (FreeBSD-15.0-CURRENT-amd64-20231223-dac33a65b965-267058-bootonly.iso) = > abdd81c253c651bbc10e3db1b97b8b111f73b3f657f729e37cdbe975de0dc056 > > CHECKSUM.SHA256-FreeBSD-15.0-CURRENT-amd64-20231228-fb03f7f8e30d-267242 > > SHA256 > (CHECKSUM.SHA256-FreeBSD-15.0-CURRENT-amd64-20231228-fb03f7f8e30d-267242) = 83698ee594d56108b29e40d635671c7a2de6ada2af636ef5254eafbd35e95e96 > > SHA256 > (FreeBSD-150-CURRENT-amd64-20231228-fb03f7f8e30d-267242-disc1.iso) = > 2deb850673f148cf1ab269175ddf40448e6a96b331b4ca0027f8abe16b3edfa0 > > If any further information/clarification is required, please do let me know. > > Kind Regards, > > Chris > Hi Chris, I had the same problem some time ago because I used to test iso/bsdinstall every day. Fortunately, the re@ team explained the cause and the solution to me. The new development snapshot builds are propagated to the mirror. It is non-atomic, so there is a bit of a possible race condition. (This happens once a week, unless there is some sort of build failure.) You could subscribe to the freebsd-snapshots@ mailing list if you want to be notified when the propagation is complete. Alfonso
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?df1560d8-3f1f-4264-953a-46cb30a08719>