From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MHtFR-0006i8-Hh for garchives@archives.gentoo.org; Sat, 20 Jun 2009 05:36:17 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EB6A4E01D6; Sat, 20 Jun 2009 05:36:15 +0000 (UTC) Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by pigeon.gentoo.org (Postfix) with ESMTP id 84BE5E01D6 for ; Sat, 20 Jun 2009 05:36:15 +0000 (UTC) Received: by bwz23 with SMTP id 23so1914547bwz.34 for ; Fri, 19 Jun 2009 22:36:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type; bh=Rry6tWe8KnUb8eWCV5Xo6drnI+YhVNfmI/vwNSL4PY8=; b=GR+lzbwlZ46wmE/cYMCUuRXfThrns1UmMs3FBmBpf0KgOXjmQeN4cIQFokM3AVj8oL PLGt7HdgS7N0MJVa0Cu2pwt43CEyuK3okwVffMZ+FnmXXDKTGknrbqeouFuuds5MipmI 5zDT3iZ6i0fVeEDYB4rZiA3AUJjOKQljnUb34= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=D6NWhaKExwGKp0BzmU/7kjnn3ajPoNBQN2BesYGAnWWyl1QgNMSqkaGOgv0KYzZQlJ UuRw7wkJhCjLn3uoCs5neiH61eP/AjD9djcCs2l8zBm6H3gwzi3Rt3EdHR7eJJqdH9pV NqUIdp4OVdUqhwVnzuqdAc7XcGyPSysejqCM0= Received: by 10.204.77.81 with SMTP id f17mr3353063bkk.78.1245476174849; Fri, 19 Jun 2009 22:36:14 -0700 (PDT) Received: from coercion ([91.191.238.58]) by mx.google.com with ESMTPS id y15sm7228085fkd.23.2009.06.19.22.36.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Jun 2009 22:36:14 -0700 (PDT) Date: Sat, 20 Jun 2009 11:33:38 +0600 From: Mike Kazantsev To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] lvm problem -- is timing? Message-ID: <20090620113338.7d78293c@coercion> In-Reply-To: References: X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.1; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/.RkL+nttnWY8/1EAJM7/UXV"; protocol="application/pgp-signature" X-Archives-Salt: 6509b8fa-f012-4065-aa57-65f9ca4b140f X-Archives-Hash: c3d63483a97b68a0c7c87f388631ed2f --Sig_/.RkL+nttnWY8/1EAJM7/UXV Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 19 Jun 2009 22:15:12 -0600 Maxim Wexler wrote: > Seems if I add the commands: >=20 > vgscan --mknodes > vgchange -a y > mount -a >=20 > to /etc/conf.d/bootmisc and add it to the boot runlevel, the eee boots > to a coherent system BUT not before going through LVM failure, errors, > inability to find volumes etc through many console lines until just > after the line: >=20 > *Configuring kernel parameters... >=20 > comes >=20 > Reading all physical volumes. This may take a while... > Found volume group "vg" using metadata type lvm2 > 5 logical volume(s) in volume group "vg" now active > ... >=20 > And everything is fine after that. So it looks like a question of > timing, of executing bootmisc or something like it earlier, say just > after loading dm-mod and dm-crypt and just before the line in the > console: >=20 > *Setting up the Logical Volume Manager... >=20 > When it all starts to fall apart. >=20 > FWIW I'm using baselayout-2. I've had such problem in the past, even filed the bug: http://bugs.gentoo.org/show_bug.cgi?id=3D255237 For me, the problem was that "device-mapper" initscript started after "lvm". I believe there's "after device-mapper" line already in lvm-2.02.45, so it should run fine, but as an additional precaution I have dm-crypt script at sysinit runlevel, which starts device-mapper and dm-crypt before lvm or even it's runlevel (boot). It makes sense for me, since some lvm pv's (not root) are actually on encrypted partitions, although I mount these even earlier, but should initrd become incompatible w/ latest kernel, dm-crypt should do the job instead. Guess you can do the same, at least if you don't have dm-crypt mappings, or you can try adding device-mapper to sysinit level directly. Here's my boot sequence (from rc.log): rc sysinit logging started at Fri Jun 12 04:24:55 2009 OpenRC 0.4.3 is starting up Gentoo Linux (i686) Press I to enter interactive boot mode * Mounting /proc... [ ok ] * Mounting /sys... [ ok ] * Mounting debug filesystem... [ ok ] * Mounting /dev... [ ok ] * Starting udevd... [ ok ] * Populating /dev with existing devices through uevents... [ ok ] * Waiting for uevents to be processed... [ ok ] * Mounting /dev/pts... [ ok ] * Mounting /dev/shm... [ ok ] * device-mapper uses addon code which is deprecated * and may not be available in the future. * Setting up dm-crypt mappings... * dm-crypt mapping lvcrypt is already configured [ ok ] rc sysinit logging stopped at Fri Jun 12 04:24:55 2009 rc boot logging started at Fri Jun 12 04:24:55 2009 * Setting system clock using the hardware clock [Local Time]... [ ok ] * Autoloaded 0 module(s) * lvm uses addon code which is deprecated * and may not be available in the future. * Setting up the Logical Volume Manager... Locking type -1 initialisation failed. [ ok ] * Checking local filesystems ... ... --=20 Mike Kazantsev // fraggod.net --Sig_/.RkL+nttnWY8/1EAJM7/UXV Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAko8dLYACgkQASbOZpzyXnFqaQCdGBiCD5uF/4RSW2pxn211f6nA 46UAn3Y/wzc5ynzFp97nnroWtd2pyuu0 =PrNl -----END PGP SIGNATURE----- --Sig_/.RkL+nttnWY8/1EAJM7/UXV--