Re: [gentoo-user] lvm problem -- is timing?

[Mike Kazantsev <mk.fraggod@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 3103 bytes --]

On Fri, 19 Jun 2009 22:15:12 -0600
Maxim Wexler <maxim.wexler@gmail.com> 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=255237

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 ...
  ...



-- 
Mike Kazantsev // fraggod.net

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]