From: Barry Scott <barry.scott@onelan.co.uk>
To: freegnu@163.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc6 No volume groups found
Date: Fri, 25 May 2007 10:36:16 +0100 [thread overview]
Message-ID: <4656AE10.4070104@onelan.co.uk> (raw)
In-Reply-To: <1180020784.9086.0.camel@localhost.localdomain>
freegnu wrote:
> i have the same problem when i built kernel 2.6.14.
> and the previous working kernel is 2.6.11 form Fedora Code 4
>
> anyone give me any adviece? thanks
>
>
> On Thu, 2006-06-15 at 13:35 +0100, Barry Scott wrote:
>
>> On my HP dc7600U having patch around the MCG problem
>> I now get a bit further. Previous working kernel was 2.6.16
>> from Fedora Code 4.
>>
>> I see:
>>
>> Uncompressing Linux... Ok, botinh the kernel.
>> Red Hat nash version 4.2.15 starting
>> Reading all physical volumes. This may take a while...
>> No volume groups found
>> Unable to find volume group "VolGroup00"
>> ERROR: /bin/lvm exited abnormally with value 5 ! (pid 351)
>>
>> Then a few more errors and Kernel panic
>>
>> Where would the problem be?
>>
>> Barry
>>
>>
You have to rebuild the initrd to match the kernel and its modules.
As the kernel develops the initrd scripts need to change to match changes
in modules required to support the disks for the new kernel.
I've no experience with 2.6.11 to 2.6.14. We now use 2.6.21
and know a bit about how to support it on FC4.
What we did to find differences was to run later versions of Fedora Core
that support the kernel we want to use out of the box. Then we break open
the initrd and see what the differences are between the old and new initrd
files.
Barry
next prev parent reply other threads:[~2007-05-25 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 12:35 2.6.17-rc6 No volume groups found Barry Scott
2006-06-15 16:26 ` Barry Scott
2007-05-24 15:33 ` freegnu
2007-05-25 9:36 ` Barry Scott [this message]
2007-05-27 17:08 ` freegnu
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=4656AE10.4070104@onelan.co.uk \
--to=barry.scott@onelan.co.uk \
--cc=freegnu@163.com \
--cc=linux-kernel@vger.kernel.org \
/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