enternoescape

Members
  • Posts

    3
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

enternoescape's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Found this and thought it might be helpful for those asking what did Bouxer do. I'm having a similar issue, but the solution is not here.
  2. You are correct. I have since revised this system because actually noapic seemed to fix the issue, but didn't actually. I happened to have a PCIe Intel NIC and popped it in the case. The NIC issues went away. Then there was another problem. I only have 2 PCIe slots I can use, so I got an Intel PCI NIC. My logic was it's going to be the only PCI device. The PCI NIC does work better than the onboard NICs sadly. I also did some quick benchmarks between the PCIe NIC and the PCI NIC for typical file transfers and got identical transfer speeds. I didn't hit 500mbps once with either NIC which is probably a limitation of the settings on the NIC, not the actual card or bus. The computer I was testing with has an Intel NIC as well that is optimized and I know I can get throughput in the high 800mbps. These are the results I got from copying files from multiple hard drives to a Windows 2003 Server simultaneously: 1 Disk = 280mbps 2 Disks = 420mbps 3 Disks = 490mbps Just in case anyone else decides to use a PCI card (not PCIe) with this motherboard, you should know that unRAID will boot with eth0 and eth1 as the onboard adaptors. This means your PCI adaptor will be eth2 and will not be up or already configured. There is no option in the BIOS to disable the onboard NICs. I added these lines to the go script to make this work for me: # Removes the driver for Realtek Adaptors rmmod r8169 ifconfig eth2 up ifconfig eth2 <ip address> netmask <subnet> ifconfig eth2_rename up ifconfig eth2_rename <ip address> netmask <subnet> I've had the adaptor change names on me before which was confusing, so that's why it references two different adapters. I don't have a gateway defined in my script because my server is strictly for storage and there's no reason for it to know how to get outside my network. You would also of course need to change <ip address> and <subnet> to your unRAID server's IP address and subnet respectively.
  3. I currently am using this motherboard with an Adaptec 2241000-R 1430SA and a Supermicro AOC-SAT2-MV8. My hope was to be able to use 2 of the Supermicro AOC-SASLP-MV8 controllers and get 20 high speed connections, but due to the issues people have reported this setup will suffice for now. The parity calculation speed on 7 1.5TB WD green drives connected to the motherboard and Adaptec was somewhere around 50KB/s and dropped to 30KB/s towards the end of calculation. Considering I was using this on a platform with a 2GHz processor before I moved it over to this motherboard and the performance is identical, the Atom 330 is more than able for unRAID. On a side note, I did originally have an issue when I would pull from two computers at once saturating the gigabit connection, the entire server would completely disappear from the network after about 5 minutes of this traffic. There's nothing in the log indicating an error, I couldn't ping, telnet, access the web page or open a share. I ran ifconfig on the server revealed it still had an address and was connected, but from the server I couldn't ping anything on my local network. I relaunched emhttp and everything would magically come back to life. I saw a post regarding APIC issues and changed in syslinux.cfg the line: append initrd=bzroot to append initrd=bzroot noapic Now it seems to be working much more reliably. I personally would probably buy another one because the apic issue outlined here is a common one with linux apparently.