>(wonder how the installation was successful!) RH Installer: "I have verified everything for consistency. And as is obvious from the later statements in the user's complaint, he has been able to boot the system albeit using round about methods."
> It apparently seem to be a trouble with the boot loader. RH Installer: "May be, but I'm sure the boot loaders I install are troublefree." > (I am not sure how the free space got there in the beginning > of the disk and how the machine recognize a free > space from 1 to 1. I am giving the detail because it sounded odd to me and > may be the > trouble I face is due to this.) The colourful table says: "There WAS free space in there and I have a mandate to disclose as much as possible when it comes to managing partitions." >I selected lilo as the boot loader. >I wanted it to be located in the first sector of boot >partition (/dev/hda2) RH Installer: "And I did as directed. I agree that there is a little more to say about this. I have passed that info to the Boot Loaders GRUB and LILO. Guess they can explain this better." > The system rebooted, I removed the cds. In normal circumstances, I > expected lilo >to come up. It did not. No "No system disk" error also was shown. But system >does not >boot. LILO: "But I was never called in to service. Sorry if I can't live upto expectations, but in this case I'm sure I'm not at fault." > I again used the RH CD to boot. Gave the command "vmlinuz /boot/vmlinuz >root=/dev/hda2" (courtesy JJ). The System booted in to the hard disk. X server >also >worked. But Mouse did not respond. Somebody: "Never heard about the vmlinuz command. But very interesting. Can you tell where on the CD it is living?" > I can therefore boot in to the hard disk by first using the CD and > then giving the >vmlinuz command but not directly. That is why I fealt that the problem is with >Lilo. How >Do I fix this? In fact this is the second attempt. I first tried grub. All the >circumstances are the same. That also did not work. Since both lilo and grub >refuse to >work, I think there is something wrong in what I did. But where exactly did I >go wrong? >and How? LILO and GRUB responds: "Like all programs we have to be loaded and started, so we can figure out the system and at least try to live up to expectations. In this case we were never in the boot scenario and so could not be of any service. Our contacts at the RH Installer CD tell us, the system admin has explicitly directed them that the Master Boot Record that was present at MBR at the time of installation should be given the honour for booting the Multi Boot Configuration. Incidently this Boot Loader, which the guys at RH installer CD unofficilly acknowledges as part of an Operating System named 'Windows Me' is rumoured to be not capable of booting OSes from far off partitions on large Disks, but we did not verify it or anything." LILO: "I'll see what I can do if I'am passed control from BIOS. I'll get that control if the following is run as root. " # dd if=/dev/hda2 of=/dev/hda bs=1 count=446 LILO and GRUB: "BTW, we dont' care whether active flag is set or unset for the partitions, the bootsector of which we try to boot. But as is well known, it matters very much to some OSes" Transcription by, Unni Krishnan.
