How did the need for flash drive verification arise?
Based on errors I encountered during my testing, I discovered that ISO files can sometimes be written incorrectly to flash drives. Even if the writing software indicates that the process was successful, it may not actually detect errors. An incorrectly written flash drive typically reveals itself when booting into a live environment, during installation, or even after the installation is complete—sometimes, it may not even be able to boot into the live environment at all. While error messages might appear on the screen between the BIOS stage and the login session, they often scroll by so quickly that they go unnoticed. In short, verifying the ISO file alone is not enough; verifying the flash drive onto which the file has been written is also necessary to ensure everything is correct.
For this reason, creating such a verification tool became essential.
The verification tool, which I have named "Bes-usbverify," supports 58 languages. It runs using the Yad framework and is installed in the user's home directory. It calculates the SHA256 checksum for both the ISO file and the flash drive it was written to; if the two values match, the flash drive has been written correctly. If they do not match, do not use the drive. Instead, format the flash drive using GParted or Mintstick, and continue the process until the verification values match.
Download the file here
Besgnulinux Flash drive verification
Screenshot of the flash drive verification tool
No comments:
Post a Comment