From: Remco Post <r.post@sara.nl>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Rescue cd for lvm 1.0.3 (fwd)
Date: Tue Feb 26 06:52:02 2002 [thread overview]
Message-ID: <200202261252.NAA02080@mailgate.sara.nl> (raw)
In-Reply-To: Your message of "Tue, 26 Feb 2002 13:27:40 +0100." <Pine.A32.4.33.0202261321320.16246-100000@as1.viastore.de>
Because lilo doesn't have a clue about lvm, so it cannot properly store the
location of your kernel in your boot record if /boot is also in lvm (like in
your setup). That is why the lvm howto tells you you must have /boot on a
separate (dos) partition (eg hda1).
>
>
> Hello all,
>
> again a little question. i have currently the following configuration:
>
> # fdisk -l /dev/hda
> /dev/hda1 1 1115 8e Linux LVM
>
> /dev/hda1 => rootvg
>
> rootvg
> /dev/rootvg/root /
> /dev/rootvg/usr /usr
> /dev/rootvg/boot /boot
>
> Why this configuration is so bad? Is it better to leave the /boot on an
> "normal" ext2 filesystem? But, what files need the kernel from /boot to
> bootup the system correctly? I think the kernel will be stored in the
> master boot record with lilo?
> And all files from /boot are accessable, after the ramdisk was loaded.
>
> Btw. linux boot up succesfull, on my other system, where the /boot is on
> an logival volume.
>
> Any hints?
>
> Thx
> Thorsten
>
> ---------- Forwarded message ----------
> Date: Tue, 26 Feb 2002 11:08:16 -0000
> From: William Blunn <bill@tao-group.com>
> Reply-To: linux-lvm@sistina.com
> To: linux-lvm@sistina.com
> Subject: Re: [linux-lvm] Rescue cd for lvm 1.0.3
>
> > not really a lvm problem, but after moving my system to boot from an
> > root-lvm, my lilo stops with the LI error. I think, rewriting the lilo
> > could help, but how can I access my system datas?
>
> "boot from an root-lvm" ... sounds dodgy to me.
>
> You can have the *root* filesystem "/" on an LVM volume.
>
> However the *boot* filesystem should be /boot, which should be a small
> ext2 partition mounted directly on a partition.
>
> Bill
> --
> William H. Blunn - bill+linuxlvm@tao-group.com
> Tao
> 62/63 Suttons Business Park, Earley, READING, RG6 1AZ, United Kingdom
> Tel: +44 118 901 2999 - Fax: +44 118 901 2963 - http://tao-group.com/
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
--
Met vriendelijke groeten,
Remco Post
SARA - Stichting Academisch Rekencentrum Amsterdam
High Performance Computing Tel. +31 20 592 8008 Fax. +31 20 668 3167
"I really didn't foresee the Internet. But then, neither did the computer
industry. Not that that tells us very much of course - the computer industry
didn't even foresee that the century was going to end." -- Douglas Adams
next prev parent reply other threads:[~2002-02-26 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 6:27 [linux-lvm] Rescue cd for lvm 1.0.3 (fwd) Thorsten Sauter
2002-02-26 6:52 ` Remco Post [this message]
2002-02-27 3:29 ` Yves Alloyer
2002-02-27 3:50 ` William Blunn
2002-02-26 10:24 ` 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=200202261252.NAA02080@mailgate.sara.nl \
--to=r.post@sara.nl \
--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;
as well as URLs for NNTP newsgroup(s).