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

[Dirk Heinrichs <dirk.heinrichs@online.de>]

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

Am Sonntag 21 Juni 2009 01:51:34 schrieb Maxim Wexler:
> > So you should really put device-mapper into the boot runlevel. And btw,
> > why do
> > compile things as modules which you need in any case? Doesn't make sense
> > to me.
>
> I put device-mapper into the boot runlevel. I re-compiled the kernel
> with dm-mod=<*>, dm_crypt=<*>, mmc_block=<*> and rebooted.
>
> No change.
>
> Near the start of boot messages this appears:
>
> *Setting up the Logical Volume Manager
> Locking type 1 initilisation failed.

That's just a warning. Hmm, I even wonder why it appears at all, because it 
indicates that /var/lock/lvm is not writeable/available and the lvm startup 
code uses the --ignorelockingfailure option for all lvm commands. That may 
also be a hint that there is still some bl1 stuff around on your system.

> There follows a couple of screenfuls of self-abuse then

Could you please remove rc.log, reboot and post the fresh rc.log?

BTW: Do you see messages like this:

*   device-mapper uses addon code which is deprecated
*   and may not be available in the future.

Also: What are your versions of bl2 and openrc?

Did you compare the contents of those packages (esp. openrc) with the contents 
of your /etc/runlevels?

It may also help to wipe /etc/runlevels and copy the contents of 
/usr/share/openrc/runlevels/ into it, then add symlinks for lvm, device-mapper 
and (if needed) dmcrypt to the boot runlevel again.

Bye...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 190 bytes --]