After /usr conflation: why not copy booting software to /sbin rather than initramfs?
Neil Bothwick wrote:
> On Wed, 04 Apr 2012 04:05:27 -0500, Dale wrote:
>
>> It's a bug. Roach report here:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=409921
>>
>> 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.
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"
04-04-2012, 11:22 AM
Neil Bothwick
After /usr conflation: why not copy booting software to /sbin rather than initramfs?
On Wed, 04 Apr 2012 04:54:05 -0500, Dale wrote:
> > 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.
You didn't want to change one line in a file, which you could have easily
changed back if it didn't work, so you rebuilt the whole kernel and
initramfs (which are irrelevant to the bug) and downgraded? :-O
--
Neil Bothwick
Give a man a fish and you have fed him for a day, but give him a case of
dynamite and soon the village will be showered with mud and seaweed and
unidentifiable chunks of fish.
After /usr conflation: why not copy booting software to /sbin rather than initramfs?
On Wed, Apr 4, 2012 at 4:54 AM, Dale <rdalek1967@gmail.com> wrote:
> Neil Bothwick wrote:
>> On Wed, 04 Apr 2012 04:05:27 -0500, Dale wrote:
>>
>>> It's a bug. Â*Roach report here:
>>>
>>> https://bugs.gentoo.org/show_bug.cgi?id=409921
>>>
>>> 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).
> 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)
/run is not the problem. The default setting is to write to /var/lock.
Changing that to /run/lock removes the problem.
--
Neil Bothwick
Profanity, The Language of Computer Professionals.
04-04-2012, 11:37 PM
Dale
After /usr conflation: why not copy booting software to /sbin rather than initramfs?
Neil Bothwick wrote:
> On Wed, 04 Apr 2012 04:54:05 -0500, Dale wrote:
>
>>> 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.
>
> You didn't want to change one line in a file, which you could have easily
> changed back if it didn't work, so you rebuilt the whole kernel and
> initramfs (which are irrelevant to the bug) and downgraded? :-O
>
>
Well, yea. I figure they will fix it pretty quick since the bug is
active and folks are working on it. I wouldn't want my change to break
something in the future when just using a known good version, one that I
was using until just the other day, will work just fine. Also, I'll
forget I changed that and let the config update when it gets updated
again. They could lead to breakage too.
Also, I was wanting to update the kernel anyway. I had trouble with my
network on a older kernel and had to update to fix that. So far, the
new 3.3 kernel has helped my network even more. I was actually fixing
more than one issue with the kernel upgrade and downgrading was all of a
one line command. I'm more likely to remember downgrading than editing
a config file these days.
I'm just glad to get some of this mess sorted. < sighs >
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"
04-04-2012, 11:39 PM
Dale
After /usr conflation: why not copy booting software to /sbin rather than initramfs?
After /usr conflation: why not copy booting software to /sbin rather than initramfs?
