[gentoo-user] lvm problem(s)

[gentoo-user] lvm problem(s)

[Maxim Wexler]

Hi group,

My fresh install of 2.6.29-r5 goes kablooey just after 'Loading module dm-mod'

Then the boot console reports:

Couldn't find device with uuid 'ldwVeS-gw14-HE42-M3Gw-DILI-Dbjh-2lHroF'

and

Couldn't find all physical volumes for volume group vg.

and

Volume group "vg" not found

The above repeat several times until: 'Failed to setup the LVM'. Then
off course fsck.ext2 complains it can't find /dev/vg/usr and so on...

My fllter in lvm.conf : filter = [ "a|/dev/sd[ab]|", "r/.*/"] which
corresponds to my Phison SSD and a 8G SD card.

In /etc/fstab the logical volumes are listed like:

/dev/vg/usr   /usr   ext2  noatime  0 2 # etc as per 'Gentoo LVM2 installation'

When I run the reactivate commands given at the end of the above
document all goes well except for:

WARNING: Ignoring duplicate config node: filter (seeking filter)

But /usr /home /tmp /opt are still empty and /var has only lib and
lock below it.

The good news: it boots and lets me log in ;)

Maxim

Re: [gentoo-user] lvm problem(s)

[Neil Bothwick]

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

On Sun, 14 Jun 2009 19:04:35 -0600, Maxim Wexler wrote:

> My fllter in lvm.conf : filter = [ "a|/dev/sd[ab]|", "r/.*/"] which
> corresponds to my Phison SSD and a 8G SD card.

On an Eee 900, the SD card is sdc.

> When I run the reactivate commands given at the end of the above
> document all goes well except for:
> 
> WARNING: Ignoring duplicate config node: filter (seeking filter)

Do you have two filter lines in the config? Only one is used.

> But /usr /home /tmp /opt are still empty and /var has only lib and
> lock below it.

Did you mount -a after activating the VG?


-- 
Neil Bothwick

I never forget a face, but in your case I'll be glad to make an exception.

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

Re: [gentoo-user] lvm problem(s)

[Maxim Wexler]

On 6/15/09, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Sun, 14 Jun 2009 19:04:35 -0600, Maxim Wexler wrote:
>
>> My fllter in lvm.conf : filter = [ "a|/dev/sd[ab]|", "r/.*/"] which
>> corresponds to my Phison SSD and a 8G SD card.
>
> On an Eee 900, the SD card is sdc.

Nope, sdb, just checked. It goes to sdc if you pop it out and push it
back in again.


>
>> When I run the reactivate commands given at the end of the above
>> document all goes well except for:
>>
>> WARNING: Ignoring duplicate config node: filter (seeking filter)
>
> Do you have two filter lines in the config? Only one is used.

Bingo!

>
>> But /usr /home /tmp /opt are still empty and /var has only lib and
>> lock below it.
>
> Did you mount -a after activating the VG?

Cool! There's all my little dirs. Thanks Neil. But isn't it supposed
to do this automaticamente?
From the doc:

    Restart your machine and all partitions should be visible and mounted.

Does my particular setup require further tweaking? Should I be placing
the activate plus mount commands into some conf file?

mw

>
>
> --
> Neil Bothwick
>
> I never forget a face, but in your case I'll be glad to make an exception.
>

Re: [gentoo-user] lvm problem(s)

[Alan McKinnon]

On Monday 15 June 2009 18:51:54 Maxim Wexler wrote:

> > Did you mount -a after activating the VG?
>
> Cool! There's all my little dirs. Thanks Neil. But isn't it supposed
> to do this automaticamente?
> From the doc:
>
>     Restart your machine and all partitions should be visible and mounted.
>
> Does my particular setup require further tweaking? Should I be placing
> the activate plus mount commands into some conf file?

With baselayout2 and openrc, you need to explicitly put lvm into the boot 
runlevel. It then runs "vgchange -a y" to make your volumes visible.

After that, they will be mounted from /etc/fstab as normal.

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] lvm problem(s)

[Maxim Wexler]

>
> With baselayout2 and openrc, you need to explicitly put lvm into the boot

Wow! I didn't even realize lvm was in init.d. There's nothing in the
doc about it. So I went ahead and added to the boot-level and
rebooted.

Same as before with (looks like) one addition:
...
*The lvm init-script is written for baselayout-2!
                   [!!]
*Please do not use it with baselayout-1!

So I removed lvm from boot level and just did a static /etc/init.d/lvm
start and got the exact msg as above.

...

How did I only get baselayout-1? I used the latest tarballs. And what
init-script should I use?

FWIW only one device, the SD card, can't be found and it is listed
about 20 times in the boot console before the LVM gives up.

Hold on, here's /etc/conf.d/lvm:

#LVM should normally only be started after mdraid is available
#this is because LVM physical volumes are very often MD devices
RC_AFTER="mdraid"

#vim: ft=gentoo-conf-d

Well, I don't have mdraid, as far as I know. I'll just comment out
that line and see where it leads.

mw

Re: [gentoo-user] lvm problem(s)

[Maxim Wexler]

>
> #LVM should normally only be started after mdraid is available
> #this is because LVM physical volumes are very often MD devices
> RC_AFTER="mdraid"
>
> #vim: ft=gentoo-conf-d
>
> Well, I don't have mdraid, as far as I know. I'll just comment out
> that line and see where it leads.
>
> mw

nowhere <wah!>

Re: [gentoo-user] lvm problem(s)

[Alan McKinnon]

On Tuesday 16 June 2009 02:33:22 Maxim Wexler wrote:
> > With baselayout2 and openrc, you need to explicitly put lvm into the boot
>
> Wow! I didn't even realize lvm was in init.d. There's nothing in the
> doc about it. So I went ahead and added to the boot-level and
> rebooted.
>
> Same as before with (looks like) one addition:
> ...
> *The lvm init-script is written for baselayout-2!
>                    [!!]
> *Please do not use it with baselayout-1!
>
> So I removed lvm from boot level and just did a static /etc/init.d/lvm
> start and got the exact msg as above.
>
> ...
>
> How did I only get baselayout-1? I used the latest tarballs. And what
> init-script should I use?
>
> FWIW only one device, the SD card, can't be found and it is listed
> about 20 times in the boot console before the LVM gives up.
>
> Hold on, here's /etc/conf.d/lvm:
>
> #LVM should normally only be started after mdraid is available
> #this is because LVM physical volumes are very often MD devices
> RC_AFTER="mdraid"
>
> #vim: ft=gentoo-conf-d
>
> Well, I don't have mdraid, as far as I know. I'll just comment out
> that line and see where it leads.

Here's something to check:

By the time lvm wants to start during boot on that machine, is the SD card 
actually available yet? It needs drivers and such to be loaded and initialized 
first. dmesg should list if that step has been completed first.

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] lvm problem(s)

[Neil Bothwick]

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

On Mon, 15 Jun 2009 18:33:22 -0600, Maxim Wexler wrote:

> How did I only get baselayout-1? I used the latest tarballs. And what
> init-script should I use?

Because the tarballs use stable packages and baselayout-2 is still in
testing.

> FWIW only one device, the SD card, can't be found and it is listed
> about 20 times in the boot console before the LVM gives up.

Is everything needed to use the SD card compiled into the kernel? As it
works after everything is loaded, I suspect not. Look for anything
relevant in the output of lsmod after the system loads and the card is
working, then either add those modules to the autoload file, or build
them into the kernel.


-- 
Neil Bothwick

Save energy: Drive a smaller shell.

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

Re: [gentoo-user] lvm problem(s)

[Maxim Wexler]

>> FWIW only one device, the SD card, can't be found and it is listed
>> about 20 times in the boot console before the LVM gives up.
>
> Is everything needed to use the SD card compiled into the kernel? As it
> works after everything is loaded, I suspect not. Look for anything
> relevant in the output of lsmod after the system loads and the card is
> working, then either add those modules to the autoload file, or build
> them into the kernel.

One step forward, two steps back. The missing module is mmc_block
which I added to the file /etc/conf.d/modules(I upgraded to
baselayout-2 thinking this would help).  Did no good. I see dm-mod and
mmc_block getting loaded alright and then just after 'Setting up the
Logical Volume Manager':

Locking type 1 initialisation failed
Couldn't find devices with  uuid etc...

mw

Re: [gentoo-user] lvm problem(s)

[Maxim Wexler]

On 6/16/09, Maxim Wexler <maxim.wexler@gmail.com> wrote:
>>> FWIW only one device, the SD card, can't be found and it is listed
>>> about 20 times in the boot console before the LVM gives up.
>>
>> Is everything needed to use the SD card compiled into the kernel? As it
>> works after everything is loaded, I suspect not. Look for anything
>> relevant in the output of lsmod after the system loads and the card is
>> working, then either add those modules to the autoload file, or build
>> them into the kernel.
>
> One step forward, two steps back. The missing module is mmc_block
> which I added to the file /etc/conf.d/modules(I upgraded to
> baselayout-2 thinking this would help).  Did no good. I see dm-mod and
> mmc_block getting loaded alright and then just after 'Setting up the
> Logical Volume Manager':
>
> Locking type 1 initialisation failed
> Couldn't find devices with  uuid etc...
>
> mw
>
Come to think of it, it couldn't have been the module. Old udev loaded
it automatically, it was there all the time, I could still mount the
volumes by hand. Now that i've 'migrated' have to specify the module
in the new modules file or modprobe it manually. But I can still mount
the volumes and execute commands.

mw

Re: [gentoo-user] lvm problem(s)

[Alan McKinnon]

On Tuesday 16 June 2009 17:52:28 Maxim Wexler wrote:
> >> FWIW only one device, the SD card, can't be found and it is listed
> >> about 20 times in the boot console before the LVM gives up.
> >
> > Is everything needed to use the SD card compiled into the kernel? As it
> > works after everything is loaded, I suspect not. Look for anything
> > relevant in the output of lsmod after the system loads and the card is
> > working, then either add those modules to the autoload file, or build
> > them into the kernel.
>
> One step forward, two steps back. The missing module is mmc_block
> which I added to the file /etc/conf.d/modules(I upgraded to
> baselayout-2 thinking this would help).  Did no good. I see dm-mod and
> mmc_block getting loaded alright and then just after 'Setting up the
> Logical Volume Manager':
>
> Locking type 1 initialisation failed
> Couldn't find devices with  uuid etc...

My unorthodox but highly effective way to resolve issues like this:

If google or menuconfig's help function doesn't give me an answer in 10 
minutes, I boot off Ubuntu Netbook Remix on a usb stick (it's a 1G download), 
and note which modules it loads and settings it uses for stuff. Boot back into 
gentoo, configure and build accordingly ... sorted

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] lvm problem(s)

[Maxim Wexler]

>
> If google or menuconfig's help function doesn't give me an answer in 10
> minutes, I boot off Ubuntu Netbook Remix on a usb stick (it's a 1G
> download),
> and note which modules it loads and settings it uses for stuff. Boot back
> into
> gentoo, configure and build accordingly ... sorted

Does it provide more info than sysrescuecd-1.2?

mw

Re: [gentoo-user] lvm problem(s)

[Alan McKinnon]

On Tuesday 16 June 2009 21:12:06 Maxim Wexler wrote:
> > If google or menuconfig's help function doesn't give me an answer in 10
> > minutes, I boot off Ubuntu Netbook Remix on a usb stick (it's a 1G
> > download),
> > and note which modules it loads and settings it uses for stuff. Boot back
> > into
> > gentoo, configure and build accordingly ... sorted
>
> Does it provide more info than sysrescuecd-1.2?

I don't know that product so I have to say "I don't know" :-)

I suppose any full fledged desktop LiveCD distro is good enough for this, I 
prefer Ubuntu Remix as it's written for netbooks with all the odd peculiar 
things that put in the hardware.

I also find in general that rescue systems are not very good at these desktopy 
things, and automagic SD card hotplugging is very much something driven by 
desktop usage. Try by all means, I just think YMMV.

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] lvm problem(s)

[Neil Bothwick]

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

On Tue, 16 Jun 2009 22:39:56 +0200, Alan McKinnon wrote:

> I also find in general that rescue systems are not very good at these
> desktopy things, and automagic SD card hotplugging is very much
> something driven by desktop usage. Try by all means, I just think YMMV.

Except Maxim doesn't want automatic hotplugging, he wants to mount the LV
from init scripts.


-- 
Neil Bothwick

But I thought YOU did the backups...

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

Re: [gentoo-user] lvm problem(s)

[Neil Bothwick]

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

On Tue, 16 Jun 2009 09:52:28 -0600, Maxim Wexler wrote:

> Locking type 1 initialisation failed
> Couldn't find devices with  uuid etc...

Just a guess, but it could be that it takes a while for the card reader
to recognise the card after the module is loaded.

I wouldn't put part of an LVM on an SD card though, they are too
unreliable. I do have an SD card mounted from /etc/fstab though, and it
doesn't have any problems, although there was a time when it wouldn't
mount that early in the boot sequence.


-- 
Neil Bothwick

The people who are wrapped up in themselves are overdressed.

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

Re: [gentoo-user] lvm problem(s)

[Maxim Wexler]

>
> Locking type 1 initialisation failed

googling this finds precious little -- whether spelled with an 's' or
a 'z', but check this:

http://bugs.gentoo.org/show_bug.cgi?id=118275#c16

A lot like my situation: the unit boots, the above error flashes by, I
log into a crippled system and enter the two commands #vgchange -a y
and #mount  -a, and everything's fine.

Then in comment #19 the poster mentions using the lvm2 option in the
genkernel. Well, there's no such option in the 2.6.29 kernel. Is there
some way to pass the two commands, vgchange and mount as options to
dm-mod? In /etc/conf.d/modules, lvm? Or, is this a bad idea
altogether?

mw

Re: [gentoo-user] lvm problem(s)

[Neil Bothwick]

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

On Mon, 15 Jun 2009 10:51:54 -0600, Maxim Wexler wrote:

> > On an Eee 900, the SD card is sdc.  
> 
> Nope, sdb, just checked. It goes to sdc if you pop it out and push it
> back in again.

So where is the second SSD. This is the 900 you have?

> >> WARNING: Ignoring duplicate config node: filter (seeking filter)  
> >
> > Do you have two filter lines in the config? Only one is used.  
> 
> Bingo!
> 
> >  
> >> But /usr /home /tmp /opt are still empty and /var has only lib and
> >> lock below it.  
> >
> > Did you mount -a after activating the VG?  
> 
> Cool! There's all my little dirs. Thanks Neil. But isn't it supposed
> to do this automaticamente?

Yes, but the duplicate filter line is preventing your VGs from being
created, so mounting those devices fails. Fix lvm.conf and it should all
work.


-- 
Neil Bothwick

Confucius say :
He who play in root, eventually kill tree!

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

Re: [gentoo-user] lvm problem(s)

[Maxim Wexler]

>
> So where is the second SSD. This is the 900 you have?

900A, maybe different from yours.

>> Cool! There's all my little dirs. Thanks Neil. But isn't it supposed
>> to do this automaticamente?
>
> Yes, but the duplicate filter line is preventing your VGs from being
> created, so mounting those devices fails. Fix lvm.conf and it should all
> work.

No, all it did was remove the warning. All the other errors are the same.
As I mentioned up-thread, the content of filter line appears to be
irrelevant. But if there is more than one, then the LVM complains
about that in addition to everything else.

mw

Re: [gentoo-user] lvm problem(s)

[Daniel Troeder]

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

On Sun, 2009-06-14 at 19:04 -0600, Maxim Wexler wrote:
> Hi group,
> 
> My fresh install of 2.6.29-r5 goes kablooey just after 'Loading module dm-mod'
> 
> Then the boot console reports:
> 
> Couldn't find device with uuid 'ldwVeS-gw14-HE42-M3Gw-DILI-Dbjh-2lHroF'
> 
> and
> 
> Couldn't find all physical volumes for volume group vg.
> 
> and
> 
> Volume group "vg" not found
> 
> The above repeat several times until: 'Failed to setup the LVM'. Then
> off course fsck.ext2 complains it can't find /dev/vg/usr and so on...
> 
> My fllter in lvm.conf : filter = [ "a|/dev/sd[ab]|", "r/.*/"] which
> corresponds to my Phison SSD and a 8G SD card.
> 
> In /etc/fstab the logical volumes are listed like:
> 
> /dev/vg/usr   /usr   ext2  noatime  0 2 # etc as per 'Gentoo LVM2 installation'
> 
> When I run the reactivate commands given at the end of the above
> document all goes well except for:
> 
> WARNING: Ignoring duplicate config node: filter (seeking filter)
> 
> But /usr /home /tmp /opt are still empty and /var has only lib and
> lock below it.
> 
> The good news: it boots and lets me log in ;)
> 
> Maxim

Hello :)

Have you tried with the default filter 
	filter = [ "r|/dev/nbd.*|", "a/.*/" ]
to be on the safe side?

Are you sure, that at the moment the script runs, the devices are
accessible? Maybe a module needs to load before dm-mod loads?

Bye,
Daniel


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

Re: [gentoo-user] lvm problem(s)

[Maxim Wexler]

> Have you tried with the default filter
> 	filter = [ "r|/dev/nbd.*|", "a/.*/" ]

exact same result.

mw