Troubleshooting the ISOLINUX Checksum Error
Last night I attempted to reinstall Ubuntu Linux 8.04 Beta on my system and hit a road block: Every time I burned an Ubuntu Install CD and tried to boot from it, I would get the following error that I’m sure some of you Linux veterans have seen before:
ISOLINUX: Image Checksum Error, Sorry Boot Failed
I’ve seen people screaming (in ALL CAPS, that is) and pull their hair out (probably) over this error in many linux forums, desperately trying to figure out the cause of this problem and how to solve it. Some people who have encountered it manage to “fix” the problem by burning their ISO files at a slow speed (say, 2x or 4x). I tried that 3 times, but no bueno. I would still get the same error no matter what…except on one accidental occasion this morning where I took one disc I had tossed in the trash the night before, tried it again, and it actually booted… at least to the installer menu. It failed to load much of anything though. So, as you can see, my DVD drive seemed to be acting kind of flaky.
But then I decided to check and see if my BIOS was up to date. Sure enough, it wasn’t. And in addition to that, one of the bugs the latest BIOS version release notes claimed to fix was “Booting from a CD-ROM which is on the same IDE channel as the primary hard drive.” Kooky little bug indeed. After updating my BIOS, Ubuntu 8.04 installed without a single hitch, and I’m happy to report it’s running better than I ever anticipated; much more stable than 7.10 (particularly Compiz, but that’s a separate story). I’ll soon be writing another blog about the new features to be found in 8.04.
So how did I update my BIOS?
Well, for starts I needed a floppy disk…I could have burnt a boot ISO image to a CD (see this guide here if you want to make a CD instead of a floppy), but considering how flaky these Linux ISO boots were going, I didn’t want to chance a checksum error on my BIOS image or anything weird like that. And speaking of my floppy drive, I had to open the case and plug the damn thing back in and blow off some dust on it’s faceplate because I’ve probably only used the thing a couple times in the whole life of the computer. I had disconnected it so my boot time would be a little faster. And I’m sure some of you probably laughed a moment ago saying, “A f—ing boot floppy tutorial? Are you kidding me? What’s a floppy, haw haw haw!” Hey, I know how you feel.
Captain Not-So-Obvious Warning: “Floppy’s are unreliable! Try to use a brand new one if you intend to do this. A corrupt floppy could cause your BIOS image file or flash utility to contain an error, which could disrupt the BIOS flash process, and turn your computer into a paper weight. So be careful, got it? Because I’m not saying it again, damn it!”
The basic steps to make the BIOS update floppy in Ubuntu Linux are:
- Download the FreeDOS floppy disk image from here and save it to your Desktop.
- Right-Click on the FDSTD.144.gz file you just downloaded and select “Extract Here”. A new file, FDOEM.144 will appear on the desktop.
- Open a Terminal window (Applications>Accessories>Terminal) and browse to your Desktop by typing “cd Desktop” (case-sensitive) then hit the Enter Key.
- Insert your floppy disk. Then type in terminal “dd if=FDOEM.144 of=/dev/fd0” — This will write the FDOEM.144 FreeDOS image to your floppy disc, making it bootable.
Now that the basic boot image and files are on the disc, we’ll need to mount it and copy the bios update files to the floppy. To mount the floppy, enter the following two commands into a terminal window:
- sudo mkdir /media/floppy
- mount /dev/fd0 /media/floppy
Your floppy disc should now be mounted and have it’s own icon in your Places menu as well as the Desktop. Now we need to copy your new bios files to the floppy. (For example purposes, here’s where my BIOS was downloaded from. Consult your motherboard manufacture’s website for your correct BIOS images).

When you download a BIOS upgrade from your motherboard manufacture, it usually comes in the form of a compressed ZIP file, which contains two files (see above). One is a *.bin file, and the other is a small program that’s made to inject that *.bin file and replace the previous BIOS version. All you have to do is extract these two files, then copy them both to your newly created boot floppy. Once these two files are copied over, you can reboot with the floppy in the drive, and once you’re at your A:> prompt, you can then execute your BIOS upgrade utility.
What else might cause a ISOLINUX Checksum Error?
A corrupt copy of an ISO file can cause a bad checksum error. Re-download the ISO if this is the case and try burning it again. Also remember that you have to burn an ISO file by telling your burning software that you want to “burn an image”. A bad burner could also be the cause of the problem, as is the case with drives that have seen heavy use (I’ve worn a few out myself).
One other possible solution you could try using is a boot-disk image called Smart Boot Manager. This utility boots from a floppy, but then allows you to point to another device on the PC to boot from. It’s a good utility if your BIOS doesn’t support CD-ROM booting. Unfortunately, when I tried this utility out, it failed to see my CD-ROM device (but in its defense, this was before I upgraded my BIOS, so that probably factored into this little bug).
As a last resort I also tried to create a bootable USB flash drive to install Ubuntu from. Not all PC’s are capable of booting from a USB drive though and as of this writing, I’ve not yet tested this possible feature out on my PC since updating. But you can give it a shot by following this guide.
That’s all for now! After the break, more CCNA posts and a close look at Ubuntu 8.04.
Monday, April 7th, 2008




