On 8/2/25 21:50, Titus Newswanger wrote:
On 8/2/25 22:44, David Christensen wrote:
5. Verify the computed SHA256 checksum appears in the downloaded
SHA512SUMS file:
I've been meaning to learn how to sha512sum after it is written to disk.
Now I've got it. Here are my results:
on the older usb disk that worked, sha512sum matched
on the new faulty disk, after writing with dd, sha512sum did not match
on the same faulty disk, after writing with "Disk Image Writer" and I
successfully installed trixie on a machine, I checked the usb disk and
sha512sum did not match 🙁 I thought I was finished with that server.
Now I need to decide if I will start over or just leave it and hope for
the best. Considering it is a mini pc used as a headless print server to
connect a little used usb only printer to my network, I think I will
just place a note in /etc/motd like:
This copy of Debian was installed with a broken installer, expect anything!
Thanks
Beware that the Debian installer (d-i) can change the contents of the
USB flash drive when it runs (!). So, you must do the checksum
immediately after burning the ISO to the USB flash drive.
So, a failed checksum of a d-i USB flash drive that has been run does
not prove a faulty d-i or a bad install.
I reported the above on this list sometime in the past (few years?), but
am unable to locate the thread at this time. I seem to recall the
report was confirmed, but the details were not where I had guessed.
I have burned my most recent d-i images to CD-R discs, so that the bytes
are fixed and I can validate the d-i image whenever I like (such as
before doing an install).
David
