Здравствуйте.
В офисе установлен файловый сервер, Ubuntu 16.04. Две сетевухи, объединены в одну.
Что-то у них там зависло и персонал не долго думая, вытащил провод питания из розетки. Потом, опять не думая, в процессе загрузки компа, работник нажал на ресет......
Что получили: При загрузке компа, в бондинг добавляется только одна карта, соответственно, линл 1000 Mbps, вместо 2000 Mbps
root@fserver:~# ifconfig
bond0 Link encap:Ethernet HWaddr 00:07:e9:09:e7:c7
inet addr:10.10.44.131 Bcast:10.10.44.255 Mask:255.255.255.128
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:2659198 errors:0 dropped:573 overruns:0 frame:0
TX packets:10781384 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:382091090 (382.0 MB) TX bytes:17463089014 (17.4 GB)
enp2s0 Link encap:Ethernet HWaddr 00:07:e9:09:e7:c7
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25181 errors:0 dropped:138 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1911873 (1.9 MB) TX bytes:0 (0.0 B)
Interrupt:18
enp3s1 Link encap:Ethernet HWaddr 00:07:e9:09:e7:c7
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:2659198 errors:0 dropped:573 overruns:0 frame:0
TX packets:10781384 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:382091090 (382.0 MB) TX bytes:17463089014 (17.4 GB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:919 errors:0 dropped:0 overruns:0 frame:0
TX packets:919 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:99884 (99.8 KB) TX bytes:99884 (99.8 KB)
root@fserver:~#
root@fserver:~# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: transmit load balancing
Primary Slave: None
Currently Active Slave: enp3s1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: enp3s1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:07:e9:09:e7:c7
Slave queue ID: 0
root@fserver:~#
root@fserver:~# cat /var/log/syslog | grep bond0
Sep 10 09:46:28 fserver systemd-udevd[349]: Could not generate persistent MAC address for bond0: No such file or directory
Sep 10 09:46:28 fserver systemd[1]: Found device /sys/subsystem/net/devices/bond0.
Sep 10 09:46:28 fserver systemd-udevd[364]: Could not generate persistent MAC address for bond0: No such file or directory
Sep 10 09:46:28 fserver systemd[1]: Started ifup for bond0.
Sep 10 09:46:28 fserver sh[697]: Waiting for bond master bond0 to be ready
Sep 10 09:46:28 fserver sh[693]: Waiting for bond master bond0 to be ready
Sep 10 09:46:28 fserver sh[689]: Waiting for a slave to join bond0 (will timeout after 60s)
Sep 10 09:46:28 fserver kernel: [ 3.333970] bond0: Setting MII monitoring interval to 100
Sep 10 09:46:28 fserver kernel: [ 3.440038] bond0: Adding slave enp3s1
Sep 10 09:46:28 fserver kernel: [ 3.440508] bond0: Enslaving enp3s1 as an active interface with a down link
Sep 10 09:46:28 fserver kernel: [ 3.440621] bond0: Adding slave enp2s0
Sep 10 09:46:28 fserver kernel: [ 3.441149] bond0: the hw address of slave enp2s0 is in use by the bond; couldn't find a slave with a free hw address to give it (this should not have happened)
Sep 10 09:46:28 fserver sh[693]: Failed to enslave enp2s0 to bond0. Is bond0 ready and a bonding interface ?
Sep 10 09:46:28 fserver ifup[776]: /sbin/ifup: waiting for lock on /run/network/ifstate.bond0
Sep 10 09:46:30 fserver kernel: [ 5.450873] bond0: link status definitely up for interface enp3s1, 1000 Mbps full duplex
Sep 10 09:46:30 fserver kernel: [ 5.450879] bond0: making interface enp3s1 the new active one
Sep 10 09:46:30 fserver kernel: [ 5.451080] bond0: first active interface up!
root@fserver:~#
root@fserver:~# cat /var/log/kern.log | grep bond0
Sep 10 09:46:28 fserver kernel: [ 3.333970] bond0: Setting MII monitoring interval to 100
Sep 10 09:46:28 fserver kernel: [ 3.440038] bond0: Adding slave enp3s1
Sep 10 09:46:28 fserver kernel: [ 3.440508] bond0: Enslaving enp3s1 as an active interface with a down link
Sep 10 09:46:28 fserver kernel: [ 3.440621] bond0: Adding slave enp2s0
Sep 10 09:46:28 fserver kernel: [ 3.441149] bond0: the hw address of slave enp2s0 is in use by the bond; couldn't find a slave with a free hw address to give it (this should not have happened)
Sep 10 09:46:30 fserver kernel: [ 5.450873] bond0: link status definitely up for interface enp3s1, 1000 Mbps full duplex
Sep 10 09:46:30 fserver kernel: [ 5.450879] bond0: making interface enp3s1 the new active one
Sep 10 09:46:30 fserver kernel: [ 5.451080] bond0: first active interface up!
root@fserver:~#
Как лечить?
