Installation Issues - Checksum

[hlago]

Is an internet connection necessary to install VME? In my test labs, I have never encountered an error when installing it, but I am trying it in another environment without internet access and I am receiving the following error:

I' m using the following ISO: HVM_Install_24.04.ISO_S5Q83-11033.iso I have checked the md5 and it is all correct

[AshwiniBarath]

Hello @hlago 
Hope you are doing well.

No — an internet connection is not strictly required to install VME from the official ISO.
The error message confirms the installer fails its media check before/during install. It's almost always a problem with the ISO image or how it was written to the media, not with having no Internet.
Here are few steps to resolve it.
>Re-verify the ISO
>Recreate the install media
Use a raw-write method (dd on Linux/macOS or Rufus in DD mode / balenaEtcher). Avoid simple file copy or tools that alter the image.
Try a different USB stick and a different USB port (use a rear-panel port on desktops).
If you used a virtual mounting tool, instead write the ISO to disk rather than mounting.
>Check for corruption during download
If the checksum doesn’t match, re-download the ISO (preferably over a different network) and re-validate checksums.
>If everything else fails
Re-download the ISO and recreate media first (this fixes 95% of checksum errors).
If a newly downloaded ISO still fails checksums, please contact HPE support for further assistance.

If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.
Regards,
Ashwini

[hlago]

The installation is being performed on an HPE ProLiant Compute DL325 Gen12 server. I mount the ISO (located on my computer) from the iLO and start the installation. I can't use this method; do I have to do it from a USB drive? Installing from the iLO makes the task much easier.

[SergeMe · Accepted solution]

It is also possible that you are hitting a casper integrity check bug or it incorrectly flagging valid media as invalid (can happen when using Virtual Media/iDRAC/ILO environments).

A potential workaround is to skip the kernel integrity check by editing the boot parameters:

1. At the GRUB boot menu, highlight "Try or Install Ubuntu Server" and press e.

2. Find the line starting with linux (or linuxefi).

3. Append fsck.mode=skip to the end of that line.

4. Press F10 or Ctrl+X to boot.

[matrixagent]

I’ve run into this issue twice now on two completely different setups.

When you get checksum or installation errors, it usually comes down to two things:

1. Bad installation media (ISO or USB)
2. Old partitions or metadata on the disk
   – especially from previous installations of Windows Server, VMware, Hyper‑V, or other hypervisors.

These systems often leave behind NTFS or vendor‑specific partitions that interfere with formatting during the installer’s partitioning phase.

The fix in every case has been to fully wipe the disk(s) before installing.

If you're using RAID, I strongly recommend software RAID instead of hardware RAID—specifically creating the RAID during installation using the Custom Storage Layout in the Ubuntu installer. In my experience, old hardware RAID configurations are one of the most common causes of these install failures.

Steps that consistently solve the issue:

1. Set the RAID controller to passthrough / AHCI mode
   (Skip if you're not using hardware RAID.)

2. Boot a Linux live environment (e.g. Ubuntu Live CD).

3. (within the Ubuntu Live CD Shell Session); Stop and remove any leftover software RAID metadata using mdadm:

   Shell (example names for software raid instances are (md0 or md126, md127 etc, thats what i mean by mdX)

   mdadm --stop /dev/mdX

   mdadm --zero-superblock /dev/sdX

   Completely wipe all disks
   using tools like wipefs, fdisk, or any dedicated disk‑cleaning utility.
   A USB bootable disk‑wipe ISO also works well, and is often the safer alternative.

Once the disks are clean, the installation proceeds normally without checksum or formatting errors.

This approach has solved the issue in all my cases and is the proper long‑term fix—much better than simply skipping the checksum or forcing the installer to continue.