You are not logged in.
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.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
The beyond kernel failed to boot with kernel panic received with failed to kinit.
Will now add the fallback in Lilo and try again...................
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Modified Lilo to add the wiki described lines for the fallback boot data.
/sbin/lilo -v failed with error that label is too long...label=ArchLinuxFallback .. in wiki.
Changed to ...ArchFallback and reran /sbin/lilo -v successfully...( so much for the statement any label is OK).
Rebooted in ArchFallback to the same kernel panic.
I give.................
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Discovered that /boot partition supplied with installCD auto install is 32MB in size which is too small to alllow several kernel installs.
Besides the kernel26beyond data, the upgrade also included kenel26 fallback- beyond data which was too much for the partitionand the lilo failed as a consequence. The normal arch install was unaffected but the kernel26 beyond did not load completely into /boot.
It seems the size of the auto partitioned hda1/boot should allow much more data space in order for vanilla systems to utilize the latest upgrades which are double-sized due to the fallback device.
Lilo would not accept the label....ArchLinuxFallback...too long!
I have no solution for the problem other than re-install with larger /boot partition....
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
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
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline