Nas dont reconnect to lan after router Reboot

[thedaggert]

Hi,

I have installed 1.04 b and DSM_DS918+_24922 and it's working really good.
But i have one issue, and that is if i restart my router my NAS dosen't auto connect again and then i have to reboot it.

Is there anyone that have had same issue?

Edited December 28, 2019 by thedaggert

[IG-88]

router with integrated hub/switch?

maybe dhcp or nic driver problem

whats the hardware (nic)?

 

try what happens when you disconnect and reconnect the nas from the network (router not rebooted)

did you try a static ip for the nas?

[thedaggert]

Yes my router is with integrated switch.

I have setup my NAS with static mac/ip mapping in my router and on my NAS IP was set to DHCP.

I have changed the DHCP IP to STATIC IP on my NAS, and now it reconnects, it's weird because it has been working with DHCP.

Thx for the help.

[IG-88]

8 minutes ago, thedaggert said:

I have setup my NAS with static mac/ip mapping in my router and on my NAS IP was set to DHCP.

 

for this you need a MAC for the dhcp server

in this case i'd strongly suggest using the real MAC of the nic in grub.cfg so it will always have the same MAC

 

[thedaggert]

44 minutes ago, IG-88 said:

 

for this you need a MAC for the dhcp server

in this case i'd strongly suggest using the real MAC of the nic in grub.cfg so it will always have the same MAC

 

I found the MAC address for my NIC in my BIOS and typed that into the grub.cfg and i have checked that they are correct both on USB and in my router.

[IG-88]

then giving the nas a static address seems to be the best choice left

[thedaggert]

Yes for now it's the best thing.

[thedaggert]

Today i couldent contact my NAS again i can see that my router has not been restarted.

Is there mabye some log files that i could share with you so you mabye could see what could be wrong?

[IG-88]

you can open a ssh session with putty and type "dmesg" to see some log

you can also look at files in /var/log/ the files dmesg, kernel.log or messages

in this files you should see at least the time when the connection got lost

if that is possible you can install a 2nd nic, configure it to a different ip and connect it parallel to you existing connection an see if it disconnects too at the same time

 

[thedaggert]

Then i need to go to the store to buy a new one.

Should then add the mac adress of the new nic to grub.cfg aswell?

I kern.log i get this error a lot 

 

2019-12-13T13:45:04+01:00 synology2 kernel: [   18.420546] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
2019-12-13T13:45:04+01:00 synology2 kernel: [   18.420547] igb: Copyright (c) 2007-2014 Intel Corporation.
2019-12-13T13:45:04+01:00 synology2 kernel: [   18.423366] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 4.2.1-k
2019-12-13T13:45:04+01:00 synology2 kernel: [   18.423367] ixgbe: Copyright (c) 1999-2015 Intel Corporation.
2019-12-13T13:45:04+01:00 synology2 kernel: [   18.882768] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
2019-12-13T13:45:04+01:00 synology2 kernel: [   18.882769] e1000: Copyright (c) 1999-2006 Intel Corporation.
2019-12-13T13:45:05+01:00 synology2 kernel: [   18.917777] 2019-12-13 12:45:5 UTC
2019-12-13T13:45:05+01:00 synology2 kernel: [   18.917781] Brand: Synology
2019-12-13T13:45:05+01:00 synology2 kernel: [   18.917782] Model: DS-918+

2019-12-20T07:16:23+01:00 synology2 kernel: [502181.758189] e1000e 0000:00:1f.6 eth0: Reset adapter unexpectedly
2019-12-20T07:16:27+01:00 synology2 kernel: [502185.519319] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2019-12-23T12:37:57+01:00 synology2 kernel: [780682.342445] e1000e 0000:00:1f.6 eth0: Reset adapter unexpectedly
2019-12-23T12:38:01+01:00 synology2 kernel: [780686.286544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091]   TDH                  <0>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091]   TDT                  <55>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091]   next_to_use          <55>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091]   next_to_clean        <0>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091] buffer_info[next_to_clean]:
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091]   time_stamp           <12e83773e>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091]   next_to_watch        <0>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091]   jiffies              <12e837f21>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091]   next_to_watch.status <0>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091] MAC Status             <40080083>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091] PHY Status             <796d>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091] PHY 1000BASE-T Status  <3800>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091] PHY Extended Status    <3000>
2019-12-23T12:38:03+01:00 synology2 kernel: [780688.344091] PCI Status             <10>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826]   TDH                  <0>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826]   TDT                  <55>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826]   next_to_use          <55>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826]   next_to_clean        <0>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826] buffer_info[next_to_clean]:
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826]   time_stamp           <12e83773e>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826]   next_to_watch        <0>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826]   jiffies              <12e8386f0>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826]   next_to_watch.status <0>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826] MAC Status             <40080083>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826] PHY Status             <796d>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826] PHY 1000BASE-T Status  <3800>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826] PHY Extended Status    <3000>
2019-12-23T12:38:05+01:00 synology2 kernel: [780690.342826] PCI Status             <10>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902]   TDH                  <0>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902]   TDT                  <55>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902]   next_to_use          <55>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902]   next_to_clean        <0>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902] buffer_info[next_to_clean]:
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902]   time_stamp           <12e83773e>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902]   next_to_watch        <0>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902]   jiffies              <12e838ec0>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902]   next_to_watch.status <0>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902] MAC Status             <40080083>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902] PHY Status             <796d>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902] PHY 1000BASE-T Status  <3800>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902] PHY Extended Status    <3000>
2019-12-23T12:38:07+01:00 synology2 kernel: [780692.342902] PCI Status             <10>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958]   TDH                  <0>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958]   TDT                  <55>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958]   next_to_use          <55>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958]   next_to_clean        <0>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958] buffer_info[next_to_clean]:
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958]   time_stamp           <12e83773e>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958]   next_to_watch        <0>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958]   jiffies              <12e839690>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958]   next_to_watch.status <0>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958] MAC Status             <40080083>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958] PHY Status             <796d>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958] PHY 1000BASE-T Status  <3800>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958] PHY Extended Status    <3000>
2019-12-23T12:38:09+01:00 synology2 kernel: [780694.342958] PCI Status             <10>
2019-12-23T12:38:11+01:00 synology2 kernel: [780696.342761] e1000e 0000:00:1f.6 eth0: Reset adapter unexpectedly
2019-12-23T12:38:15+01:00 synology2 kernel: [780700.390883] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438]   TDH                  <0>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438]   TDT                  <34>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438]   next_to_use          <34>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438]   next_to_clean        <0>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438] buffer_info[next_to_clean]:
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438]   time_stamp           <12e83aeba>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438]   next_to_watch        <0>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438]   jiffies              <12e83b5d1>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438]   next_to_watch.status <0>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438] MAC Status             <40080083>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438] PHY Status             <796d>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438] PHY 1000BASE-T Status  <3800>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438] PHY Extended Status    <3000>
2019-12-23T12:38:17+01:00 synology2 kernel: [780702.344438] PCI Status             <10>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191]   TDH                  <0>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191]   TDT                  <34>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191]   next_to_use          <34>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191]   next_to_clean        <0>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191] buffer_info[next_to_clean]:
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191]   time_stamp           <12e83aeba>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191]   next_to_watch        <0>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191]   jiffies              <12e83bda0>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191]   next_to_watch.status <0>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191] MAC Status             <40080083>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191] PHY Status             <796d>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191] PHY 1000BASE-T Status  <3800>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191] PHY Extended Status    <3000>
2019-12-23T12:38:19+01:00 synology2 kernel: [780704.343191] PCI Status             <10>
2019-12-23T12:38:21+01:00 synology2 kernel: [780706.343245] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:

 

Edited January 2, 2020 by Polanskiman
Please use code tags when posting command line, code or logs.

[IG-88]

looks like a hardware or driver related problem

the section about the driver loading is missing (for e1000e)

whats the version number you see in the log? also there should be no odd comments when the driver loads

 

if you are not using additional drivers (as it looks to me) you can copy the extra/extra2.lzma files from here

https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

to your usb (2nd partition, it should be accessible on a windows computer), overwrite the existing files (extra/extra2) and reboot

as the driver 3.6.0 in that package is recent it might work then (you should see a change in version number in log when the driver loads)

 

 

whats the exact hardware you are using (board, nic, storage)?

 

 

[thedaggert]

I found this from last time i made a restart of the NAS:

2019-12-30T21:46:00+01:00 synology2 kernel: [   17.089068] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
2019-12-30T21:46:00+01:00 synology2 kernel: [   17.089069] igb: Copyright (c) 2007-2014 Intel Corporation.
2019-12-30T21:46:00+01:00 synology2 kernel: [   17.091408] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 4.2.1-k
2019-12-30T21:46:00+01:00 synology2 kernel: [   17.091409] ixgbe: Copyright (c) 1999-2015 Intel Corporation.
2019-12-30T21:46:01+01:00 synology2 kernel: [   17.521982] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
2019-12-30T21:46:01+01:00 synology2 kernel: [   17.521984] e1000: Copyright (c) 1999-2006 Intel Corporation.
2019-12-30T21:46:02+01:00 synology2 kernel: [   17.555738] 2019-12-30 20:46:2 UTC

That with Bold is that not the driver?

 

Specs
Board: Z270 Gaming Pro with onboard INTEL NIC
CPU: intel core i7-7700k kaby lake (not OC)
Menmory: 16 GB 
I have 6 storage drives 

 

Storage pools

 

Edited January 2, 2020 by Polanskiman
Please use code tags when posting command line, code or logs.