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 1MHugT-0003IH-6l for garchives@archives.gentoo.org; Sat, 20 Jun 2009 07:08:17 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 70198E0334; Sat, 20 Jun 2009 07:08:15 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by pigeon.gentoo.org (Postfix) with ESMTP id 1F1D9E0334 for ; Sat, 20 Jun 2009 07:08:15 +0000 (UTC) Received: from rohan.altum.de (p5DC80C4B.dip0.t-ipconnect.de [93.200.12.75]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0MKv1o-1MHugQ1IX8-000jkx; Sat, 20 Jun 2009 09:08:14 +0200 Received: from localhost (localhost [127.0.0.1]) by rohan.altum.de (Postfix) with ESMTP id EDC85700092 for ; Sat, 20 Jun 2009 09:08:13 +0200 (CEST) Received: from gondolin.localnet (gondolin.altum.de [192.168.1.4]) (Authenticated sender: heini) by rohan.altum.de (Postfix) with ESMTPSA id 37B3070008B for ; Sat, 20 Jun 2009 09:08:11 +0200 (CEST) From: Dirk Heinrichs Organization: Privat To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] lvm problem -- is timing? Date: Sat, 20 Jun 2009 09:08:05 +0200 User-Agent: KMail/1.11.4 (Linux/2.6.30; KDE/4.2.4; i686; ; ) References: <20090620113338.7d78293c@coercion> In-Reply-To: <20090620113338.7d78293c@coercion> 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; boundary="nextPart25953252.94mOPOevAP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200906200908.10610.dirk.heinrichs@online.de> X-Provags-ID: V01U2FsdGVkX18rhN90j1VjsHE1T3qwzQy6q4Ms0GcIYQoH9gl CW3TgbyLqIJoBFDvTYyaKWZv68Buo6C3iHWOQ4wYzrNGzr7PJ0 wktp07nlXTOvk1l1y8mqg== X-Archives-Salt: b4db510f-39a7-47cf-bdde-8c04ce4e79f4 X-Archives-Hash: d074786308f20ce3970ae102e7e37220 --nextPart25953252.94mOPOevAP Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Samstag 20 Juni 2009 07:33:38 schrieb Mike Kazantsev: > On Fri, 19 Jun 2009 22:15:12 -0600 > > Maxim Wexler wrote: > > Seems if I add the commands: > > > > vgscan --mknodes > > vgchange -a y > > mount -a > > > > 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: > > > > *Configuring kernel parameters... > > > > comes > > > > 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 > > ... > > > > 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: > > > > *Setting up the Logical Volume Manager... > > > > When it all starts to fall apart. > > > > 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). That's not needed, it should be sufficient to have them all in the boot=20 runlevel: # ll /etc/runlevels/boot insgesamt 0 lrwxrwxrwx 1 root root 20 28. Dez 14:02 bootmisc -> /etc/init.d/bootmisc* lrwxrwxrwx 1 root root 25 12. Apr 08:58 device-mapper -> /etc/init.d/device- mapper* lrwxrwxrwx 1 root root 19 12. Apr 08:59 dmcrypt -> /etc/init.d/dmcrypt* lrwxrwxrwx 1 root root 16 28. Dez 13:53 fsck -> /etc/init.d/fsck* lrwxrwxrwx 1 root root 20 28. Dez 14:02 hostname -> /etc/init.d/hostname* lrwxrwxrwx 1 root root 19 28. Dez 14:02 hwclock -> /etc/init.d/hwclock* lrwxrwxrwx 1 root root 19 28. Dez 17:20 keymaps -> /etc/init.d/keymaps* lrwxrwxrwx 1 root root 22 28. Dez 14:02 localmount -> /etc/init.d/localmoun= t* lrwxrwxrwx 1 root root 15 12. Apr 08:58 lvm -> /etc/init.d/lvm* lrwxrwxrwx 1 root root 19 28. Dez 14:02 modules -> /etc/init.d/modules* lrwxrwxrwx 1 root root 16 28. Dez 13:53 mtab -> /etc/init.d/mtab* lrwxrwxrwx 1 root root 18 28. Dez 14:02 net.lo -> /etc/init.d/net.lo* lrwxrwxrwx 1 root root 18 28. Dez 13:53 procfs -> /etc/init.d/procfs* lrwxrwxrwx 1 root root 16 28. Dez 13:53 root -> /etc/init.d/root* lrwxrwxrwx 1 root root 16 28. Dez 13:53 swap -> /etc/init.d/swap* lrwxrwxrwx 1 root root 18 28. Dez 14:02 sysctl -> /etc/init.d/sysctl* lrwxrwxrwx 1 root root 24 28. Dez 14:02 termencoding ->=20 /etc/init.d/termencoding* lrwxrwxrwx 1 root root 19 28. Dez 14:02 urandom -> /etc/init.d/urandom* > 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. No, it does not make sense. You don't even need an initrd. > 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. As said above, it's not not needed. Maybe it's better to investigate wether= =20 there are any leftovers from baselayout 1 in the runlevels. This was at lea= st=20 the reason I got an unbootable system after switching to bl 2. HTH... Dirk --nextPart25953252.94mOPOevAP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iD8DBQBKPIra8NVtnsLkZ7sRAtVxAKCHACqFirK6eRg4+XjR3vSi4vb/WwCfVF35 4qk/PtivwKkWDdIzG+ljVGo= =tHz3 -----END PGP SIGNATURE----- --nextPart25953252.94mOPOevAP--