Lilo fails after latest beyond kernel (solution found)

Question

The lilo message is as follows:
[root@n6re ~]# /sbin/lilo -v
LILO version 22.7.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2005 John Coffman
Released 17-Sep-2005 and compiled at 14:59:07 on Sep 21 2005.
Reading boot sector from /dev/hda
Using MENU secondary loader
Calling map_insert_data
Boot image: /boot/vmlinuz26
write map file: Input/output error
[root@n6re ~]#
Obviously, I cannot reboot since lilo failed.
EDIT2:  Powered down and rebooted into arch kernel OK. 
Re-ran Lilo successfully.  Rebooted into kernel26beyond and received kernel panic with reference to cannot find hda3.
rebooted into arch and added the following to Lilo.conf ...append="root=/dev/hda3 rootfs=ext3"
Now must run /sbin/lilo -v again before running the beyond kernel....
Will report back...
Any ideas to correct the error in vmlinuz26 map file?  Mebbe corrupt download?
EDIT:  Since the error in lilo references /vmlinuz26 (not /vmlinuz26beyond) I assume that the arch kernel listing in my Lilo has been affected.  The wiki introduces an append to replace ...root=/dev/hda3.... which I assume to mean in the beyond kernel listing only.  Perhaps it is needed in the arch kernel as well?
Below is my Lilo conf.:
# /etc/lilo.conf
boot=/dev/hda
# This line often fixes L40 errors on bootup
# disk=/dev/hda bios=0x80
default=arch
timeout=50
lba32
prompt
image=/boot/vmlinuz26
        label=arch
        root=/dev/hda3
        initrd=/boot/initrd26-full.img
        read-only
image=/boot/vmlinuz26beyond
        label=2.6.16-beyond
        append="root=/dev/hda3"
        initrd=/boot/kernel26.img
        read-only
image=/boot/vmlinuz26beyond
       label=cpio
        root=/dev/hda3
        initrd=/boot/ray.img
        read-only
image=/boot/vmlinuz26
        label=cpio2
        append="root=/dev/hda3 rootfs=ext3"
        initrd=/boot/rays.img
        read-only
#other=/dev/hda1
#        label=dos
It would seem that the arch kernel needs the changes as well as the beyond kernel which isn't made mandatory in the wiki.  Am I wrong?
EDIT3:   Ran kernel26beyond and again received ...kernel panic.
Rewrote lilo.conf to change the append to...append="root=/dev/hda3 rootfstype=ext3" in all lilo references to beyond kernel  and cpio boots.
Reran Lilo and will reboot into beyond kernel and report result.

Answer 1

Utilized qtparted in another arch HDD boot to re-partition via USB IDE as sda1 and enabled a larger /boot partition from MB borrowed from sda2 swap partition.  Ran /sbin/lilo -v in sda3 partition.
After rebooting into original arch HDD, successfully, rebooted to kernel26beyond and received.... kernel panic-not syncing-attempted to kill init...
Iphitus advised that my Lilo was in error...initrd=/boot/kernel26.img....should be...initrd=/boot/kernel26beyond.img..  This change in Lilo corrected the boot of kernel26beyond.
The original Lilo config was obtained from the wiki "Configurin mkinitcpio" which lists the wrong lilo config which I followed for the kernel26beyond.
A word to the wise>>>>>
Edit:  Iphitus advises wiki has been corrected