I want to install Ubuntu, and I'm switching from Windows 10.

I've heard that some people will check the integrity of the ISO image. Should I do this and if so, why?

  • @guiverc didn't see that, sorry
    – theyeetman
    Jan 27, 2021 at 0:40
  • Not a problem @theyeetman, I hadn't remembered that answer until I'd already written you the answer on this question (otherwise I'd have just marked duplicate) and I suspect my answer this time is better for your actual question, it's more up-to-date anyway (md5sums aren't used any longer which still applied when the last answer was written).
    – guiverc
    Jan 27, 2021 at 2:58

3 Answers 3


Media Checks

As KGIII said - modern releases (20.04 and later) automatically scan. I for sure let that scan occur (on the first boot of the day; I tend to skip it if rebooted in the same box on the same day).

If you don't want to check beforehand, you can switch to a terminal (post-install) and always do a

dmesg |grep squashfs

and look for errors. A standard install should find only the copyright messages when dmesg is scanned; if any other lines appear with squashfs I'd read them as the install is likely not trustworthy.

Ubuntu 23.04 Desktop

The way you verify actually varies on release, with a Ubuntu 23.04 Desktop system I'll use the following

sudo journalctl |grep casper-md5check

And what I look for is

May 11 08:37:42 ubuntu casper-md5check[3924]: Checking ./casper/install-sources.yaml..../casper/install-sources.yaml: OK
May 11 08:37:42 ubuntu casper-md5check[3924]: Checking ./casper/vmlinuz..../casper/vmlinuz: OK
May 11 08:37:47 ubuntu casper-md5check[3924]: Checking ./casper/initrd......./casper/initrd: OK
May 11 08:37:47 ubuntu casper-md5check[3924]: Checking ./boot/memtest86+x64.bin..../boot/memtest86+x64.bin: OK
May 11 08:37:47 ubuntu casper-md5check[3924]: Checking ./boot/grub/grub.cfg..../boot/grub/grub.cfg: OK
May 11 08:37:47 ubuntu casper-md5check[3924]: Checking ./boot/grub/loopback.cfg...../boot/grub/loopback.cfg: OK
May 11 08:37:47 ubuntu casper-md5check[3924]: Check finished: no errors found.
May 11 08:37:47 ubuntu systemd[1]: Finished casper-md5check.service - casper-md5check Verify Live ISO checksums.

Where the key message I look (& wait for; ie. I may need to run this command a few times as the process will continue to run as a background task) is

Check finished: no errors found.

ISO image Validation

As for ISO image validation pre-write, or How to verify your Ubuntu download, I download using zsync and it checks the integrity of the ISO image at the conclusion of download; I tend to trust that, and just do the self-scan on boot.

If using an older release (pre-20.04), I'll always also do a manual CD integrity check, primarily as the write to USB-media I've found the most troublesome (I have 10+ failures per year, even if that's a smallish percentage of writes; it's still significant).

If I download via a torrent, I tend to do a quick sha256sum check against the checksum file I downloaded using wget on a different device. I tend to perform this check on ISO image files downloaded previously anyway.

Why do it?

The checks take seconds to maybe a minute. If you have a single bit wrong, the debugging the installation or corrupted data could take hours if you're lucky, but more likely days-weeks-months.

There are generally at least one bug report filed per day (on launchpad; I monitor via #ubuntu-bugs-announce), reported by users who've been having problems with they consider a bug that would have been prevented by these checks. The bug reports are just marked INVALID and given a quick paste with a couple of lines from their dmesg output). So I see on a very regular basis users wasting hours trying to repeat processes that will never work (often over days), because they skipped these checks and thus are starting with corrupted media where problems should be expected.

I see it as a very cheap insurance.

  • I'm gonna check it then, I appreciate all the information too. This forum has been very helpful in my transfer from windows to linux. I lost access to my last account and couldn't reset the password. So I had to create a new one.
    – theyeetman
    Jan 27, 2021 at 0:45

These days, it's not as important, so long as it's one of the more modern releases. During the boot phase of the live ISO it does a file integrity check. Just don't skip the pre-boot file system check and you should be good.

Additionally, if you download it with a torrent client, the BitTorrent protocol has a built in file integrity mechanism. So, downloading the image with a torrent client will also automatically verify the file for you.

But, more importantly, verifying the file will not harm anything and will add an extra layer of surety. You lose nothing by taking the time to verify the iso. It's a pretty painless process.

  • I definitely will check it then.
    – theyeetman
    Jan 27, 2021 at 0:44

Yes, please do.

There has been an incident once where the integrity of an ISO was compromised. Yes, it was not Ubuntu (but Mint). Even though I (and almost all of us) trust Canonical it is always better to be safe than sorry. And it also takes mere seconds to do so so why not.

If you do find an issue your username will be in the history books and at least for a day you will be the hero ;)

  • 1
    I'll check it then, because it is better to safe than sorry. Especially when it comes to my main OS. Btw I lost access to my last account and had to create this one, i couldn't bothered to come up with a better name so I just went with the first thing that came to my head.
    – theyeetman
    Jan 27, 2021 at 0:49

Not the answer you're looking for? Browse other questions tagged .