From: "Brian J. Murrell" <lvm@interlinx.bc.ca>
To: linux-lvm@sistina.com
Subject: [linux-lvm] LILO configuration for LVM "boot" filesystem
Date: Mon, 4 Jun 2001 01:07:50 -0700 [thread overview]
Message-ID: <20010604010750.A2560@pc.ilinx> (raw)
I know this is starting to become a LILO issue but I think that the
problem I have is really got to do with LILO and it's interacting with
LVM. I have applied Andreas' patch, thanks Andreas.
When I try to boot with the LVM disk I get "LI" and that is it. The
LILO docs say this about "LI":
This means the first-stage loader gained control; it thought it success-
fully loaded the second-stage loader; but it never got there. This most
often occurs when the second-stage loader, '/boot/boot.b', is not load-
able using the BIOS.
Which would suggest to me that the mapping is not making it through
LVM correct me. But I don't really know that much about how LILO
really works with the underlying device.
My current lilo.conf is:
boot=/dev/hdg
map=/boot/map
install=/boot/boot.b
vga=780
default=linux
keytable=/boot/us.klt
lba32
prompt
timeout=50
message=/boot/message
image=/boot/vmlinuz
label=linux
root=/dev/system/root
initrd=/boot/initrd-lvm-2.4.5-1.1mdk.gz
append=" hda=ide-scsi devfs=mount video=matrox:vesa:263"
read-only
Anyone got any ideas or run into this before?
b.
--
Brian J. Murrell
next reply other threads:[~2001-06-04 8:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 8:07 Brian J. Murrell [this message]
2001-06-04 14:21 ` [linux-lvm] LILO configuration for LVM "boot" filesystem Ben Lutgens
2001-06-05 2:01 ` Brian J. Murrell
2001-06-05 11:56 ` Steven Lembark
2001-06-05 15:48 ` Jack McKinney
2001-06-05 18:32 ` Andreas Dilger
2001-06-06 4:07 ` Brian J. Murrell
2001-06-07 15:30 ` Steven Lembark
2001-06-07 15:43 ` Jack McKinney
2001-06-07 21:18 ` Steven Lembark
2001-06-07 21:36 ` Steve Wray
2001-06-07 21:37 ` Steven Lembark
2001-06-07 21:52 ` Steve Wray
2001-06-07 22:15 ` Jack McKinney
2001-06-07 22:24 ` Steve Wray
2001-06-07 22:27 ` Steven Lembark
2001-06-07 22:23 ` Steven Lembark
2001-06-08 2:28 ` Russell Coker
2001-06-08 2:26 ` Russell Coker
2001-06-07 22:29 ` Mark van Walraven
2001-06-07 22:38 ` Steve Wray
[not found] ` <20010607182636.H3232@jensbenecke.de>
2001-06-07 16:32 ` Jack McKinney
[not found] ` <20010607191649.R3232@jensbenecke.de>
2001-06-07 19:18 ` Jack McKinney
2001-06-07 16:39 ` Mario 'BitKoenig' Holbe
2001-06-07 21:20 ` Steven Lembark
2001-06-08 2:27 ` Russell Coker
2001-06-07 21:08 ` Michael Tokarev
[not found] ` <20010608153036.G21909@jensbenecke.de>
2001-06-11 0:04 ` Mark van Walraven
2001-06-11 0:10 ` Steven Lembark
2001-06-11 0:20 ` Michael Tokarev
2001-06-11 11:39 ` Russell Coker
2001-06-07 15:26 ` Steven Lembark
2001-06-05 18:00 ` Andreas Dilger
2001-06-04 17:56 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010604010750.A2560@pc.ilinx \
--to=lvm@interlinx.bc.ca \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox