walt wrote: > Something in today's update for ~amd64 changed the bootup behavior > of lvm (again). Now I get an error message that none of the labels > on my lvm disks can be found (I mount by disk label in fstab). > > So now lvm is starting even later than before. I still get the > (now familiar) error from lvm that file locking failed, but I've > been seeing that since the last thread on the subject and this > problem just started today. (lvm does start eventually, but only > after fstab fails to find the lvm disks). > > While poking around in the rc scripts I realized that device-mapper > daemon is no longer running -- I think it was running a few months > ago but I can't be certain now. Should it be running? > > I added device-mapper to the boot runlevel but it changed nothing > AFAICT. > > Also, I notice that a /run directory on tmpfs appeared a while ago > (can't remember when) and I think that should have fixed the file > locking error from lvm, no? But it's not fixed for me. > > What are you guys seeing? > > >
Have you searched the forums? I'm not sure but I think I ran across that issue while searching for the other issues you described, missing lock file. There was a fix for what you are having but I can't recall what it was off the top of my head. I think it was putting device-mapper in the boot runlevel but don't break things on my bad memory. :/ I'm also pretty sure I was using google to search the forums too. I have found that google does a MUCH better job with searches than the forums search tool. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
