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

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

[Maxim Wexler]

Hi group,

Rather than resurrect an old thread though I'd start anew with a fresh clue.

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.

Maxim

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

[Mike Kazantsev]

[-- 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 --]

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

[Dirk Heinrichs]

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

Am Samstag 20 Juni 2009 07:33:38 schrieb Mike Kazantsev:
> 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).

That's not needed, it should be sufficient to have them all in the boot 
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/localmount*
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 -> 
/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 
there are any leftovers from baselayout 1 in the runlevels. This was at least 
the reason I got an unbootable system after switching to bl 2.

HTH...

	Dirk

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

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

[Mike Kazantsev]

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

On Sat, 20 Jun 2009 09:08:05 +0200
Dirk Heinrichs <dirk.heinrichs@online.de> wrote:

> > 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 
> runlevel:

So LVM would start before dmcrypt? Great.


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

I do, but mainly for other purposes.
Mounting encrypted partitions from there is a bonus and while root is
not encrypted (although it doesn't even holds most configuration
from /etc) it is an LVM volume.
Can linux boot from lvm root w/o initrd these days?


-- 
Mike Kazantsev // fraggod.net

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

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

[Dirk Heinrichs]

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

Am Samstag 20 Juni 2009 09:37:24 schrieb Mike Kazantsev:

> Dirk Heinrichs <dirk.heinrichs@online.de> wrote:
> > > 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
> > runlevel:
>
> So LVM would start before dmcrypt? Great.

Yes.

> > > 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.
>
> I do, but mainly for other purposes.

Which?

> Mounting encrypted partitions from there is a bonus and while root is
> not encrypted (although it doesn't even holds most configuration
> from /etc) it is an LVM volume.

> Can linux boot from lvm root w/o initrd these days?

Yes, it always could. As long as /boot is a separate partition one can put the 
same stuff into it. Much simpler to setup.

Bye...

	Dirk

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

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

[Mike Kazantsev]

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

On Sat, 20 Jun 2009 11:01:33 +0200
Dirk Heinrichs <dirk.heinrichs@online.de> wrote:

> Am Samstag 20 Juni 2009 09:37:24 schrieb Mike Kazantsev:
> 
> > Dirk Heinrichs <dirk.heinrichs@online.de> wrote:
> > > > 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
> > > runlevel:
> >
> > So LVM would start before dmcrypt? Great.
> 
> Yes.

No, because encrypted partitions hold LVM volumes as well.


> > > > 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.
> >
> > I do, but mainly for other purposes.
> 
> Which?

Keeping my mini-distro there, which I use as instant-boot router w/o
mounting anything.
Why not keep it on /boot, separate partition or separate initrd?
I do, each with a bit different setup and purpose.


> > Mounting encrypted partitions from there is a bonus and while root is
> > not encrypted (although it doesn't even holds most configuration
> > from /etc) it is an LVM volume.
> 
> > Can linux boot from lvm root w/o initrd these days?
> 
> Yes, it always could. As long as /boot is a separate partition one can put the 
> same stuff into it. Much simpler to setup.

Simplier to setup prehaps, but I find it simplier to keep my initrds
contents in git branches w/ one-click build and deploy script, which I
find simplier to maintain than ten different paths under /boot.

But this goes completely offtopic. It's not like I seek suggestions for
my setup, it works perfectly already.


-- 
Mike Kazantsev // fraggod.net

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

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

[Dirk Heinrichs]

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

Am Samstag 20 Juni 2009 13:56:51 schrieb Mike Kazantsev:

> > > So LVM would start before dmcrypt? Great.
> >
> > Yes.
>
> No, because encrypted partitions hold LVM volumes as well.

Well, the usual way is to encrypt LVs, so LVM mut be first. Gentoo support's 
this scheme as default. If you decide to do it different, then of course you'll 
need to start dmcrypt first and put it into sysinit. But since it's not the 
usual way, it's also not the best proposal for everyone.

Bye...

	Dirk

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

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

[Maxim Wexler]

> As said above, it's not not needed. Maybe it's better to investigate wether
> there are any leftovers from baselayout 1 in the runlevels. This was at

How?

> least
> the reason I got an unbootable system after switching to bl 2.
>

I upgraded to bl-2 to avoid this problem but it didn't help. The
system "boots" but is crippled until the vgs are mounted by hand.

mw

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

[Dirk Heinrichs]

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

Am Samstag 20 Juni 2009 21:23:29 schrieb Maxim Wexler:
> > As said above, it's not not needed. Maybe it's better to investigate
> > wether there are any leftovers from baselayout 1 in the runlevels. This
> > was at
>
> How?

You could start by comparing the contents of the bl2 and openrc packages with 
what you really have the directories they install their files into.

Bye...

	Dirk

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

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

[Dirk Heinrichs]

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

Am Samstag 20 Juni 2009 22:26:31 schrieb Dirk Heinrichs:
> Am Samstag 20 Juni 2009 21:23:29 schrieb Maxim Wexler:
> > > As said above, it's not not needed. Maybe it's better to investigate
> > > wether there are any leftovers from baselayout 1 in the runlevels. This
> > > was at
> >
> > How?
>
> You could start by comparing the contents of the bl2 and openrc packages
> with what you really have the directories they install their files into.

You could also look into /usr/share/openrc/runlevels/, which shows the default 
state of /etc/runlevels.

Bye...

	Dirk

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

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

[Maxim Wexler]

> 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

No good. rc-update shows udev, devfs, dmesg, device-mapper in sysinit
runlevel. But the word 'sysinit' doesn't appear even once in the
entire rc.log. Another clue?


FWIW I stopped dm-crypt from being loaded to test whether I really
need it. Makes no difference.

mw

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

[Dirk Heinrichs]

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

Am Samstag 20 Juni 2009 21:14:35 schrieb Maxim Wexler:
> > 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
>
> No good. rc-update shows udev, devfs, dmesg, device-mapper in sysinit
> runlevel.

device-mapper is wrong, there.

# ll /etc/runlevels/sysinit
insgesamt 0
lrwxrwxrwx 1 root root 17 28. Dez 14:03 devfs -> /etc/init.d/devfs*
lrwxrwxrwx 1 root root 17 28. Dez 14:03 dmesg -> /etc/init.d/dmesg*
lrwxrwxrwx 1 root root 16 28. Dez 17:09 udev -> /etc/init.d/udev*

It belongs into boot, together with dmcrypt and lvm.

Bye...

	Dirk

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

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

[Dirk Heinrichs]

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

Am Samstag 20 Juni 2009 22:23:58 schrieb Dirk Heinrichs:
> > No good. rc-update shows udev, devfs, dmesg, device-mapper in sysinit
> > runlevel.
>
> device-mapper is wrong, there.

After reading your initial post in this thread again, that explains the 
problem. You have dm-crypt and dm-mod compiled as modules. Module loading is 
the first thing to happen in the boot runlevel. But the sysinit runlevel is 
executed before the boot runlevel. That means, when your device-mapper init 
script runs, it doesn't even have its module loaded.

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.

Bye...

	Dirk

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

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

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

There follows a couple of screenfuls of self-abuse then

*ERROR: lvm failed to start.

Followed by fsck.ext2 complaining it can't read the volumes,
naturally, since they're are'nt mounted.

a screenful or two of this then

* Some local filesystems failed to mount

La di da

Then

*Configuring kernel parameters...

Finally the volumes are found and mounted and the login appears. All
seems normal except that under /etc/init.d  depscan.sh and
runscript.sh are flashing white on red indicating that they now point
to nothing. And whatever else I haven't spotted yet.

mw

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

[Dirk Heinrichs]

[-- 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 --]

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

[Maxim Wexler]

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

Done:

rc shutdown logging started at Sun Jun 21 14:40:55 2009

* Stopping local...
 [ ok ]
* Saving random seed...
 [ ok ]
* Deactivating swap devices...
 [ ok ]
* Unmounting network filesystems...
 [ ok ]
* Bringing down interface lo
*   Removing addresses
* Stopping gpm...
 [ ok ]
* Stopping syslog-ng...
 [ ok ]
  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
mount: /dev/sda1 already mounted on /boot
mount: /dev/vg/usr already mounted on /usr
mount: /dev/vg/home already mounted on /home
mount: /dev/vg/opt already mounted on /opt
mount: /dev/vg/var already mounted on /var
mount: /dev/vg/tmp already mounted on /tmp
mount: shm already mounted on /dev/shm
mount: tmpfs already mounted on /tmp
nothing was mounted
* Stopping prebootmisc...
 [ ok ]
* Unmounting loopback devices
* Unmounting filesystems
*   Unmounting /var...
 [ ok ]
*   Unmounting /opt...
 [ ok ]
*   Unmounting /home...
 [ ok ]
*   Unmounting /usr...
 [ ok ]
*   Unmounting /tmp...
 [ ok ]
*   Unmounting /boot...
 [ ok ]
*   lvm uses addon code which is deprecated
*   and may not be available in the future.
* Shutting down the Logical Volume Manager
*   Shutting Down logical volume: /dev/vg/home ...
 [ ok ]
*   Shutting Down logical volume: /dev/vg/opt ...
 [ ok ]
*   Shutting Down logical volume: /dev/vg/tmp ...
 [ ok ]
*   Shutting Down logical volume: /dev/vg/usr ...
 [ ok ]
*   Shutting Down logical volume: /dev/vg/var ...
 [ ok ]
*   Shutting Down volume group: vg ...
 [ ok ]
* Finished Shutting down the Logical Volume Manager
* Stopping udevd...
 [ ok ]

rc shutdown logging stopped at Sun Jun 21 14:41:04 2009


rc boot logging started at Sun Jun 21 08:41:52 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.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
* Failed to setup the LVM
 [ !! ]
* ERROR: lvm failed to start
*   device-mapper uses addon code which is deprecated
*   and may not be available in the future.
* Checking local filesystems ...
/dev/sda2: clean, 6837/65952 files, 41219/263424 blocks
/dev/sda1: clean, 37/12544 files, 9602/50148 blocks
fsck.ext2: No such file or directory while trying to open /dev/vg/usr
/dev/vg/usr:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck.ext2: No such file or directory while trying to open /dev/vg/home
/dev/vg/home:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck.ext2: No such file or directory while trying to open /dev/vg/opt
/dev/vg/opt:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck.ext2: No such file or directory while trying to open /dev/vg/var
/dev/vg/var:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck.ext2: No such file or directory while trying to open /dev/vg/tmp
/dev/vg/tmp:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

* Operational error
 [ !! ]
* Remounting root filesystem read/write...
 [ ok ]
* Updating /etc/mtab...
 [ ok ]
* Mounting local filesystems...
mount: special device /dev/vg/usr does not exist
mount: special device /dev/vg/home does not exist
mount: special device /dev/vg/opt does not exist
mount: special device /dev/vg/var does not exist
mount: special device /dev/vg/tmp does not exist
* Some local filesystem failed to mount
 [ !! ]
* Setting hostname to localhost...
 [ ok ]
* Configuring kernel parameters...
 [ ok ]
  Reading all physical volumes.  This may take a while...
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
  Couldn't find all physical volumes for volume group vg.
  Volume group "vg" not found
mount: /dev/sda1 already mounted on /boot
mount: shm already mounted on /dev/shm
mount: tmpfs already mounted on /tmp
mount: special device /dev/vg/usr does not exist
mount: special device /dev/vg/home does not exist
mount: special device /dev/vg/opt does not exist
mount: special device /dev/vg/var does not exist
mount: special device /dev/vg/tmp does not exist
mkdir: cannot create directory `/var/log': File exists
* failed to create needed directory /var/log
 [ !! ]
* ERROR: bootmisc failed to start
* Setting terminal encoding [UTF-8]...
 [ ok ]
* Setting console font [default8x16]...
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
Cannot open font file default8x16
 [ !! ]
* ERROR: consolefont failed to start
* Loading key mappings [us]...
cannot open file windowkeys
* Error loading key mappings
 [ !! ]
* ERROR: keymaps failed to start
* Bringing up interface lo
*   127.0.0.1/8...
 [ ok ]
*   Adding routes
*     127.0.0.0/8 via 127.0.0.1...
 [ ok ]
* Activating swap devices...
 [ ok ]
* Initializing random number generator...
 [ ok ]

rc boot logging stopped at Sun Jun 21 14:41:54 2009


rc default logging started at Sun Jun 21 14:41:54 2009

*   lvm uses addon code which is deprecated
*   and may not be available in the future.
* Setting up the Logical Volume Manager...
 [ ok ]
  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
mount: /dev/sda1 already mounted on /boot
mount: shm already mounted on /dev/shm
mount: tmpfs already mounted on /tmp
/dev/mapper/vg-usr on /usr type ext2 (rw,noatime)
/dev/mapper/vg-home on /home type ext2 (rw,noatime)
/dev/mapper/vg-opt on /opt type ext2 (rw,noatime)
/dev/mapper/vg-var on /var type ext2 (rw,noatime)
/dev/mapper/vg-tmp on /tmp type ext2 (rw,noatime)
* Creating user login records...
 [ ok ]
* Cleaning /var/run...
 [ ok ]
* Wiping /tmp directory...
 [ ok ]
* Setting console font [default8x16]...
 [ ok ]
* Starting syslog-ng...
 [ ok ]
* Starting gpm...
 [ ok ]
* Loading key mappings [us]...
 [ ok ]
* Setting keyboard mode [UTF-8]...
 [ ok ]
* Mounting network filesystems...
 [ ok ]
* Starting local...
 [ ok ]

rc default logging stopped at Sun Jun 21 14:41:57 2009


>
> BTW: Do you see messages like this:
>
> *   device-mapper uses addon code which is deprecated
> *   and may not be available in the future.

Yes

>
> Also: What are your versions of bl2 and openrc?

OpenRC 0.4.4, bl-2.0.1



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

I assume you mean /usr/share/openrc/runlevels.

Under /usr/share/openrc/runlevels/boot there are definitely
differences: no device-mapper, no consolefont, no lvm, no root

Under /usr/share/openrc/runlevels/default: no gpm, syslog-ng

Under /usr/share/openrc/runlevels/sysinit: no udev.

No /usr/share/openrc/runlevels/single also no nonetwork

shutdown runlevels the same.


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

Don't understand. The links in /etc/runlevels and
/usr/share/openrc/runlevels are identical(except for the omissions
noted above) eg bootmisc -> /etc/init.d/bootmisc. Maybe if I add the
missing links to /usr/share/openrc/runlevels that'll fix things...I'll
try that in the meantime.

Thanks for the hints!

mw

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

[Maxim Wexler]

> differences: no device-mapper, no consolefont, no lvm, no root

My bad: root IS there.

> noted above) eg bootmisc -> /etc/init.d/bootmisc. Maybe if I add the
> missing links to /usr/share/openrc/runlevels that'll fix things...I'll
> try that in the meantime.

No change whatever. Back to the drawing board :(

mw

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

[Neil Bothwick]

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

On Sun, 21 Jun 2009 15:16:49 -0600, Maxim Wexler wrote:

> mount: /dev/vg/tmp already mounted on /tmp
> mount: tmpfs already mounted on /tmp

It's nothing to do with your problem, but why are you mounting two
filesystems on /tmp?

>   Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.

Can you confirm this is the SD card?

I still think there may be a delay in the kernel seeing the SD card, this
used to happen with my Eee. Have you tried adding a sleep command to the
relevant part of init.d/bootmisc?

How large is the SSD in your Eee? Is it really necessary to have a volume
group spanning the SSD and SD card, two very different devices?


-- 
Neil Bothwick

I just got lost in thought. It was unfamiliar territory.

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

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

[Ian Lee]

Neil Bothwick wrote:
> On Sun, 21 Jun 2009 15:16:49 -0600, Maxim Wexler wrote:
> 
>> mount: /dev/vg/tmp already mounted on /tmp
>> mount: tmpfs already mounted on /tmp
> 
> It's nothing to do with your problem, but why are you mounting two
> filesystems on /tmp?
> 
>>   Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
> 
> Can you confirm this is the SD card?
> 
> I still think there may be a delay in the kernel seeing the SD card, this
> used to happen with my Eee. Have you tried adding a sleep command to the
> relevant part of init.d/bootmisc?
> 
> How large is the SSD in your Eee? Is it really necessary to have a volume
> group spanning the SSD and SD card, two very different devices?
> 
> 
Would I be correct in thinking the SSD is a sata device while the SD is 
a usb device??

How are you USB drivers compiled in the kenrnel?

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

[Maxim Wexler]

> Would I be correct in thinking the SSD is a sata device while the SD is
> a usb device??
>
> How are you USB drivers compiled in the kenrnel?

# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
CONFIG_RT2500USB=m
# CONFIG_RT73USB is not set
CONFIG_RT2X00_LIB_USB=m
# USB Network Adapters
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_HSO is not set
CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_US122L is not set
# USB Input Devices
CONFIG_USB_HID=y
# CONFIG_USB_HIDDEV is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
# Miscellaneous USB options
# CONFIG_USB_DEVICEFS is not set
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_MON is not set
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set
# USB Host Controller Drivers
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_WHCI_HCD is not set
# CONFIG_USB_HWA_HCD is not set
# USB Device Class drivers
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
CONFIG_USB_WDM=m
# CONFIG_USB_TMC is not set
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed;
# see USB_STORAGE Help for more information
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_LIBUSUAL is not set
# USB Imaging devices
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# USB port drivers
CONFIG_USB_SERIAL=m
# CONFIG_USB_EZUSB is not set
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_CH341 is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP2101 is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_FUNSOFT is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_IUU is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_MOTOROLA is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_SPCP8X5 is not set
# CONFIG_USB_SERIAL_HP4X is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIEMENS_MPI is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_OPTICON is not set
# CONFIG_USB_SERIAL_DEBUG is not set
# USB Miscellaneous drivers
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_VST is not set
# CONFIG_USB_GADGET is not set

>
>

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

[Dirk Heinrichs]

Am Montag 22 Juni 2009 03:20:02 schrieb Maxim Wexler:
> > Would I be correct in thinking the SSD is a sata device while the SD is
> > a usb device??
> >
> > How are you USB drivers compiled in the kenrnel?

And what about:

> # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed;
> # see USB_STORAGE Help for more information
> CONFIG_USB_STORAGE=y

Are CONFIG_BLK_DEV_SD and CONFIG_SCSI also compiled in?

Bye...

	Dirk

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

[Maxim Wexler]

> Are CONFIG_BLK_DEV_SD and CONFIG_SCSI also compiled in?
>

Yes

mw

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

[Maxim Wexler]

On 6/21/09, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Sun, 21 Jun 2009 15:16:49 -0600, Maxim Wexler wrote:
>
>> mount: /dev/vg/tmp already mounted on /tmp
>> mount: tmpfs already mounted on /tmp
>
> It's nothing to do with your problem, but why are you mounting two
> filesystems on /tmp?

fstab:
...
shm  /dev/shm   tmpfs  nodev,nosuid,noexec 0 0
tmpfs  /tmp   tmpfs   nodev,nosuid,noexec 0 0 #suggested in a forum,
seems harmless enough

>>   Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
>
> Can you confirm this is the SD card?

According to pvdisplay it is.

>
> I still think there may be a delay in the kernel seeing the SD card, this
> used to happen with my Eee. Have you tried adding a sleep command to the
> relevant part of init.d/bootmisc?

Not yet. What is the 'relevant' part? Is this the same thing as adding
a delay to the kernel line in grub?

>
> How large is the SSD in your Eee? Is it really necessary to have a volume
> group spanning the SSD and SD card, two very different devices?

Asus SSD, 4G  SD card 8G

Necessary? Don't know but is meant to spare the SSD too much r/w strain.

mw

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

[Neil Bothwick]

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

On Sun, 21 Jun 2009 19:13:19 -0600, Maxim Wexler wrote:

> >> mount: /dev/vg/tmp already mounted on /tmp
> >> mount: tmpfs already mounted on /tmp
> >
> > It's nothing to do with your problem, but why are you mounting two
> > filesystems on /tmp?
> 
> fstab:
> ...
> shm  /dev/shm   tmpfs  nodev,nosuid,noexec 0 0
> tmpfs  /tmp   tmpfs   nodev,nosuid,noexec 0 0 #suggested in a forum,
> seems harmless enough

It is, but you're also mounting /dev/fg/tmp on /tmp.

> > I still think there may be a delay in the kernel seeing the SD card,
> > this used to happen with my Eee. Have you tried adding a sleep
> > command to the relevant part of init.d/bootmisc?
> 
> Not yet. What is the 'relevant' part? Is this the same thing as adding
> a delay to the kernel line in grub?

Actually, it's /etc/init.d/localmount, not bootmisc. Add a sleep command
just before No, you'de need to edit the bootmisc script and add a sleep
command just before

ebegin "Mounting local filesystems"

> > How large is the SSD in your Eee? Is it really necessary to have a
> > volume group spanning the SSD and SD card, two very different devices?
> 
> Asus SSD, 4G  SD card 8G

Ah, I thought only the 701 had the small SSD.
 
> Necessary? Don't know but is meant to spare the SSD too much r/w strain.

How? By spanning an LVM across the two, you have no control over which is
written to the most. I'd put / on the SSD then mount write-heavy
directories, like /var and /home, on the SD card. I'd also set $PORTDIR
to /var/portage (/usr is a daft place to put the portage tree anyway).


-- 
Neil Bothwick

Windows to 486/50 mhz cpu: Don't rush me, don't rush me...

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

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

[Maxim Wexler]

> Actually, it's /etc/init.d/localmount, not bootmisc. Add a sleep command
> just before No, you'de need to edit the bootmisc script and add a sleep
> command just before

Sorry, this doesn't scan well. Do I put the sleep command in
localmount or not? Then edit bootmisc too?

How many seconds do I assign to NUMBER?

mw

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

[Neil Bothwick]

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

On Mon, 22 Jun 2009 11:42:05 -0600, Maxim Wexler wrote:

> > Actually, it's /etc/init.d/localmount, not bootmisc. Add a sleep
> > command just before No, you'de need to edit the bootmisc script and
> > add a sleep command just before  
> 
> Sorry, this doesn't scan well.

It doesn't, that not what I (thought I'd) typed.

> Do I put the sleep command in
> localmount or not? Then edit bootmisc too?

Put it in localmount, not bootmisc, just before
ebegin "Mounting local filesystems"
 
> How many seconds do I assign to NUMBER?

There's only one way to find out. Try 60, if that doesn't fix it, it's
not a delay reading the card.


-- 
Neil Bothwick

If you use envelopes, why not encryption ?

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

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

[Maxim Wexler]

>
>> Necessary? Don't know but is meant to spare the SSD too much r/w strain.
>
> How? By spanning an LVM across the two, you have no control over which is
> written to the most. I'd put / on the SSD then mount write-heavy
> directories, like /var and /home, on the SD card. I'd also set $PORTDIR
> to /var/portage (/usr is a daft place to put the portage tree anyway).

That's what I have, I think,  sda1 is /boot approx 50M , sda2 is /
approx 1G,  then the rest of the SSD is spanned with the SD card,
approx 11G, and committed to /usr /home /opt /var and /tmp just as in
the gentoo doc LVM2.

mw

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

[Neil Bothwick]

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

On Mon, 22 Jun 2009 12:09:52 -0600, Maxim Wexler wrote:

> >> Necessary? Don't know but is meant to spare the SSD too much r/w
> >> strain.  
> >
> > How? By spanning an LVM across the two, you have no control over
> > which is written to the most. I'd put / on the SSD then mount
> > write-heavy directories, like /var and /home, on the SD card. I'd
> > also set $PORTDIR to /var/portage (/usr is a daft place to put the
> > portage tree anyway).  
> 
> That's what I have, I think,  sda1 is /boot approx 50M , sda2 is /
> approx 1G,  then the rest of the SSD is spanned with the SD card,
> approx 11G, and committed to /usr /home /opt /var and /tmp just as in
> the gentoo doc LVM2.

How does that spare the SSD when frequently written directories,
like /var and /usr/portage on partially on the SSD? If you want to keep
them off the SSD, you must not use LVM like this.

Forget LVM, forget a separate /boot, just stick / on the SSD and mount
the likes of /var on the SD card. I use LVM on my Eee, but that's because
it has two SSDs, I wouldn't dream of including the SD card in there.


-- 
Neil Bothwick

C&W music backward: get yer dog, wife, job, truck, kids, and sobriety
back.

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

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

[Maxim Wexler]

> Forget LVM, forget a separate /boot, just stick / on the SSD and mount
> the likes of /var on the SD card. I use LVM on my Eee, but that's because
> it has two SSDs, I wouldn't dream of including the SD card in there.
>

Ok, I did it! No more LVM! Wiped the SSD and made one partition out of
it. Mounted it on /mnt/gentoo and unpacked the stage3 tarball. Silly
question: now what? Where do I mount the SD card prior to unpacking
portage? Do I make separate partitions on the SD card for each dir I
need /usr /var /tmp etc? The natural place would seem to be on
/mnt/gentoo/usr, but what about the other dirs? I should know this;
I've done it often enough, but only when the other drive held a
different OS or was strictly for storage. It probably seems obvious to
you, but I can't see it.

mw

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

[Neil Bothwick]

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

On Mon, 22 Jun 2009 20:12:01 -0600, Maxim Wexler wrote:

> Ok, I did it! No more LVM! Wiped the SSD and made one partition out of
> it. Mounted it on /mnt/gentoo and unpacked the stage3 tarball. Silly
> question: now what? Where do I mount the SD card prior to unpacking
> portage? Do I make separate partitions on the SD card for each dir I
> need /usr /var /tmp etc? The natural place would seem to be on
> /mnt/gentoo/usr, but what about the other dirs? I should know this;
> I've done it often enough, but only when the other drive held a
> different OS or was strictly for storage. It probably seems obvious to
> you, but I can't see it.

I'd put /home and /var on the SD card to start with, you may need to
put /usr/src on there too or your SSD may fill up when installing or
compiling a second or third kernel.

I'd also move the portage tree there, but you can do that
post-installation by moving /usr/portage to /var/portage and changing
PORTDIR in make.conf.

Mount the partitions in the relevant places for installation, 
/mnt/gentoo/var etc. 


-- 
Neil Bothwick

Oxymoron: Clearly Misunderstood.

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

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

[Maxim Wexler]

> I'd put /home and /var on the SD card to start with, you may need to
> put /usr/src on there too or your SSD may fill up when installing or
> compiling a second or third kernel.
>
> I'd also move the portage tree there, but you can do that
> post-installation by moving /usr/portage to /var/portage and changing
> PORTDIR in make.conf.
>
> Mount the partitions in the relevant places for installation,
> /mnt/gentoo/var etc.

OK, been staring at this terminal for about an hour. I'm at
root@sysresccd /mnt/gentoo where sda1 is mounted. Do I just mount sdb1
on /mnt/gentoo too? Do I delete home and var then mkdirs on sdb2?
Won't they just be re-made on the same partition, sda1? I've already
unpacked portage on sdb1(mounted on usr), not a problem, I can just
delete it. But why is it when I umount sdb1 from usr and mount it
under /mnt/gentoo  I can't see portage under /mnt/gentoo? It's there
when I mount sdb1 on usr. Do I need to fdisk /dev/sdb with all the
relevant partitions? Then I'll have one big 4G partition on the SSD
and a lot of little partitions on the 8G SD, no?

mw

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

[Alan McKinnon]

On Tuesday 23 June 2009 21:15:13 Maxim Wexler wrote:
> > I'd put /home and /var on the SD card to start with, you may need to
> > put /usr/src on there too or your SSD may fill up when installing or
> > compiling a second or third kernel.
> >
> > I'd also move the portage tree there, but you can do that
> > post-installation by moving /usr/portage to /var/portage and changing
> > PORTDIR in make.conf.
> >
> > Mount the partitions in the relevant places for installation,
> > /mnt/gentoo/var etc.
>
> OK, been staring at this terminal for about an hour. I'm at
> root@sysresccd /mnt/gentoo where sda1 is mounted. Do I just mount sdb1
> on /mnt/gentoo too? Do I delete home and var then mkdirs on sdb2?
> Won't they just be re-made on the same partition, sda1? I've already
> unpacked portage on sdb1(mounted on usr), not a problem, I can just
> delete it. But why is it when I umount sdb1 from usr and mount it
> under /mnt/gentoo  I can't see portage under /mnt/gentoo? It's there
> when I mount sdb1 on usr. Do I need to fdisk /dev/sdb with all the
> relevant partitions? Then I'll have one big 4G partition on the SSD
> and a lot of little partitions on the 8G SD, no?

Think about this.

You have something mounted at /mnt/gentoo. You want to mount something else at 
/mnt/gentoo - this will succeed, but what makes you think you will then be 
able to see the files from the first thing mounted there?

Light bulb coming on yet?

You have two things to mount, so mount them on *different*directories* and mv 
files around to your heart's content.


-- 
alan dot mckinnon at gmail dot com

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

[Neil Bothwick]

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

On Tue, 23 Jun 2009 13:15:13 -0600, Maxim Wexler wrote:

> OK, been staring at this terminal for about an hour. I'm at
> root@sysresccd /mnt/gentoo where sda1 is mounted. Do I just mount sdb1
> on /mnt/gentoo too? Do I delete home and var then mkdirs on sdb2?
> Won't they just be re-made on the same partition, sda1? I've already
> unpacked portage on sdb1(mounted on usr), not a problem, I can just
> delete it. But why is it when I umount sdb1 from usr and mount it
> under /mnt/gentoo  I can't see portage under /mnt/gentoo? It's there
> when I mount sdb1 on usr. Do I need to fdisk /dev/sdb with all the
> relevant partitions? Then I'll have one big 4G partition on the SSD
> and a lot of little partitions on the 8G SD, no?

Create two partitions on sdb
mount /dev/sdb1 /mnt/gentoo/var
mount /dev/sdb2 /mnt/gentoo/home

It's really not that hard, but you seem to be trying to find clever
solutions when the simple one will do.


-- 
Neil Bothwick

If Microsoft made cars:
"The airbag system would ask "are you sure?" before deploying."

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

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

[Maxim Wexler]

> Create two partitions on sdb
> mount /dev/sdb1 /mnt/gentoo/var
> mount /dev/sdb2 /mnt/gentoo/home
>
> It's really not that hard, but you seem to be trying to find clever

Walking's hard -- until you learn.

> solutions when the simple one will do.

Well, of course the simple things have a way of eluding one, don't
they? eg Natural Selection.

mw

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

[Neil Bothwick]

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

On Tue, 23 Jun 2009 15:59:02 -0600, Maxim Wexler wrote:

> > It's really not that hard, but you seem to be trying to find clever  
> 
> Walking's hard -- until you learn.

But you've been using Gentoo for some time now, so you would be expected
to have a grasp of the fundamentals. After all, you passed the Gentoo
Entrance Exam :)


-- 
Neil Bothwick

Random access is the optimum of the mass storages.

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

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

[Maxim Wexler]

> But you've been using Gentoo for some time now, so you would be expected
> to have a grasp of the fundamentals. After all, you passed the Gentoo
> Entrance Exam :)

True enough, but I have a lot of hobbies.  I may leave gentoo for a
while and go on to something else completely different as the hard won
knowledge dribbles away. All this time I've had a desktop which served
my needs with a minimum of tweaking. Then I bought the tripleE, my
first portable, with an SSD and only 4G of storage, acpi etc and my
world changed.

mw

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

[Dirk Heinrichs]

Am Sonntag 21 Juni 2009 23:16:49 schrieb Maxim Wexler:

>   Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
>   Couldn't find all physical volumes for volume group vg.

That could either mean that (not all of) the drivers needed to access this 
device are available (not compiled into the kernel), or what Neil already 
wrote: a delay in discovering the device.

dmesg output would also be a good thing to sort this out.

Bye...

	Dirk

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

[Maxim Wexler]

> That could either mean that (not all of) the drivers needed to access this
> device are available (not compiled into the kernel), or what Neil already
> wrote: a delay in discovering the device.
>
> dmesg output would also be a good thing to sort this out.
>

477 lines! Rather than post it, what sort of thing(s) should I look
for. sda and sdb show up OK. All the usb stuff looks alright. grepping
for scsi shows that the SSD and SD devices have been found.

mw

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

[Neil Bothwick]

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

On Mon, 22 Jun 2009 11:33:13 -0600, Maxim Wexler wrote:

> > dmesg output would also be a good thing to sort this out.
 
> 477 lines! Rather than post it, what sort of thing(s) should I look
> for. sda and sdb show up OK. All the usb stuff looks alright. grepping
> for scsi shows that the SSD and SD devices have been found.

The SD device it is reporting is the card reader at sdb, that's not the
same as recognising the volume in it.


-- 
Neil Bothwick

If the cops arrest a mime, do they tell her she has the right to remain
silent?

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