Home > Aplikasi Desktop, Tutorial > Checking Ubuntu Server ISO File Integrity using MD5SUM

Checking Ubuntu Server ISO File Integrity using MD5SUM

I’ve a problem when running Ubuntu server installation using CDs burned from ISO files I’ve downloaded from Ubuntu repository. They are ubuntu-server-10.04.3-i386.iso and ubuntu-server-10.04.3-amd64.iso. Both of them failed when installing the base system during Ubuntu server installation. It told that CD was corrupt.

There are at least 2 possibilities of failure:
1. The ISO image file is corrupt. It indicates failure when downloading that file;
2. The CD is corrupt. It can happen when CD has scratch on its surface so that CD ROM can not read it. It’s physical failure. Another cause of corrupted CD is a burning failure. I’m using Brasero under Ubuntu Lucid desktop to burn CD;

To test ISO file, we can use md5sum utility. It’s recommended to do as it can test file integrity (for corrupt) and security (for injecting malware code). There is tutorial to do it. At a short, download MD5SUMS file to directory in which iso files reside, then run ‘md5sum -c MD5SUMS‘. md5sum will generate a bunch of warnings, but it’s OK.

md5sum: ubuntu-10.04.3-desktop-amd64.iso: No such file or directory
ubuntu-10.04.3-desktop-amd64.iso: FAILED open or read
md5sum: ubuntu-10.04.3-desktop-i386.iso: No such file or directory
ubuntu-10.04.3-desktop-i386.iso: FAILED open or read
ubuntu-10.04.3-server-amd64.iso: OK
ubuntu-10.04.3-server-i386.iso: OK
md5sum: wubi.exe: No such file or directory
wubi.exe: FAILED open or read
md5sum: WARNING: 8 of 10 listed files could not be read

It ensures that our ISO files are all OK. First failure checking has passed.

We can ensure CD integrity by checking it prior to installation. Select “Check disk integrity test” when booting using CD installer. It will check CD whether it’s passed or failed. In my case, it’s failed to pass checking. So, it’s the CD that cause installation failure. But, CD surface is physically clean, no scratch. Our last suspect is burning program, Brasero.

Changing burning program to gnomebaker has solved my problem.

  1. No comments yet.
  1. No trackbacks yet.

This blog is kept spam free by WP-SpamFree.

Skip to toolbar