From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Berra Subject: Re: [linux-lvm] booting a dm+lvm2 kernel Message-ID: <20040102220935.GQ26275@percy.comedia.it> References: <20040102201045.GK26275@percy.comedia.it> <20040102202206.GA28007@ti19.telemetry-investments.com> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20040102202206.GA28007@ti19.telemetry-investments.com> Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Date: Fri Jan 2 16:11:01 2004 List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit To: linux-lvm@sistina.com On Fri, Jan 02, 2004 at 03:22:06PM -0500, Bill Rugolsky Jr. wrote: >On Fri, Jan 02, 2004 at 09:10:46PM +0100, Luca Berra wrote: >> On Fri, Jan 02, 2004 at 07:30:45PM +0000, Kjartan Reynir Hauksson wrote: >> >>work. You have to use the --lvm-version=2 option to mkinitrd. >> > >> >kernel panic, this time VFS: Cannot open root device "3a00" or 3a:00 >> >> ouch that should never happen, do you have anything printed above the >> kernel panic? > >0x3a == 58 == lvm1 major device number. So it looks like the initrd >is still incorrect. > no, the culprit for 0x3a is lilo, but initrd should purposefully ignore that. it should mount the root fs and then do a pivot_root, so the kernel trying to open a root device is unexpected. L. -- Luca Berra -- bluca@comedia.it Communication Media & Services S.r.l. /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML MAIL / \