This is a self resolved post that I thought I should share with the community.
PRELIMINARY
- I'm on a Windows 7 machine prepping a bootable USB for installing on an old HP
- I downloaded the official Ubuntu 12.04 Server 32bit ISO
- The MD5 checksum checked out OK using winMd5Sum
- I created a bootable USB using:
(all three are sufficient but none corrected the errors I will mention)
PROBLEM
During installation I received the following error message:
If I chose Yes it failed. So I chose No and worked my way back to the main install menu to check the integrity of my CD-ROM as suggested by the error. NOTE: In this case CD-ROM means the bootable USB I am installing from.[!!] Load installer components from CD
There was a problem reading data from the CD-ROM. Please make sure it is in the drive. If retrying does not work, you should check the integrity of your CD-ROM.
Failed to copy file from CD-ROM. Retry?
When I checked the integrity I received a failed message:
At this point, I knew the CD-ROM (bootable USB) was not corrupted because I checked its MD5 checksum before creating the bootable drive. So it had to be the file.[!] Check the CD-ROM(s) integrity
Integrity test failed
The nic-pcmcia-modules-3.5.0-23-generic-di_3.5.0-23.35~precise1_i386.udeb file failed the MD5 checksum verification. Your CD-ROM or this file may have been corrupted.
RESEARCH
Using the advice from a post with the same situation, I took the bootable USB back to my Win7 machine and searched for all extensions that ended with .ude. I discovered the extension was indeed wrong as assumed in the post. I changed all the wrong extensions I discovered to .udeb as suggested.
Once I finished I took the bootable USB back to my potential server and began installing again. Unfortunately I was provided with the same error. No matter what I did I ended up with the same error. It wasn't until I discovered this page discussing the particular file I was dealing with that I realized the situation is worse than just the extension being incomplete. This is when the full extension actually caught my eye. I saw it should be ~precise1_i386.udeb and in my case this was not so. It appeared to be very inconsistent for a number of files.
SOLUTION (parts I corrected are in red)
n = no (wrong file name)
y = yes (corrected file name)
n firewire-core-modules-3.5.0.23-generic-di_3.5.0-23.35~precise.ude
y firewire-core-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n fs-core-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.ude
y fs-core-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n fs-secondary-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1.ude
y fs-secondary-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n message-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.ude
y message-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n multipath-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i3.ude
y multipath-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n nic-usb-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.ude
y nic-usb-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n nic-pcmcia-modules-3.5.0-23-generic-di_3.5.0-23.35~precise1_i.ude
y nic-pcmcia-modules-3.5.0-23-generic-di_3.5.0-23.35~precise1_i386.udeb
n parport-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.ude
y parport-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n pcmcia-storage-modules-3.5.0.23-generic-di_3.5.0-23.35~precis.ude
y pcmcia-storage-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n speakup-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.ude
y speakup-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n squashfs-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i38.ude
y squashfs-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
n storage-core-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1.ude
y storage-core-modules-3.5.0.23-generic-di_3.5.0-23.35~precise1_i386.udeb
NOTE: There was one more I fixed. Unfortunately I don't remember what file it was or what I had to add to the file name. However, I'm confident that with this information you now know what to look for if you are in a similar situation.
CONCLUSION
From what I gather is that the install process knows what files should exist. If the file name is wrong then it throws an error and displays the file name that it is looking for. The only way it can be found is if it exist. This means it has to be named appropriately. I could not discover why/how the misnaming was happening. I theorize that it has something to do with the character limitation of the Windows environment in combination of the Windows apps used for creating the bootable USB. I conclude with this because the ISO itself checks out OK. It's either that or a tiny Leprechaun in my machine messing with me
PLEASE ELABORATE
If you have additional feedback, solutions or theories...please share them.
Bookmarks