May 17, 201115 yr Hi I'm wondering if someone can take a look at this kernel panic message and provide any words of wisdom or even vague ideas. I seem to be able to make copies from my Mac Finder windows to the Unraid server with no problems, but whenever I use the backup program Such as carbon copy cloner or data backup the Unraid server freezes and I have to reboot. It might be worth noting that I have recently downgraded from version 5.0.6 Beta back to 4.7. I am wondering if I should just do a complete clean reinstall of 4.7–––but I'm concerned that I would lose all my shares in the process. Is there a way to reinstate existing shares after doing a clean install of Unraid? I've attached a JPEG as I cannot capture syslog after the system is crashed. I can see the potential of my Unraid and I will do do anything necessary to get it working– many thanks for all forum help.
May 17, 201115 yr What is the hardware you are using? Which mobo and are you using the onboard nic? Some of the messages seem to indicate RTL8169 - most likely your onboard nic. Some of us have had same issues with Realtek and transfering large amount of data. System freeze. Put in a external NIC card (like an Intel chipset), disable onboard and all is well. Could be the reason... Shawn
May 17, 201115 yr Author Thank you Shawn! The MB is: http://www.asus.com/Motherboards/AMD_AM3/M4A89GTD_PROUSB3/#specifications It has a realtek Nic. ! Hmmm. I am also running Memtest right now... one error so far.... see attached image. Which would you try first?
May 17, 201115 yr there should never be errors in memtest. Pull a stick and run memtest again one stick at a time. When one of, or both, sticks fail replace them.
May 17, 201115 yr Author I tested one stick of RAM at a time, sure enough the first one was bad. I am running a pretty big back up now and so far so good. I also ordered a new Intel-based NIC card should be here tomorrow and will try that and report back as well. Thanks for all your help I really appreciate it. Should've posted to the board much sooner.
May 18, 201115 yr Author Every backup I've run since replacing the RAM has been flawless. Thanks for the suggestions–as obvious and simple as they might've been to you they were pretty important to me, I do appreciate it.
May 18, 201115 yr Glad things are working out - esp that you caught the bad RAM. That can be a real pain... Shawn
May 19, 201115 yr Author I tried installing the Intel card: http://www.intel.com/products/desktop/adapters/gigabit-ct/gigabit-ct-overview.htm and the Unraid system doesn't see it. I've disabled the onboard LAN card which is a realtek on an Asus motherboard: http://www.asus.com/Motherboards/AMD_AM3/M4A89GTD_PROUSB3/#specifications Do I need to do anything else other than disable the onboard LAN? I realize this is not exactly an Unraid question and hope it's not inappropriate here.
May 19, 201115 yr You disabled the onboard through the BIOS right? From a command, run "ifconfig" and "ethtool eth0" and see what it spits back at you? You may just need to manually conifgure the card... Shawn
May 19, 201115 yr Author Yes, I did disable the onboard through the bios but was unable to make a connection through the new NIC card. Will try to do a command line tomorrow as I am in the middle of a backup now. These are the errors I'm seeing in the log as I'm doing this huge backup, have you seen this before? kernel: r8169: eth0: link upMay 18 20:42:52 Tower last message repeated 3 times May 18 20:45:36 Tower kernel: r8169: eth0: link up May 18 20:46:38 Tower last message repeated 3 times May 18 20:47:59 Tower kernel: r8169: eth0: link up May 18 20:49:25 Tower kernel: r8169: eth0: link up May 18 20:50:30 Tower kernel: r8169: eth0: link up May 18 20:51:44 Tower last message repeated 3 times May 18 20:52:58 Tower kernel: r8169: eth0: link up May 18 20:54:31 Tower last message repeated 3 times May 18 20:57:37 Tower last message repeated 3 times May 18 21:00:54 Tower last message repeated 3 times May 18 21:02:20 Tower last message repeated 2 times May 18 21:03:37 Tower last message repeated 3 times May 18 21:07:46 Tower kernel: r8169: eth0: link up May 18 21:09:05 Tower last message repeated 2 times May 18 21:10:28 Tower last message repeated 3 times May 18 21:12:02 Tower last message repeated 2 times May 18 21:13:42 Tower last message repeated 2 times May 18 21:16:08 Tower last message repeated 2 times May 18 21:17:36 Tower last message repeated 5 times May 18 21:19:19 Tower last message repeated 3 times May 18 21:20:32 Tower last message repeated 2 times May 18 21:20:59 Tower last message repeated 2 times May 18 21:21:30 Tower kernel: mdcmd (17): spindown 4 May 18 21:21:33 Tower kernel: r8169: eth0: link up May 18 21:22:46 Tower last message repeated 2 times May 18 21:24:20 Tower last message repeated 4 times May 18 21:26:16 Tower last message repeated 2 times May 18 21:37:15 Tower kernel: mdcmd (18): spindown 1
Archived
This topic is now archived and is closed to further replies.