[SOLVED] initrd/vmlinuz issues: Losing my mind...

[MultimediaMan]

Sometime between March and now, I've discovered a problem with my home network boot solution.

ALL Linux distros I use (CentOS/ Scientific Linux/ VMware ESX 4.1) which use the standard initrd/vmlinuz load combinations panic at pretty much the exact same point during the net boot.

The messages are, without fail, are some variation of "Failed to find Ramdisk at 0..."

Googling reveals this message to be usually the result of a corrupted image. CRC checks on the actual files are good (The installation ISOs are mounted as iso9660 Read-Only File systems)

The problems seem to be occurring after I rearranged the directory structure.

This leads me to wonder: Is there is a directory depth limitation with either iPXE or the Linux kernel itself?

http://andromeda.olympus.bv.ar.us.local/...initrd.img

and

http://andromeda.olympus.bv.ar.us.local/...ot/vmlinuz

These addresses will not resolve outside my network, and are for information only.

Both load fine in iPXE, but I wonder if the directory path length might be too deep for Anaconda? Maybe around 127-128 characters?

Thoughts?