About File Checksum
- 1. Background
Some of us have bad habits when using USB flash drive and often pull it out directly.
If you pull the USB drive out immediately after finish copy a big ISO file, most probably the file in the USB will be corrupted. Because alough it seems that the copy operation has been finished, there may be still some data is in the system cache and not yet fully flushed to the USB drive. As a result, you may run into problems when you boot the corrupted ISO file.
Because Linux and Windows use different caching mechanisms, this problem is especially obvious in Linux systems, and it is very easy to cause problems.
So we should develop a good habit of using USB drive and use safe operations to remvoe the USB drive before pull it out.
Besides, we can checksum the file after copy.
- 2. Checksum
Alough you can checksum the file in the original system. But I recommend to checksum in Ventoy to avoid the interference of system cache.
- 3. Usage
Ventoy provides a hotkey
m for file checksum.
When in Ventoy's main menu, select the image file, press
m and then select the checksum type.
- 4. Checksum file compare
At the same time, if there exist a text file with name FILENAME +
.md5/.sha1/.sha256/.sha512 suffix, then Ventoy will automatically
read the checksum from the file and compare with the calculated result.
It should be noted that, the text file must have a name with an additional
.md5/.sha1/.sha256/.sha512 suffix, don't replace the old suffix with
/ISO/Linux/tails-amd64-4.23.iso /ISO/Linux/tails-amd64-4.23.iso.md5 /ISO/Linux/tails-amd64-4.23.img /ISO/Linux/tails-amd64-4.23.img.md5 /ISO/Windows/en_Windows11.iso /ISO/Windows/en_Windows11.iso.sha1 /ISO/ChromeOS/cloudready-free-92.3.4-64bit.img /ISO/ChromeOS/cloudready-free-92.3.4-64bit.img.sha256
The following two format of
.md5/.sha1/.sha256/.sha512 file are supported. (Take sha256 for example)
- 5. Screenshot