All of lore.kernel.org
 help / color / mirror / Atom feed
From: 'Luca Berra ' <bluca@comedia.it>
To: "Weber, Geoffrey M." <Geoffrey.Weber@mcleodusa.com>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems with initrd for LVM2 on 2.6.0-test8 and -test9 kernels.. .
Date: Fri Oct 31 02:17:03 2003	[thread overview]
Message-ID: <20031031081603.GA26757@percy.comedia.it> (raw)
In-Reply-To: <253458D17524064C996F67C97116BF8806592C@Oscar-5.north.mcld.net>

On Thu, Oct 30, 2003 at 09:46:52AM -0600, Weber, Geoffrey M. wrote:
>My apologies for not providing the information earlier... and for my mistake
>in supplying the link to my initrd image.  I have been bookmarking sites
>like mad and apparently chose the wrong one...
if you even quit posting in multipart/alternative i'll be an happy man
:))))

>Here is my linuxrc inside the initrd image (this is the one based off of the
>evms initrd I found on the web, since it seemed the most complete).
>
>Please note that I still can't get the "/bin/ash" command to work properly,
>though I'm working on it.  I did put in the /dev/tty* and /dev/pt* nodes
>into the initrd image, but still no luck.  

here's the initrd i produce (shell is modified mdk/redhat nash)
note that i mount manually the root fs then i pivot_root.

-------------------------------------------------
... load modules ...
echo Mounting /proc filesystem
mount -t proc /proc /proc
echo Creating device files
mkdevices /dev
echo Activating md devices
mknod /dev/md1 b 9 1
mdassemble
echo Scanning logical volumes
vgscan
echo Activating logical volumes
vgchange -ay
echo 0x0100 > /proc/sys/kernel/real-root-dev
echo Mounting root filesystem
mount -o defaults --ro -t ext3 /dev/vg00/lvol1 /sysroot
pivot_root /sysroot /sysroot/initrd
echo Remounting devfs at correct place if necessary
handledevfs
umount /initrd/proc
-------------------------------------------------
mkdevices: creates device files based on /proc/partitions (if not devfs)
mdassemble: diet-libc version of mdadm --assemble (cannot build full
mdadm with diet-libc)
handledevfs: is described in the comment above

>Here is my menu.lst from grub.  I've been testing with grub just so that I
>could enter changes at boot time instead of running "lilo" all over the
>place.
you can append options to lilo command lines (just type 'em)

>-------- CUT --------
>
>gweber@windforce:/tmp/test$ more menu.lst
>default=1
>root    (hd0,3)
>splashimage (hd0,0)/grub/images/debian_cooleye-dither.xpm.gz
>vga=791
>title   Linux (2.6.0-lvm)
>kernel  (hd0,0)/vmlinuz-2.6.0-test9-aa0.2 root=fe00 console=ttys0
>initrd  (hd0,0)/initrd-gw.gz
                                                     ^^^^^^^^^^^^^
ttys0 ???
i tought serial console was ttyS0,<speed>

L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

  reply	other threads:[~2003-10-31  2:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 16:54 [linux-lvm] Problems with initrd for LVM2 on 2.6.0-test8 and -test9 kernels.. Weber, Geoffrey M.
2003-10-31  2:17 ` 'Luca Berra ' [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-29 17:53 Weber, Geoffrey M.
2003-10-30  7:50 ` Luca Berra

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=20031031081603.GA26757@percy.comedia.it \
    --to=bluca@comedia.it \
    --cc=Geoffrey.Weber@mcleodusa.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.