June 7, 200917 yr I am starting to have an issue where the unRAID box is unavail on the network. This usually happens when copying large amounts of data (5+ gb) to/from the array. The kernel isnt crashing (comfirmed by being able to hook up monitor and keyboad to local machine and being able to login and locally use the box). And the NIC is good (confirmed by having no issuse with a bootable OS (WinPE and Fedora then copying large amounts of data to/from). The box also passes all memory tests. These issues happen with using the onboard nic or USB nic or PCI nic. Ive tried different ports on my switch all with the same issue. I am also unable to access unRAID via http from any Win7/IE8 machines (this issue appered with the network access issues)... Hopefully someone isnt as confused about this issue as I am ??? ??? ??? ??? ??? ??? ???
June 7, 200917 yr Author One more piece of info. The computer that im doing the copying to/from is still able to see and navigate the file structure of the unRAID box. Network info modem to nic 1 of XP box using ICS for DHCP nic 2 of XP box to 5 port gigabit switch unRAID box and Win7 laptop connected to switch
June 7, 200917 yr One more piece of info. The computer that im doing the copying to/from is still able to see and navigate the file structure of the unRAID box. Network info modem to nic 1 of XP box using ICS for DHCP nic 2 of XP box to 5 port gigabit switch unRAID box and Win7 laptop connected to switch Tom frequently updates/includes newer versions of SAMBA on unRAID releases. Same with network card drivers. It is not impossible for one or the other to have a memory "leak" that eventually uses up all your free memory. Have you looked in the syslog when these errors occur to see if it has any indication you running out of free memory? What version of unRAID are you using? It might be possible for you to upgrade/downgrade to see if a different version has the same problem. I see that version 3.3.4 of SAMBA is out, and in its release notes are these: * Fix smbd crash for close_on_completion. * Fix a memleak in an unlikely error path in change_notify_create(). Who knows, you might be tripping one of those. Joe L. Joe L.
June 9, 200917 yr Author Im using 4.3.. Its the only version ive ever used. Well, I did use 4.2 for a week or so before 4.3 was released.... There is 1.5gb of RAM in the unRAID box (and a old P4 ASUS mobo) I can see if I can get to the syslog.. Its starting to happen very frequently now. To the point that unRAID box is completly unusable. Ive noticed something else happening now that Im starting to pay closer attention to it.. There is an 8 drive array. disk7 is empty (its not new to the array).. When I get these symptoms, there is a ton of errors on this drive (one for every READ/WRITE attempt)!! Im not using user shares and not accessing that disk!! I see if I can grab a screen cap (its kinda difficult as I use the Win7 laptop for everything on the internet and I cant access the unRAID box from it).. Should I attempt upgrading to a newer ver of unRAID?? granted there is mostly video collection and I still have access to everything, but losing 6tb of data would suck.....
June 9, 200917 yr The box also passes all memory tests. When you said the box passes all memory tests, are you referring to the BIOS memory self-test at boot up? or are you referring to the "memtest86" that is built into the boot menu of unRAID? If the latter, did you let it run overnight? (or at least for a few hours and several cycles)? The errors you are describing can easily fill your syslog, use up all available memory, and result in unRAID killing off processes... (resulting in no connectivity) I'd like to see a copy of your syslog... And yes, you should upgrade too, once things settle down.. many fixes since 4.3 Joe L.
Archived
This topic is now archived and is closed to further replies.