public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] no network "eth0" after upgrade.
Date: Sat, 19 Dec 2015 21:57:12 +0200	[thread overview]
Message-ID: <CAJ1xhMXLQJ3pN5SqOy+n7ih-fMWUWHq_9pcw9cj4w9CfK0uHiQ@mail.gmail.com> (raw)
In-Reply-To: <5675AEE7.8030606@sys-concept.com>

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

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.

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

  reply	other threads:[~2015-12-19 19:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 19:10 [gentoo-user] no network "eth0" after upgrade thelma
2015-12-19 19:24 ` thelma
2015-12-19 19:57   ` Alexander Kapshuk [this message]
2015-12-19 20:03     ` Alexander Kapshuk
2015-12-19 20:59     ` thelma
2015-12-19 21:04       ` John Runyon
2015-12-19 21:10         ` thelma
2015-12-19 21:20           ` Dale
2015-12-19 23:02       ` Neil Bothwick
2015-12-20  0:02         ` Philip Webb
2015-12-20  0:56           ` Neil Bothwick
2015-12-20  1:48             ` [gentoo-user] [SOLVED] " thelma
2015-12-20  4:19               ` Philip Webb
2015-12-20  4:26                 ` thelma
2015-12-20  5:37                 ` J. Roeleveld
2015-12-20 10:54                   ` Philip Webb
2015-12-20 14:42                     ` J. Roeleveld
2015-12-20 17:01                     ` Daniel Frey
2015-12-19 20:13 ` [gentoo-user] " Alan Mackenzie
2015-12-19 20:46   ` thelma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ1xhMXLQJ3pN5SqOy+n7ih-fMWUWHq_9pcw9cj4w9CfK0uHiQ@mail.gmail.com \
    --to=alexander.kapshuk@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox