public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 2.6.17-rc6 No volume groups found
@ 2006-06-15 12:35 Barry Scott
  2006-06-15 16:26 ` Barry Scott
  2007-05-24 15:33 ` freegnu
  0 siblings, 2 replies; 5+ messages in thread
From: Barry Scott @ 2006-06-15 12:35 UTC (permalink / raw)
  To: linux-kernel

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.17-rc6 No volume groups found
  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
  1 sibling, 0 replies; 5+ messages in thread
From: Barry Scott @ 2006-06-15 16:26 UTC (permalink / raw)
  To: linux-kernel

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
I have this kernel working on a system with IDE disks. But the HP uses
SATA disks.

Is there SATA specific LVM code that may be missing from my build of the
kernel?

Barry


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.17-rc6 No volume groups found
  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
  1 sibling, 1 reply; 5+ messages in thread
From: freegnu @ 2007-05-24 15:33 UTC (permalink / raw)
  To: Barry Scott; +Cc: linux-kernel

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
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 
> 



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.17-rc6 No volume groups found
  2007-05-24 15:33 ` freegnu
@ 2007-05-25  9:36   ` Barry Scott
  2007-05-27 17:08     ` freegnu
  0 siblings, 1 reply; 5+ messages in thread
From: Barry Scott @ 2007-05-25  9:36 UTC (permalink / raw)
  To: freegnu; +Cc: linux-kernel

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.17-rc6 No volume groups found
  2007-05-25  9:36   ` Barry Scott
@ 2007-05-27 17:08     ` freegnu
  0 siblings, 0 replies; 5+ messages in thread
From: freegnu @ 2007-05-27 17:08 UTC (permalink / raw)
  To: Barry Scott; +Cc: linux-kernel

yes, i have rebuilt the initrd by the command: /sbin/mkinitrd
--builtin=ata_piix /boot/initrd-2.6.14.img initrd-2.6.14

On Fri, 2007-05-25 at 10:36 +0100, Barry Scott wrote:
> 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.

yes, i have rebuilt the initrd by the command: 
/sbin/mkinitrd --builtin=ata_piix /boot/initrd-2.6.14.img initrd-2.6.14
> 
> 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.
how did you analysis the differences? the constent of the file is scale
of two. 
> 
> Barry
> 
> 



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-05-28  9:07 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2007-05-27 17:08     ` freegnu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox