linux-kernel - Re: 2.6.21.1 on Fedora Core 6 breaks LVM/vgscan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070530192214.GC2794@redhat.com>
Date:	Wed, 30 May 2007 15:22:14 -0400
From:	Dave Jones <davej@...hat.com>
To:	Bill Davidsen <davidsen@....com>
Cc:	Jonathan Woithe <jwoithe@...sics.adelaide.edu.au>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.21.1 on Fedora Core 6 breaks LVM/vgscan

On Sat, May 26, 2007 at 12:23:30PM -0400, Bill Davidsen wrote:
 > Jonathan Woithe wrote:
 > > On 21 May 2007 I wrote:
 > > 
 > >> Attempting to compile a 2.6.21.1 kernel for use on a Fedora Core 6 box
 > >> results in a panic at boot because the root filesystem can't be found.
 > > 
 > > I have just compiled 2.6.22-rc2 with the configuration file given in my
 > > previous post and the resulting kernel successfully boots on the machine
 > > concerned.  Whatever broke LVM for this machine in between 2.6.18 and
 > > 2.6.21.1 has now been fixed.
 > > 
 > I haven't had any problem booting with any of the kernels, but when I 
 > try to build a kernel with a Fedora config from /boot, it builds fine 
 > but doesn't boot after install. I started by building a very basic 
 > kernel for testing, and then started adding features to get everything I 
 > need. But just using the latest FC6 config file gets me a kernel which 
 > fails in just the way you mention.

9 times out of 10 it's a busted initrd.
Pull it apart and check that the relevant storage modules & their dependancies
are present.

	Dave

-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/