Andy74 Posted December 31, 2011 Posted December 31, 2011 Hello, I have run unRaid for some years now and a while ago I upgraded to 4.7. Unfortunately my motherboard died a few weeks ago and now I have replaced it with a new one. Everything looks OK in the webGUI and all the disks are green, the parity is valid. I can read files from the flashdrive but my other two shares is impossible to read the files. I can see the folders and the files but as soon as I try to open or copy a file its "stuck". Nothing happens for a while and then I get a sign saying that it can't reach \\tower and should check the spelling etc. I have four 1TB disks and before the motherboard failure everything worked just fine. Someone that have a clue what I can do to reach my files?
marcusone Posted December 31, 2011 Posted December 31, 2011 Have you tried pining your unraid box from the one you are trying to access when that happens? Can you open the console on the unraid box and ping your Windows box when this occurs? Are you using the same motherboard as before? Could be a network driver issue.
dgaschk Posted December 31, 2011 Posted December 31, 2011 See here: http://lime-technology.com/forum/index.php?topic=9880.0
Andy74 Posted December 31, 2011 Author Posted December 31, 2011 Ping works both ways. It's not the exact same motherboard cause its out of date but it's a similar one that matches with my cpu. On this one I had to add it with extra sata ports on an expansion card. It's no problem using files on the flashdrive holding unRaid. This time I also attach the systemlog. systemlog.txt
Andy74 Posted January 4, 2012 Author Posted January 4, 2012 Anyone that have a clue that can solve my problem?
evans036 Posted January 4, 2012 Posted January 4, 2012 try logging into your unraid server using a direct attached keyboard/monitor and then issue command: ifconfig this should display (amonst other things) your ip address. there will be a section likely called 'eth0' which should look something like: eth0 Link encap:Ethernet HWaddr 00:21:5E:C4:0A:6C inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::221:5eff:fec4:a6c/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:4649351622 errors:14 dropped:1890787648 overruns:0 frame:14 TX packets:5768769300 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1265032277532 (1.1 TiB) TX bytes:6455141397173 (5.8 TiB) then try pinging that ip address (in eg above that would be 192.168.1.11) from another computer. hope this helps, steve
Andy74 Posted January 5, 2012 Author Posted January 5, 2012 I don't understand how a ping could help. I have allready tried ping from a windows computer and I have pinged the windows computer from the unRaid server. No problems there. I can view the web GUI and it works OK. I can see my folders and files but I can't open or copy files from my ordinary shares. I can open and copy files from the flashdrive holding the unRaid OS.
dgaschk Posted January 5, 2012 Posted January 5, 2012 What MB are you using? Your syslog shows symptoms of an Artheros Ethernet chip. These are not compatible with version 4.7. I think they work with the 5.0 beta. Your other option is a Intel PCI gig-E card. Note the garbage characters: Dec 19 06:54:06 NAS kernel: 6 disabled Dec 19 06:54:06 NAS kernel: 7 disabled Dec 19 06:54:0l?IP?åâ•SÎE¯?—@@¿® ¿®#P»?AØn€ÄÜMPüÑ406, new 0x7010600070106 Dec 19 06:54:06 NAS kernel: initial memory mapped : 0 - 01800000 Dec 19 06:54:06 NAS kernel: init_memory_mapping: 0000000000000000-00000000379fe000 Dec 19 06:54:06 NAS kernel: NX (Execute Disable) protection: active D Random garbage appears periodically.
Andy74 Posted January 5, 2012 Author Posted January 5, 2012 It's a MSI G41M-P28 MB and it's Atheros networkcard. I will try to add a pci-card to solve the problem.
Andy74 Posted January 9, 2012 Author Posted January 9, 2012 I have added the pci-card and connected it to my switch but how do I "activate" it? I can't see it on my network at all. I guess unRaid still think it's gonna use the network card on the motherboard.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.