On Sat, Jun 10, 2006 at 01:52:52PM -0500, Arnie Stender wrote:
> Hello,
> I completed the final build and went through the section 12.4 making
> LFS bootable but I can't get my new LFS to boot.
> I have checked and re-checked the conf file and gone through the section
> 12.4 a number of times and keep getting an error that says it can't find
> a "boot signature on that partition". It's been a long time since I have
> used LILO but I have read about the loading in multiple stages and
> printing LILO on the screen but I never get as far as seeing an "L". I
> am working from "SVN-20060516" building a pure 64. Has anyone ever seen
> this message about a boot signature? At first I thought it was that I
> hadn't marked the boot partition active but that is not the case. BTW,
> the partition table looks like this. Partition 1 is the home of the LFS
> kernel I am trying to boot.
> Disk /dev/sdb: 82.3 GB, 82348277760 bytes
> 255 heads, 63 sectors/track, 10011 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 * 1 13 104391 83 Linux
> /dev/sdb2 14 379 2939895 83 Linux
> /dev/sdb3 380 1596 9775552+ 83 Linux
> /dev/sdb4 1597 10011 67593487+ 5 Extended
> /dev/sdb5 1597 2083 3911796 82 Linux swap / Solaris
> /dev/sdb6 2084 2692 4891761 83 Linux
> /dev/sdb7 2693 3058 2939863+ 83 Linux
> /dev/sdb8 3059 10011 55849941 83 Linux
>
> Any body have any ideas? Any help would be greatly appreciated. I'd like
> to start building X and other things on my new OS.
>
I've never seen this, but I'm the lilo enthusiast on the editorial
team, so I'd better respond ;) Let's try to work this out.
The message you are getting seems to come from mbr.S in lilo, and
is produced becasue it cannot find the 'LILO' text at offset 6 in
the potential mbr it is looking at. On my machine booting on
/dev/sda the start of the mbr looks like this:
[EMAIL PROTECTED] /home/ken/lilo-22.7.1 #hexdump -C -n 512 /dev/sda
00000000 fa eb 21 01 b2 01 4c 49 4c 4f 16 07 44 63 77 44
|..!...LILO..DcwD|
You seem to have started to boot from lilo (otherwise, it could not
produce the error message), so maybe it is looking in the wrong
place. I'm not clear about your setup -
(1.) which partition contains the host system ?
(2.) can you still boot the host system ? (Actually, if you can't,
trying to fix it will be an interesting exercise).
(3.) but most importantly, what is in your lilo.conf ?
In particular, where does 'boot=' point to ?
I've never tried booting from other than the first hard disk, but
I can recall that people used to have to do things when upgrading a
disk (install on the slave, then pull out the original disk and make
the new one the master) - in that case, people had to use
disk=/dev/hdb bios=0x80 # Tell LILO to treat the second
# disk as if it were the first
# disk (BIOS ID 0x80).
boot=/dev/hdb # Install LILO on second hard
# disk.
(taken from www.tldp.org/HOWTO/Hard-Disk-Upgrade/prepare.html)
I'm not clear if you have a first disk (sda) connected ?
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
_______________________________________________
Clfs-support mailing list
[email protected]
http://ninja.linux-phreak.biz/mailman/listinfo/clfs-support