Canek Peláez Valdés wrote:
> On Wed, Apr 4, 2012 at 4:54 AM, Dale <rdalek1967@...> wrote:
>> Neil Bothwick wrote:
>>> On Wed, 04 Apr 2012 04:05:27 -0500, Dale wrote:
>>>> It's a bug. Roach report here:
>>>> Going back a version and then reboot.
>>> No need for that, just change locking_dir in lvm.conf to somewhere
>>> writeable, as mentioned in the bug report - comment 6.
>> Well, I didn't want to mess with the config much since I may make it
>> worse. So, I built a new kernel 3.3.0 and built a new init do hicky.
>> Now, it seems to work. It boots with no errors and everything mounts.
>> I also downgraded to lvm2-2.02.88 which works. A newer version may work
>> but that is what I went back to. It was the last one that I knew worked.
>> So, I took my med and I'm off to bed. Hmmm. I'm a poet and didn't know
>> it. :-p
>> I'll test some more tomorrow.
> It seems the problem it's in LVM, or (more appropriately) in the
> failure to create the /run tmpfs:
> # mount | grep /run
> tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
> tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
> It seems other problems (like 张春江's one with plymouth) have the same
> reason. With systemd the /run tmpfsgets created, so maybe now that
> systemd and udev are being merged this problem will go away.
> For now, I think we can (finally) call this case closed; Dale, I would
> strongly recommend the workaround (editing the config file) instead of
> downgrading. Eventually you will need the new version anyhow.
> Glad to hear it works, albeit with some issues (unrelated to the initramfs).
I'm glad too. Now to keep this mess working. That's my new concern. lol
Thanks much for all the help. I needed it. ;-)
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!
Miss the compile output? Hint: