thedaggert

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thedaggert

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, I have a setup a DS-918+ (DSM 6.2.2-24922 Update 4) Board: Z270 Gaming Pro with onboard INTEL NIC CPU: intel core i7-7700k kaby lake Menmory: 16 GB My problem is that when i send or copy some big files to or from my NAS the network card in my NAS resets and then the only way to connect to it again is to reboot the NAS, it get a lot of these errors when that happens. 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] TDH <0> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] TDT <1> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] next_to_use <1> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] next_to_clean <0> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] buffer_info[next_to_clean]: 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] time_stamp <109709654> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] next_to_watch <0> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] jiffies <10970a6e0> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] next_to_watch.status <0> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] MAC Status <40080083> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] PHY Status <796d> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] PHY 1000BASE-T Status <3800> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] PHY Extended Status <3000> 2020-01-13T16:22:56+01:00 synology2 kernel: [158681.377035] PCI Status <10> 2020-01-13T16:22:57+01:00 synology2 kernel: [158682.384859] e1000e 0000:00:1f.6 eth0: Reset adapter unexpectedly 2020-01-13T16:23:01+01:00 synology2 kernel: [158686.158975] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx 2020-01-13T16:23:03+01:00 synology2 kernel: [158688.378512] e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: I have tried to 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 my usb 2nd partition and overwrite the existing files (extra/extra2) That didn't help anything. When i look i kern.log i can see that the driver for my NIC is loaded: 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.225886] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.225887] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.226029] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.518273] e1000e 0000:00:1f.6 eth0: registered PHC clock 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.518277] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 4c:cc:6a:cf:51:c6 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.518279] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.518308] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.530759] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.530760] igb: Copyright (c) 2007-2014 Intel Corporation. 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.533014] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 4.2.1-k 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.533015] ixgbe: Copyright (c) 1999-2015 Intel Corporation. 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.964138] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.964139] e1000: Copyright (c) 1999-2006 Intel Corporation. 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.997416] 2020-1-13 15:24:1 UTC 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.997420] Brand: Synology 2020-01-13T16:24:01+01:00 synology2 kernel: [ 15.997421] Model: DS-918+ I haven't tried with a different NIC yet. I hope someone can help me
  2. Have you setup your NAS with static ip then you should be able to reach it from browser or Synology Assistant. You can see the IP of your NAS in Network - Network Interface.
  3. 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
  4. 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:
  5. 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?
  6. 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.
  7. 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.
  8. 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?
  9. After i got my synology installed i skipped the quick connect login at the startup because i thought i would just do that later. But when i try to login to my synology account now i just get an error, the error just says "there is an unknown error" and i cant type anything is the quick id field. Mabye some one have experienced the same issue?
  10. Thx a lot for your reply But i just realized that my CPU is a Intel so insted og using AMD i downloaded used 1.04 b and DSM_DS918+_24922 now is everything running smoothly. Sorry for being a noob but i figuered it out
  11. Hi, I am total new to XPEnology and i have looked at some guides on youtube and i have made the USB drive using synoboot ds3617_6.2 and i boot using v1.03b and i install DSM_DS3617xs_24922. After the 10 min when my Nas reboots i can't connect using find synoloy and synology assistant, even if i ping the ip i get host unreachable. Thank you in advice.