| 1 |
walt wrote: |
| 2 |
> This is an ~amd64 machine, up to date as of today. The strange thing |
| 3 |
> is that lvm did *not* fail to start -- it's working perfectly. |
| 4 |
> |
| 5 |
> Now, being an Incorrigible Old Fart(TM) I'm still using openrc, and |
| 6 |
> who knows what evil lurks in that paleolithic package? :p |
| 7 |
> |
| 8 |
> Anyone else getting this (false) alarm during boot? |
| 9 |
> |
| 10 |
> |
| 11 |
|
| 12 |
Well, for me its not a false alarm, sort of. Mine fails to start and |
| 13 |
then works later on or after I restart lvm, sort of iffy here. This is |
| 14 |
what mine looks like: |
| 15 |
|
| 16 |
Setting up the Logical Volume Manager . . . |
| 17 |
File-based locking initialisation failed |
| 18 |
*Failed to setup the LVM [!!] |
| 19 |
* Error: lvm failed to start |
| 20 |
|
| 21 |
After all that, it's downhill sort of. Me, I get that with or without a |
| 22 |
init thingy. I'm on Gentoo kernel 3.2.11. I'm using lvm2-2.02.95-r1. |
| 23 |
|
| 24 |
From what I found, it does this because / is mounted ro. It can't write |
| 25 |
the locking file. I thought those were in /var but . . . |
| 26 |
|
| 27 |
Also, If I restart lvm after it boots, it starts fine and all the lvm |
| 28 |
stuff shows up. Maybe this one isn't just me. o_O |
| 29 |
|
| 30 |
Dale |
| 31 |
|
| 32 |
:-) :-) |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
I am only responsible for what I said ... Not for what you understood or |
| 37 |
how you interpreted my words! |
| 38 |
|
| 39 |
Miss the compile output? Hint: |
| 40 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives