On 6 Mar 2003, Stephen Kuhn wrote:
>
> LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
> 'lba32' extensions Copyright (C) 1999,2000 John Coffman
>
> Reading boot sector from /dev/hda
> Merging with /boot/boot.b
> Secondary loader: 11 sectors.
> Mapping message file /boot/message
> Message: 0 sectors.
> Boot image: /boot/vmlinuz-2.4.18-3
> Setup length is 10 sectors.
> Mapped 0 sectors.
> Mapping RAM disk /boot/initrd-2.4.18-3.img
> RAM disk: 0 sectors.
> Added linux *
> Boot other: /dev/hda1, on /dev/hda, loader /boot/chain.b
> Mapped 6 (4+1+1) sectors.
> Added DOS
> /boot/boot.0300 exists - no backup copy made.
> Map file size: 19968 bytes.
> Writing boot sector.
>
> Does something seem amiss that I'm missing? Meanwhile, the partition
> numbers haven't changed at all - nothing. Just really weird and I
> thought that I'd dealt with enough lilo problems, just never this bloody
> bit before...which sucks because I'm trying to get my network
> straightened out so I *CAN* do a reinstall on this box...really sucks...
>
Have you tried rebuilding the initial ramdisk on the hard drive? Also,
double check the kernel on the hard drive. I am guessing here, but
looking at the lilo output, I am not happy about the
Mapping RAM disk /boot/initrd-2.4.18-3.img
RAM disk: 0 sectors.
message.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
