From: "Peter Valdemar Morch" <swp5jhu02@sneakemail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] 2.6 upgrade - LVM version ? & root partition access problems...
Date: Mon, 03 May 2004 18:26:20 +0200 [thread overview]
Message-ID: <15307-37652@sneakemail.com> (raw)
In-Reply-To: <20040503135024.GA11496@null.msp.redhat.com>
AJ Lewis alewis-at-redhat.com |Lists| wrote:
> Bah - I guess I should have pointed you at the fedora mkinitrd - it might
> have saved you the hassle. :(
> http://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/development/i386/Fedora/RPMS/mkinitrd-3.5.21-1.i386.rpm
> is the current version AFAIK. I think this will work better with RH9
> systems than the other one (which was originally built around debian)
Possibly. I can't get it to work with either 2.6.5 or my 2.4 image, though:
valde@peter:~> rpm -q mkinitrd
mkinitrd-3.5.21-1
valde@peter:~> sudo mkinitrd ost.img 2.6.5
No module raid1 found for kernel 2.6.5, aborting.
valde@peter:~> sudo mkinitrd ost.img 2.4.20-20.9custom
pvscan -- LVM driver/module not loaded?
(While I'm running in a 2.6 kernel. module raid1 is not not found for
2.6.5 because I've built it into the kernel now. I can't be bothered to
test it as a module at this point)
>>I've created a new version (incl. svn diff) of the script here:
>>http://wwww.XXXXXXXXX/postings/lvm2/
Wups, what happened with the extra 'w' (4 in all)? It does work, though...
> K - so if the fedora mkinitrd doesn't work for people using RH9, they can
> try that one. :) Thanks!
To make as few changes as possible, RH9 users will have to edit it and
uncomment these lines
INITRDSIZE=4096
INITRDINODES=5000
and run it with the -d option, such as in
# lvm2create_initrd.sh -d 2.6.5
Also, I forgot to mention something weird. If I attempt to boot my old
2.4 kernel, fsck complains. Booting with kernel option " fastboot" gets
me past the fsck point, all the way to the final login screen. However,
in the 2.4 kernel, I no longer have keyboard or mouse support. But I can
ssh into it from outside. Rebooting again into 2.6 also stops at fsck,
so the " fastboot" is required *again*. When running in 2.6, I then run
"lvm vgmknodes" and then it can boot in 2.6 fsck and all - no problemo.
But it seems I've passed the point of no-return-to-2.4.
Later,
Peter
--
Peter Valdemar M�rch
http://www.XXXXXXXXX
next prev parent reply other threads:[~2004-05-03 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-25 21:07 [linux-lvm] 2.6 upgrade - LVM version ? & root partition access problems Peter Valdemar Mørch
2004-04-26 13:58 ` AJ Lewis
2004-05-02 0:17 ` Peter Valdemar Morch
2004-05-02 22:08 ` Peter Valdemar Mørch
2004-05-03 13:50 ` AJ Lewis
2004-05-03 16:26 ` Peter Valdemar Morch [this message]
2004-05-05 15:06 ` Jeffrey Layton
-- strict thread matches above, loose matches on Subject: below --
2004-04-26 8:53 Peter Valdemar Mørch
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=15307-37652@sneakemail.com \
--to=swp5jhu02@sneakemail.com \
--cc=linux-lvm@redhat.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