今天早上，我的 Ubuntu 18.04 服务器版中的网络不再工作了：
marco@pc01:$ sudo lshw -class network
*-network DISABLED
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express
Gigabit Ethernet Controller
*-network DISABLED
description: Wireles interface
product: AR9227 Wireless Network Adapter
*-network:0
description: Ethernet interface
physical id: 2
logical name : docker0
*-network:1
description: Ethernet interface
physical id: 3
sudo nano /etc/nework/interfaces：
iface eth0 inet static
address 192.168.1.7
netmask 255.255.255.0
network 192.168.1.1
broadcast 192.168.0.255
post-up iptables-restore <
/etc/iptables.up.rules
gateway 192.168.1.1
dns-nameservers 192.168.0.5 8.8.8.8
marco@pc01:$ sudo service network-manager restart
Failed to restart network-manager.service: Unit network-manager.service
not found
即使使用 sudo /etc/init.d/networking restart：
marco@pc01:$ sudo /etc/init.d/networking restart
[ok] Restarting networking (via systemctl):
networking.service
marco@pc01:$ ping 192.168.1.4
connect: Network is unreachable
我该怎么做才能让网络再次可用？期待您的帮助 Marco
1°更新：
marco@pc01:$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKOWN group
default qlen 1000
inet 27.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 78:24:af:43:ef:5c brd ff:ff:ff:ff:ff:ff
3: wlp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether c0:4a:00:09:0e:80 brd ff:ff:ff:ff:ff:ff
4: b3-4f9fe03b1a66: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
noqueue state DOWN group default
link/ether 02:42:64:29:65:73 brd ff:ff:ff:ff:ff:ff
inet 172.22.0.1/16 brd 172.22.255.255 scope global br-4f9fe03b1a66
valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default
link/Ether 02:42:01:ea:90:66 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scoper global docker0
valid_lft forever preferred_lft forever
2°更新：
A）
marco@pc01:$ ifconfig eth0 up eth0: ERROR while getting interface flags:
eth0: ERROR while getting interface flgs: No such device
eth0: Host name lookup failure
marco@pc01:$ ifconfig
br-4f9feo3b1a66: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.22.0.1 netmask 255.255.0.0 broadcast 172.22.255.255
ether 02:42:4d:c4:bd:62 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0B)
RX errors 0 dropped 0 overruns 0 frame 0
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0: flags=4099<,UP,BROADCAST,MULTICAST> mtue 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:24:b9:3b:59 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
l0: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefoxlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 258 bytes 32343 (32.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 258 bytes 32343 (32.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
B）
在/etc/网络/接口：
auto lo
iface lo inet loopback
3°更新：
我修改了 /etc/network/interfaces 文件，如下所示：
iface enp3s0 inet static
address 192.168.1.7
netmask 255.255.255.0
network 192.168.1.1
broadcast 192.168.0.255
post-up iptables-restore <
/etc/iptables.up.rules
gateway 192.168.1.1
dns-nameservers 192.168.0.5 8.8.8.8
但还是没有网络。
4°更新：
marco@pc01:$ uname -r
4.15.0-55-generic
marco@pc01:$ ls -al /etc/netplan
total 20
drwxr-xr-x 2 root root 4096 Jul 25 18:37
drwxr-xr-x 128 root root 12288 Jul 25 12:51
-rw-r--r-- 1 root root 616 Jul 25 18:37 30-cloun-init.yaml
etc/netplan/50-cloud-init.yaml :
network:
renderer: NetworkManager/ networkd
ethernets:
enp3s0:
addresses: [192.168.1.7/24]
gateway4: 192.168.1.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
dhcp4: no
version: 2
marco@pc01:$ sudo netplan apply
sudo: netplan: command not found
对于 sudo llshw -c network ：请参见上文
5° 更新：dpkg -l 的结果网络计划
marco@pc01:$ dpkg -l *netplan*
Desired=Unknown/Install/Remove/Purge/Hold
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-
pend
Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
Name Version Architecture Description
in netplan.io <none> amd64 (no description
available)
6° 更新：sudo lshw -c network
marco@pc01:$ sudo lshw -c network
*-network DISABLED
description : Ethernet interface
product: RTL811178168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor CO., Ltd.
physical id: 0
bus info: pci@000:03:00.0
logical name: enp3s0
version: 11
serial: 78:24:af:43:ef:5c
size: 100 Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33 Mhz
capabilities: pm msi pciexpress msix vpd bus_master cap_list
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd
1000bt 1000bt-fd autonegotiation
configuration: autonegotiaion=on broadcast=yes driver=r8169
driverversion=2.3LK-NAPI duplex=full latency=0
link=no multcast=yes port=MII speed=100Mbit/s
resources: irq:18 ioport:d000(size=256) memory:f7200000-f7200fff
memory:f2100000-f2103fff
*-network DISABLED
description: Wireless interface
product: AR9227 Wireless NEtwork Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@0000:05:00.0
logical name: wlp5s0
version: 01
serial: c0:4a:00:09:0e:80
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ath9k driverversion=3.15.0-55-
generic firmware=N/A latency=168 link=no
multicast=yes wireless=IEEE 802.11
resources: irq:19 memory:f7100000-f10ffff
*-network:0
description: Ethernet interface
physical id: 2
logical name: docker0
serial: 02:42:62:12:98:6e
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3
firmware=N/A ip=172.17.0.1 link=no multicast=yes
*-network:1
description: Ethernet interface
physical id:3
logical name: br-4f9fe03b1a66
serial: 01:42:fc:9e:92:1c
capabilities: ethernet physical
consiguration: broadcast=yes driver=bridge driverversion=2.3
firmware=N/A ip=172.22.0.1 link=no multicast=yes
7°更新：
Two disks:
1° disk:
/dev/sda1 1M BIOS boot
/dev/sda2 1G Linux filesystem /dev/sda3 232G Linux filesystem
with sudo fsck -f : everything ok ;
2° disk:
/dev/sdb1 1M BIOS boot
/dev/sdb2 232G Linux filesystem
sudo fsck -f /dev/sdb1
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Supeblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block whule trying to open
/dev/sdb1
The superblock could not be read or does not describe a valid
ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then
the superblock is corrupt, and you might try running e2fsck with an
alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
即使 /dev/sdb1 可能包含损坏的超级块，我还可以安装 netplan 吗？
8°更新：
ubuntu@ubuntu:$ sudo fsck -f /dev/sda2
fsck fromutil-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: 309/65536 files (2.9% non-contiguous), 48744/262144 blocks
ubuntu@ubuntu:$ sudo fsck -f /dev/sdb2
fsck from util-linux 2.31.1
9°更新：修改/etc/netplan/01-network-manager-all.yaml后：
ubuntu@ubuntu:/etc/netplan$ sudo netplan --debug generate
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:4715): DEBUG: 15:57:43.284: Processing input file
/etc/netplan/01-network-manager-all.yaml..
** (generate:4715): DEBUG: 15:57:43.285: starting new processing pass
to 1
** (generate:4715): DEBUG: 15:57:43.285: Configuration is valid
** (generate:4715): DEBUG: 15:57:43.285: Generating output files..
** (generate:4715): DEBUG: 15:57:43.285: NetworkManager: definition
enp3s0 is not for us (backend 1)
答案1
您的/etc/network/interfaces文件应该是：
auto lo
iface lo inet loopback
您的/etc/netplan/*.yaml文件应该是：
network:
version: 2
renderer: networkd
ethernets:
enp3s0:
addresses: [192.168.1.7/24]
gateway4: 192.168.1.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
然后你应该执行：
sudo netplan generate# 生成配置文件
sudo netplan apply # 应用配置
reboot # 重启计算机
更新＃1：
你的计算机确实有些奇怪...
该
sudo lshw -C network命令没有给出完整的答案除非是手动输入错误，否则
/etc/netplan目录和文件内容很奇怪netplan 似乎未安装
在我们重新安装 netplan 之前，您最好检查一下您的文件系统……
- 启动至 Ubuntu Live DVD/USB
terminal按Ctrl+ Alt+打开窗口T- 类型
sudo fdisk -l - 识别“Linux 文件系统”的 /dev/sdXX 设备名称
- 输入
sudo fsck -f /dev/sdXX，替换sdXX为您之前找到的数字 fsck如果有错误则重复命令- 类型
reboot
现在编辑您的 .yaml 文件并继续我原来的答案。
更新 #2：
我建议此时重新安装服务器，而不是尝试修补损坏的服务器。
答案2
这听起来类似于另一篇关于在一切正常运行很长一段时间后突然出现意外网络故障的帖子。
系统经常会自动更新，而新的更新会对您现有的芯片组产生“过敏”（只是用“过敏”这个词来表示错误）。
您可能需要执行以下操作来查找您的芯片组
- linux - linux系统grep 以太网
然后，您可能不得不使用 USB 驱动器和 SneakerNet，使用另一台计算机或移动设备搜索芯片组的最新驱动程序。我还有一个 USB 以太网适配器，它经常让我在这种情况下无需使用 SneakerNet，让我重新上网，这样我就可以工作，还可以下载使板载以太网芯片组再次工作所需的驱动程序和实用程序。
希望它能有所帮助并祝你好运。