Bungy

I was just putting in an order for these too when I saw your post. Your fan supports 3 and 4 pin power inputs so either of these will work. Molex (5.25 Male) / (3.5 Female X2) , DC Y CBL. Power Cable - 8in Molex (5.25 Male) / (3.5 Female) Int. DC Power Cable - 6 Inch

I tracked down the issue to the C-compiler gcc package being installed through unmenu. Disabling re-install on reboot solved the problem. Strange, I know...

Not a problem, I appreciate the support. Which NIC do unraid users typically use? Realtek?

Thanks for the responses. I was skeptical that it was the nic since this board worked great for me for over a year. I reinstalled unraid 4.7 on my flash drive and that seems to have solved the problem. I'm going to give it a few days and if it remains stable, I'll change the subject title to [solved].

That's correct on the procedure. Boot up and then samba transfer until fail. Attached is an updated syslog with the same procedure. syslog_8-25-2011.txt

I just rebooted and attached my syslog and ifconfig eth0, ethtool eth0, and interrupts file. One thing that I changed is I switched my 640gb drive from being assigned to the cache drive to being in the array and I added a 80gb drive as the cache drive. No additional packages were installed. I don't need the additional drive at this point, so if there's a way to remove it from the array without impacting the other drives, I can try that. This issue occurs if I assign the 80gb drive to the cache or not. Also, I had a red ball next to one of my drives. I checked the drive out and found nothing wrong with it. I rebuilt the drive without any additional write errors. I am getting that distinct hard drive sound that sounds like a cricket chirping when I try to access the array. I know this isn't a typical diagonstic statistic, but just looking at the ram dropping, it appears I'm using about 6mb of ram/sec while transferring a file through ssh. Logs_8-25-2011.zip

Sorry, that may not have been clear. The one 700mb transfer made the ram about 1.5-1.6gb smaller. On the windows side it appeared as though the file was no longer available. This may be because the remaining 20-40mb of ram was too small for samba to work with. The only other client system I've tried is my XBMC live (Ubuntu maverick). This connects to the unraid box through samba shares and it will play a video file until the ram runs out and then stop. Upon trying to replay the file, it states that it is unable to locate the requested file.

I'm monitoring the memory usage using the "top" command. I don't see any error messages, it's just as I was diagnosing the problem, I noticed the ram was depleted. As a file transfers, the memory usage continually climbs upwards until there's about 40 megabytes of memory left. At this point, the transfer just stops in ssh and fails in windows using samba. I upgraded my unraid server to 2gb of ram leaving me 1.6gb of ram available after a boot up. Just transferring a 700mb file through ssh or samba cause the ram to be eventually max out out, leading me to believe it's not just a buffer issue of the file being loaded to ram before transfer (although any size file should never have this issue). For these reasons, it appears to be a memory leak.

That is really odd as I've used this same board without a problem for a year and 2 months. What would you recommend? Should I buy a new nic card? Should I try to reinstall a fresh copy of unraid on my flash drive? Or should I upgrade to unraid 5.0b10? I'd rather not upgrade to beta software because I'm concerned about losing any data, but I'm open to suggestions. And thanks a lot for the reply and the links.

Anybody have any suggestions?

I'm having an unusual issue with my unraid server running out of memory. I have 1GB of ram. While transferring files either through samba or ssh, the server runs out of ram and the file transfer fails. If I stop the array, the ram is cleared back up and returns to normal. Upon bootup there is ~600MB of ram free. Is this typical behavior? I haven't noticed this in the past before I installed an additional hard drive. I could easily just pick up more ram, but I wanted to make sure I don't have a memory leak. It seems that 600MB of ram is a lot to use during a file transfer. I've attached my syslog file. Here is my build: ECS 945GCD-M(1.0) Intel Atom 330 Intel 945GC Micro ATX Motherboard/CPU Combo SYBA SY-PCI40010 PCI SATA II (3.0Gb/s) 4 Port RAID 0/1/5/10 JBOD Card 1x Hitachi 2tb (parity) 2x WD 2.0 TB 1x WD 1.5 TB 1x WD 1.0 TB 1x Seagate 640 GB syslog.txt