Re: [gentoo-user] no network "eth0" after upgrade.

[Alexander Kapshuk <alexander.kapshuk@gmail.com>]

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

On Sat, Dec 19, 2015 at 9:57 PM, Alexander Kapshuk <
alexander.kapshuk@gmail.com> wrote:

> On Sat, Dec 19, 2015 at 9:24 PM, <thelma@sys-concept.com> wrote:
>
>>
>> On 12/19/2015 12:10 PM, thelma@sys-concept.com wrote:
>> > I just upgraded one of my systems and upon boot there is no network:
>> >
>> > /etc/init.d/net.eth0 start
>> > * Mounting local filesystems ...
>> > mount: mount point /proc/bus/usb does not exist
>> > * Some local filesystem failed to start
>> > ERROR: localmount failed to start
>> > ERROR: cannot start net.eth0 as localmount would not start
>> >
>> > rc-status sysinit
>> > sysfs   [  started  ]
>> > dmesg   [  started  ]
>> > devfs  [  started  ]
>> > tmpfiles.dev  [  started  ]
>> > udev   [  started
>> >
>> >
>> > I can not even ssh to the system as network is not working.
>> > What to check next?
>> >
>> It seems I'm not the only one:
>> https://forums.gentoo.org/viewtopic-t-1034770-highlight-localmount.html
>>
>> "The problem was openrc-0.18.4. When I downgraded to openrc-0.16.4 the
>> problem went away."
>>
>> Now, I can not downgrade without eth0 working.
>> Do I need to boot strap and downgrade or is there is easier solution?
>>
>> --
>> Thelma
>>
>>
>>
> Here is a news item that explains the situation.
>
> 2015-10-07-openrc-0-18-localmount-and-netmount-changes
>   Title                     OpenRC-0.18 localmount and netmount changes
>   Author                    William Hubbs <williamh@gentoo.org>
>   Posted                    2015-10-07
>   Revision                  1
>
> The behaviour of localmount and netmount is changing on Linux systems.
> In the past, these services always started successfully. However, now they
> will fail if a file system they attempt to mount cannot be mounted.
>
> If you have file systems listed in fstab which should not be mounted at
> boot time, make sure to add noauto to the mount options. If you have
> file systems that you want to attempt to mount at boot time but failure
> should be allowed, add nofail to the mount options for these file
> systems in fstab.
>
>
>
As a follow up, here is a postinst message generated for openrc that might
come in handy as well:
>>> Messages generated by process 3631 on 2015-12-03 16:53:14 EET for
package sys-apps/openrc-0.18.4:

WARN: postinst
In this version of OpenRC, the loopback interface no longer
satisfies the net virtual.
If you have services now which do not start because of this,
They can be fixed by adding rc_need="!net"
to the /etc/conf.d/<servicename> file.
You should also file a bug against the service asking that
need net be dropped from the dependencies.
The bug you file should block the following tracker:
https://bugs.gentoo.org/show_bug.cgi?id=439092

Bug https://bugs.gentoo.org/show_bug.cgi?id=427996 was not
fixed correctly in earlier versions of OpenRC.
The correct fix is implemented in this version, but that
means netmount needs to be added to the default runlevel if
you are using nfs file systems.

[-- Attachment #2: Type: text/html, Size: 4420 bytes --]