From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 53F331384B4 for ; Sat, 19 Dec 2015 19:58:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DF51521C00D; Sat, 19 Dec 2015 19:57:54 +0000 (UTC) Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com [209.85.217.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8D4AA21C004 for ; Sat, 19 Dec 2015 19:57:53 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id u9so79213827lbp.2 for ; Sat, 19 Dec 2015 11:57:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=JSjnF5ZQU922VMDNPQQ5/E06qjotnmO2vTOFs/XsNJE=; b=iVuK9GGj/lsXszWjAtT8IbYLtU4/mfDjK+27Gugm3AXK3noX2BhAE0iIoQ437JKiZY mkWwziPheEATTdeg9gyUSiilPQ8U6Mc6K3DRs8skNfC9Y1U0antynBC7ASKNIgscSDuZ rFAuOJgKQ2Q+PzeE/5HziiORdEsYPcdX+zn6xaAX4Y+raEgtAzUMzBO3/6IgBMqRRbko HXatyxhK6tTkChNcu0KpAQmwEeclezXgVAmkRxQQG+rUdeQDyUi0w4dQFKSgoLxsLCSH UDP7OJYAWrHC4tLiiYTpnRjIdpYZRXxRpdOQZkszzida980f/gXtMZHsbO1IK7ozifo1 n3SQ== X-Received: by 10.112.50.134 with SMTP id c6mr3792010lbo.14.1450555071889; Sat, 19 Dec 2015 11:57:51 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.25.146.77 with HTTP; Sat, 19 Dec 2015 11:57:12 -0800 (PST) In-Reply-To: <5675AEE7.8030606@sys-concept.com> References: <5675ABC2.3030007@sys-concept.com> <5675AEE7.8030606@sys-concept.com> From: Alexander Kapshuk Date: Sat, 19 Dec 2015 21:57:12 +0200 Message-ID: Subject: Re: [gentoo-user] no network "eth0" after upgrade. To: Gentoo mailing list Content-Type: multipart/alternative; boundary=001a113371b8c985a9052745ab3c X-Archives-Salt: faed6d89-d841-4d9a-87f4-b8f155efa25e X-Archives-Hash: 9334d572bc3bc11a87fcee62bdf1322f --001a113371b8c985a9052745ab3c Content-Type: text/plain; charset=UTF-8 On Sat, Dec 19, 2015 at 9:24 PM, 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 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. --001a113371b8c985a9052745ab3c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sat, Dec 19, 2015 at 9:24 PM, <thelma@sys-concep= t.com> wrote:

On 12/19/2015 12:10 PM, thelma@sy= s-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=C2=A0 =C2=A0[=C2=A0 started=C2=A0 ]
> dmesg=C2=A0 =C2=A0[=C2=A0 started=C2=A0 ]
> devfs=C2=A0 [=C2=A0 started=C2=A0 ]
> tmpfiles.dev=C2=A0 [=C2=A0 started=C2=A0 ]
> udev=C2=A0 =C2=A0[=C2=A0 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/vie= wtopic-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
=C2=A0 Title= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 OpenRC-0.18 localmount and ne= tmount changes
=C2=A0 Author=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Wi= lliam Hubbs <williamh@gentoo.org<= /a>>
=C2=A0 Posted=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 2015-10-07<= br>=C2=A0 Revision=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1

The behaviour of loc= almount and netmount is changing on Linux systems.
In the past, these se= rvices always started successfully. However, now they
will fail if a fil= e system they attempt to mount cannot be mounted.

If you have file s= ystems listed in fstab which should not be mounted at
boot time, make su= re 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, ad= d nofail to the mount options for these file
systems in fstab.

--001a113371b8c985a9052745ab3c--