Jump to content
XPEnology Community

Search the Community

Showing results for '"Intel PRO 1000"'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

  1. nasir32

    Working DSM 6

    Thanks for sharing your experience guys. I was able install DSM 6 and all the latest update on my ASUSTOR NAS under VirtualBox. I've assigned 2GB ram and 2 cores for this VM from my 8GB Quad core system Just followed instructions from the above mentioned post. I installed online version rather than using provided PAT file. Network card I used is Intel PRO 1000 (Bridge) Only thing that i would like to mention It only works under INSTALL, couldn't make it work under RUN Installed surveillance package and using my cameras, everything is running great Before this I've been using DSM 5.2.5644 for long time with no issue, just turned that VM off
  2. Intel Pro 1000 (CT/GT) sind zu 99,9% empfehlenswert bzw. haben bei mir noch nie Probleme unter XPEnology (und Windoof) gemacht. Relativ günstig zu bekommen, sowohl neu als auch gebraucht.
  3. Bonjour, Je rencontre des vitesses de lecture et d'ecriture vraiment lente avec mon installation. J'ai installé la version "XPEnology DS3612xs DSM 4.1 build 2668++ (more hardware)" sur mon shuttle K45 (Chipset Intel 945GC + ICH7) sur lequel j'ai ajouté une carte intel pro 1000 Dual MT Jai deux disque dur un caviar black 1TO et un seagate hd240UI. (Jai un message Cache en ecriture du disque desactivé veuillez mettre a jour firmware pour activer le cache) Je suis en firmware 1AQ1001 Rien n'y fait... c'est toujours aussi lent je ne depasse pas 8mo/sec en transfert. J'ai aussi essayer la version repack 1.2 du 07/07/2013 mais pareil. Pensez vous que cela vienne de mes disques ?
  4. Confirming what stanza said, I'm running Intel Pro 1000 PT Quad NICs which are also PCIe x4 without a problem. Have you reseated the cards, also check in the bios if your PCI express slots are running with Generation 1 or Generation 2 support - might make a difference.
  5. OK here is a quick guide to speed up your network transfers, either between multiple Xpenologies or between your Xpenology NAS and say a Linux Server setup for Virtual Machine Hosting Requirements Each computer needs multiple lan interfaces, how you get there doesn't matter.... Either multiple single interfaces (onboard Motherboard plus add in single port cards) Or adding in Multi port cards Seems at present (not confirmed) you are limited to a maximum of 8 interfaces using DS3612xs version... tho depending on your final outcome requirements / configuration that might be enough....your mileage may vary The hardware I am using for the below guide is Intel Socket 775 Serverboard Model S3200SH 4Gb Ram Dell H310 SAS HBA 7 a 450G Drives in a SHR1 Config Intel Pro 1000 PCI Ethernet Adapter in a PCI Slot HP NC360T Dual Port Ethernet Adapter in a x4 PCI-E slot For a total of 4 x 1Gb lan ports So first Lets configure Xpenology properly, with the correct number of interfaces and the corresponding correct matching MAC addresses How do we do that? Easiest way I have found is as follows SSH into your Xpenology box Dump the dmesg output and search it for anything that looks like eth (as eth0 eth1 etc etc will be your lan interfaces if using standard network ports......for infiniband / 10g networking it will be something else) so lets run the above and dump the output into a file for browsing through > dmesg | grep “eth” > /tmp/dmesg.txt Which saves the output in our tmp directory into a file called dmesg.txt Now we can open this file and read / scroll through it to find out our “REAL” MAC addresses of the lan interfaces >vi /tmp/dmesg.txt in my case the contents show [ 0.232970] ACPI Error: Method parse/execution failed [\_SB_._OSC] (Node ffff88011f04f4c0), AE_AML_BUFFER_LIMIT (20110623/psparse-536) [ 2.993119] e1000 0000:04:01.0: eth0: (PCI:33MHz:32-bit) 00:0e:0c:82:a8:f9 [ 2.993226] e1000 0000:04:01.0: eth0: Intel(R) PRO/1000 Network Connection [ 3.191111] e1000 0000:04:02.0: eth1: (PCI:33MHz:32-bit) 00:15:17:28:06:58 [ 3.191216] e1000 0000:04:02.0: eth1: Intel(R) PRO/1000 Network Connection [ 3.191343] jme: JMicron JMC2XX ethernet driver version 1.0.8 [ 4.934800] e1000e 0000:02:00.0: eth2: (PCI Express:2.5GT/s:Width x4) 00:1f:29:55:21:60 [ 4.934934] e1000e 0000:02:00.0: eth2: Intel(R) PRO/1000 Network Connection [ 4.935120] e1000e 0000:02:00.0: eth2: MAC: 0, PHY: 4, PBA No: D51930-004 [ 5.117775] e1000e 0000:02:00.1: eth3: (PCI Express:2.5GT/s:Width x4) 00:1f:29:55:21:61 [ 5.117909] e1000e 0000:02:00.1: eth3: Intel(R) PRO/1000 Network Connection [ 5.118095] e1000e 0000:02:00.1: eth3: MAC: 0, PHY: 4, PBA No: D51930-004 [ 19.427330] usbcore: registered new interface driver ethub [ 20.217839] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 21.234865] ADDRCONF(NETDEV_UP): eth1: link is not ready [ 22.488838] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 23.502336] ADDRCONF(NETDEV_UP): eth3: link is not ready [ 23.519820] e1000: eth3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 23.520646] ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready (you might have to scroll right to see the full lines of output....depending on screen resolution) So now we can find anything that looks like a MAC Address and either copy paste them somewhere or write them down. In the above example these 4 lines look interesting [ 2.993119] e1000 0000:04:01.0: eth0: (PCI:33MHz:32-bit) 00:0e:0c:82:a8:f9 [ 3.191111] e1000 0000:04:02.0: eth1: (PCI:33MHz:32-bit) 00:15:17:28:06:58 [ 4.934800] e1000e 0000:02:00.0: eth2: (PCI Express:2.5GT/s:Width x4) 00:1f:29:55:21:60 [ 5.117775] e1000e 0000:02:00.1: eth3: (PCI Express:2.5GT/s:Width x4) 00:1f:29:55:21:61 So now we have our 4 MAC Addresses we can edit the grub.conf file of the USB stick so we are using correct and REAL MAC Addresses of our hardware Though the numbering of the interfaces get shuffled due to the file /etc.defaults/synoinfo.conf Which has the line netif_seq=”0 2 1 3” Which reorders things and does your head in a little trying to figure out which is which Anyway in my case it ended up as follows Onboard > eth3 > Lan 4 NC360T Top Port > eth0 > Lan 1 PCI Card > eth1 > Lan 2 NC360T Bottom Port > eth2 > Lan 3 Your best bet is to plug in one cable at a time and see which interface connects then edit the grub.conf file with vi and change it to match > vi /volumeUSB1/usbshare/boot/grub/grub.conf #serial --unit=0 --speed=115200 #terminal serial default 0 timeout 3 fallback 0 title XPEnology DSM 4.3-3827 v1.1 Beta7 - HBA (SCSI/SAS) root (hd0,0) # vender /vender show # hw_model kernel /zImage root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3612xs mac1=001F29552160 mac2=000E0C82A8F9 mac3=001F29552161 mac4=001517280658 sn=B3J4N666333 initrd /rd.gz Save the file and reboot Your IP Address might change here, depending on if it's set to DHCP or manual Log back into your Xpenology web interface and open system information and Control-Panel Network to check your work Now we can make a Bonded network interface to try and speed up things a little To do this, open control-panel, go to network, then network interface tab. Select Create button and then next (you can leave it on IEEE 802ad Dynamic Link Aggregation) as we will manually change this after by editing some files Choose which interfaces you want to bond together, which in my case was Lan 1 and Lan 3 Click Next and set a manual IP Address My normal network addresses for home use are in the 10.0.0 range.... so for this separate network I made the IP Address 192.168.0.1 with a subnet of 255.255.255.0 Jumbo Frames I left as default for now. Click Apply and your bond is created, tho will show errors as we have not setup any Network Switch with an 802ad pair of ports. Safely ignore this Here is where you choose how you would like to connect / cable the computers together. If you have just 2 Xpenology boxes, the simplest way would be direct connections.... that is connect a cable from your bonded ports to each other Modern lan interfaces shouldn't need cross over cables to do this) So in my test example I am connecting an Xpenology box to a Linux (Ubuntu 12.04 Box) which both have multi port lan cards I simply connect port 0 to port 0 and port1 to port 1 with short cables If you are looking to connect multiple machines together, then for a basic setup you need 2 separate switches Connect all devices port 0 to one switch and all devices port 1 to the second switch. (it will not work using only one switch unless you perform some vlan magic....but that's another advanced configuration for later) Now we need to go and manually edit a config file to change the setup from “IEEE 802ad Dynamic Link Aggregation Mode” to use instead the hidden “Balance Round Robin Mode” so if we look in the directory /etc/sysconfig/network-scripts/ We see there are config files for up to 8 eth ports and also a newly created ifcfg-bond0 config file all we need to change is the ifcfg-bond0 file from DEVICE=bond0 BOOTPROTO=static ONBOOT=yes IPADDR=192.168.0.1 NETMASK=255.255.255.0 BONDING_OPTS="mode=4 use_carrier=1 miimon=100 updelay=100 lacp_rate=fast" USERCTL=no to DEVICE=bond0 ONBOOT=yes BONDING_OPTS=”mode=0 use_carrier=1 miimon=100 updelay=100″ USERCTL=no BOOTPROTO=static IPADDR=192.168.0.1 NETMASK=255.255.255.0 Save the file and reboot the Xpenology box How to configure your Linux Box is up to you......as each and every version of Linux does it slightly differently. If your joining 2 Xpenologies together.... simply do as above on the second box... but use a different IP Address naturally. Eg Xpenology1 - 192.168.0.1 255.255.255.0 Xpenology2 -192.168.0.2 255.255.255.0 No for some tests to see if we improved things In this test example, I created a shared folder, and shared it out with NFS. On the Linux Box I mounted this NFS share and will use DD to write a 20Gig file to the share and then after waiting for a flush will read it back again. 1st test I will do a baseline so will pull out 1 lan cable to simulate a normal everyday connection to see how things perform Results Write Test with 1 Cable Connected MTU = 1500 P55-UD3R:~$ sudo time dd if=/dev/zero of=/VMachines/ddtest2 bs=1024000 count=20000 20000+0 records in 20000+0 records out 20480000000 bytes (20 GB) copied, 176.601 s, 116 MB/s 0.01user 12.70system 2:57.29elapsed 7%CPU (0avgtext+0avgdata 7728maxresident)k 0inputs+40000000outputs (0major+533minor)pagefaults 0swaps Read Test with 1 Cable Connected MTU = 1500 P55-UD3R:~$ sudo time dd if=/VMachines/ddtest2 of=/dev/null bs=1024000 20000+0 records in 20000+0 records out 20480000000 bytes (20 GB) copied, 178.783 s, 115 MB/s 0.01user 16.17system 2:58.78elapsed 9%CPU (0avgtext+0avgdata 7712maxresident)k 40000000inputs+0outputs (0major+532minor)pagefaults 0swaps Not bad, we are getting a nice 100+ Mb/s thruput in each direction with a standard MTU of 1500 Write Test with 2 Cables Connected MTU = 1500 P55-UD3R:~$ sudo time dd if=/dev/zero of=/VMachines/ddtest2 bs=1024000 count=20000 20000+0 records in 20000+0 records out 20480000000 bytes (20 GB) copied, 118.625 s, 173 MB/s 0.02user 12.88system 1:58.62elapsed 10%CPU (0avgtext+0avgdata 7712maxresident)k 0inputs+40000000outputs (0major+532minor)pagefaults 0swaps Read Test 2 with Cables Connected MTU = 1500 P55-UD3R:~$ sudo time dd if=/VMachines/ddtest2 of=/dev/null bs=1024000 20000+0 records in 20000+0 records out 20480000000 bytes (20 GB) copied, 120.116 s, 171 MB/s 0.02user 15.05system 2:00.11elapsed 12%CPU (0avgtext+0avgdata 7712maxresident)k 40000024inputs+0outputs (1major+531minor)pagefaults 0swaps Nice, we improved the speed to nice 170+ Mb/s thruput in each direction with a standard MTU of 1500.....CPU load jumps up to around 50% It's not a double in throughput as we thought....so Now lets try again 2 x cables but bumping the MTU to 9000 (enabling Jumbo Frames) Write Test with 2 Cables Connected MTU = 9000 P55-UD3R:~$ sudo time dd if=/dev/zero of=/VMachines/ddtest2 bs=1024000 count=20000 [sudo] password for antonyplatt: 20000+0 records in 20000+0 records out 20480000000 bytes (20 GB) copied, 113.281 s, 181 MB/s 0.00user 12.28system 1:53.28elapsed 10%CPU (0avgtext+0avgdata 7728maxresident)k 0inputs+40000000outputs (0major+533minor)pagefaults 0swaps Read Test 2 with Cables Connected MTU = 9000 P55-UD3R:~$ sudo time dd if=/VMachines/ddtest2 of=/dev/null bs=1024000 20000+0 records in 20000+0 records out 20480000000 bytes (20 GB) copied, 115.037 s, 178 MB/s 0.04user 13.80system 1:55.03elapsed 12%CPU (0avgtext+0avgdata 7712maxresident)k 40000000inputs+0outputs (0major+533minor)pagefaults 0swaps Similar, though slightly improved throughput.....but our CPU has lessened down to around 35% which helps. And just for fun, I added a 3rd lan port into the bond (tho it's only a PCI card) to see if things improve any more (squeeze the last little bit extra) Write Test with 3 Cables Connected MTU = 9000 P55-UD3R:~$ sudo time dd if=/dev/zero of=/VMachines/ddtest2 bs=1024000 count=20000 20000+0 records in 20000+0 records out 20480000000 bytes (20 GB) copied, 71.1939 s, 288 MB/s 0.00user 13.27system 1:11.19elapsed 18%CPU (0avgtext+0avgdata 7712maxresident)k 0inputs+40000000outputs (0major+532minor)pagefaults 0swaps Read Test with 3 Cables Connected MTU = 9000 P55-UD3R:~$ sudo time dd if=/VMachines/ddtest2 of=/dev/null bs=1024000 20000+0 records in 20000+0 records out 20480000000 bytes (20 GB) copied, 82.8826 s, 247 MB/s 0.03user 11.24system 1:22.88elapsed 13%CPU (0avgtext+0avgdata 7728maxresident)k 40000024inputs+0outputs (1major+532minor)pagefaults 0swaps Spikes from 245 up to 341Mb/s is nice..... But I think my Xpenology box has hit it's limit with the current HDD's installed and hardware Please also NOTE, only use an MTU of 9000 if your switch supports it, or you are direct connecting. So if you had a setup with 4 x decent PCI-E based lan interfaces / jumbo frames and a good CPU plus some driver tweaking should get roughly 450Mb/s I would guesstimate. I have uploaded a video here for those who like to see pretty graphs, showing a write then a read to the Xpenology box from the Linux Box. You will note also how wildly inaccurate the Synology Resource monitor is. Video 30.2Mb MKV File http://www.stanzabike.net/images/xpenology/test_bond2-MTU9000.mkv Have fun
  6. EDIT: hAD THE realtek nice replaced...now i have an intel pro 1000 pt dual port nic in the computer, running with e1000e drivers. still network transfers are averaging 27mb per second which is kind of horrible. anyone have any ideas? Hello, I have 2 Xpenology systems up running on DSM 5 4528 update 2 with nano boot 5.0.3.2 One system has an intel nic the other has one onboard realtek 8111e and a second one mounted. now my big problem is this: Wake On lan won't work on the realtek system, on intel nic it works like a breeze. second thing and that is the worst part is, that i have really bad network speeds on realtek system. when copying files, on intel i have up to 100Mb/s which is pretty much gigabit speed, on realtek i have around 30 max...both show a gigabit connection. i suppose this is a driver issue... running lspci -v gives me this: 04:00.0 Class 0200: Device 10ec:8168 (rev 06) Subsystem: Device 1849:8168 Flags: bus master, fast devsel, latency 0, IRQ 44 I/O ports at c000 Memory at f0004000 (64-bit, prefetchable) Memory at f0000000 (64-bit, prefetchable) Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Kernel driver in use: r8169 01:00.0 Class 0200: Device 10ec:8168 (rev 06) Subsystem: Device 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 43 I/O ports at e000 Memory at f7d00000 (64-bit, non-prefetchable) Memory at f0100000 (64-bit, prefetchable) Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number d1-54-00-00-68-4c-e0-00 Kernel driver in use: r8169 What am i supposed to do? is there a wa to make nano boot run proper drivers? i am not that good at linux and understanding the whole nano boot thing as to get it by myself...but the speed really are horrible...
  7. Ребята подскажите как можно добавить еще сетевую intel pro 1000 на установленную систему? при установке не загрузилась система почему то. нет дров? или...что надо сделать?
  8. stanza oringially posted on another thread 17 Feb 2014 16:29 but no reply so far I have installed the firmware [XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2)] since Sep 2013 on a HP54L (only one hp54l on the lan and I don;t change MAC/serial no) but one great issue annoy me without solution-the NAS disappear regularly (around once each month) without any response and I can only turn off and turn on again to regain access. I am horrified and worried about data loss Original I plugin an additional Intel Pro 1000 PT Dual Port Server NIC during the install after the machine hang after 1 week time for twice, I remove the card it is better but still hang up almost every month any idea to fix that should I reinstall the whole thing (i worry about wrap out all my server data and photos as I don;t have >2TB HD to backup again the 4x1TB raid) Any hint why the NAS disappear regularly or should I just upgrade!!! any other has similiar experience Speedhk
  9. Trantor Thank you for your great work I have installed the firmware since Sep 2013 on a HP54L (only one hp54l on the lan and I don;t change MAC/serial no) but one great issue annoy me without solution-the NAS disappear regularly (around once each month) without any response and I can only turn off and turn on again to regain access. I am horrified and worried about data loss Original I plugin an additional Intel Pro 1000 PT Dual Port Server NIC during the install after the machine hang after 1 week time for twice, I remove the card it is better but still hang up almost every month any idea to fix that should I reinstall the whole thing (i worry about wrap out all my server data and photos as I don;t have >2TB HD to backup again the 4x1TB raid) or should I just upgrade!!! any other has similiar experience Speedhk
  10. Trantor Thank you for your great work I have installed the firmware since Sep 2013 on a HP54L (only one hp54l on the lan and I don;t change MAC/serial no) but one great issue annoy me without solution-the NAS disappear regularly (around once each month) without any response and I can only turn off and turn on again to regain access. I am horrified and worried about data loss Original I plugin an additional Intel Pro 1000 PT Dual Port Server NIC during the install after the machine hang after 1 week time for twice, I remove the card it is better but still hang up almost every month any idea to fix that should I reinstall the whole thing (i worry about wrap out all my server data and photos as I don;t have >2TB HD to backup again the 4x1TB raid) or should I just upgrade!!! any other has similiar experience Speedhk
  11. Same here, I want to passthrough LSI 9207-8i in IT mode and Intel Pro 1000/PT dual nic to Synology, this would be a perfect VM
  12. Merci pour ton aide, Dans un premier temps j'ai fait un test avec une carte reseau dual port intel pro 1000 qui est parfaitement reconnue. A ma grande deception je crois que le chipset "ICH7 Base" de la K45 ne supporte pas le AHCI est donc je ne parviens pas a faire détécter mes disques dur Une solution possible ou il faut radicalement changer de carte mere ?
  13. Hi, I'm trying to use a shuttle k45 with this build and no success. I put an intel pro 1000 network card and it's better but the chipset is a 82801GB (ICH7) Base (No AHCI) Is it possible to install DSM4.2 on it or not ? Everytime i'm stuck at he hard drive recognition in the install process. BTW ! Could you please help me to find a small rig small format itx with 2 x 3.5hdd low power consumption Thx
×
×
  • Create New...