drcorso Posted July 27, 2011 Share Posted July 27, 2011 I just built a version 4.7 system with all the latest and greatest parts trying to build a "green" server and was wondering if I can post some information for someone to just check out and make sure everything is running OK? There are a few errors in my syslog and I am not sure if they warrant any attention or not. I don't want to start deleting my files on WHS and moving drives until I know all is well. I am a techie in real life but with very little linux experience. Outgrew my HP MediaSmart WHS and when looking to build something bigger and better I decided on unRAID rather than a bigger WHS. Current build is: Core i3-2100T 35 watt processor Gigabyte GA-Z68A-D3H-B3 motherboard (latest z68 chipset) 4GB GSkill Ripjaws Memory DDR3 1600 Norco 4220 case with 120mm fan bracket Seasonic 650 watt 80 plus gold Powersupply 2 ea SUPERMICRO AOC-SASLP-MV8 SAS Controllers 8GB Lexar Firefly thumb drive 2TB WD Black Parity Drive 500GB WD Black Cache Drive 3 ea 2TB WD20EARS Drives (not jumpered) I have a question specifically in regards to the head parking on the WD20EARS drives. For WHS we usually jumper these and change the head parking to the max. I know unraid supports AF drives so the jumper is not an issue but how about the head parking with the wdidle utility? My guess is since unraid puts drives to sleep this maybe fine. But not sure if the SAS cards introduce some other issues with this. Also for some reason if I mount a bluray ISO and try to use clownBD to pull out the main video and audio tracks it always has a problem at various points in the process. Tried UNC and Mapped drive and no luck either way. This works fine from the WHS. May be a moot point since with unRAID I can have way more storage, but I have gotten used to not having to go through the menu's on our movies. Anyone else seen anything similar? The ISO's play fine in TMT3 with MyMovies on WMC. I have already customized it with unmenu and many other packages and constantly read the wiki and the forums to find new information. Thanks in advance! -D syslog-2011-07-26.txt Link to comment
Rajahal Posted July 27, 2011 Share Posted July 27, 2011 The motherboard you are using features the Realtek 8111E NIC, which has known compatibility problems with unRAID. Search '8111E' in the forums and you'll find plenty of reports of others having issues. Maybe you will get lucking and it will work fine for you....fingers crossed. In any case, if you start having any weird errors, I would suspect the NIC first and foremost. I didn't see anything noteworthy in your syslog. I've recently discovered the ill effects of not running wdiddle on my own personal server: High LCC count on WDEARS drives In light of this, I do recommend wdiddle on your WDEARS drives. I assume it is the same procedure you are used to from your WHS servers. I don't have an exact answer to your BluRay ripping question. Why not just rip the BluRay to the local hard drive and then transfer the encode when it is done? I see no reason to keep two hard drives spinning during the ripping process when just one will suffice. Link to comment
drcorso Posted July 28, 2011 Author Share Posted July 28, 2011 Thanks for the reply... So today I transferred another 1.2 GB to the server using robocopy. Below was the speed summary using a cache drive. Could not get above 1100 on my ex470 WHS full of wd20ears. I have had some over 6000 MB/min. Using MTU 7200 on my unraid server and trendnet greenet switches. I am also connected to SATA 3 ports with Sata 3 drive for my cache and parity drive. Although they really are the same max throughput as a Sata 2 if you look at WD specs (138 MB/s or around there). Speed : 77379663 Bytes/sec. Speed : 4427.699 MegaBytes/min. So it looks like I would have had some lockups of the system and such if I had the realtek chipset issue. None yet and had the system about a month now. One thing I may be doing different than other is I am using DHCP rather than a static address. I control a static assigned dhcp address at my router instead. Also the MTU setting of 7200 seems to work great at my house. On the wdidle thing... in the past I always used my desktop which has all hot swap drive bays to pull out my drive and put in the green drive and boot with a cd to run wdidle. Do you think I do that right in the server in this case since these are using SAS/Sata connections? I will try anyway but thought I'd ask. That was the same thought I had on the bluray thing I had. I will just stick with that. Thanks again... Link to comment
drcorso Posted September 27, 2011 Author Share Posted September 27, 2011 I realize I probably need to post again but wanted to at least update my original post in case anyone finds this. I spoke too soon on the "RTL8111E" NIC. The issue has finally hit me 3 months later. Seems the NIC comes back after my drives go to sleep enough so I was able to get in and grab the syslog from unmenu and get in a clean reboot. I lost my connection around 21:58 sometime. A sample from the syslog during my issue is here and the output of ethtool and ifconfig but from after a reboot. I have found plenty of others speaking about the issues with this NIC in the forum but I have not found any solutions posted. Seems most people are just being steered away from motherboards with this NIC chipset. What are other people doing to resolve this? I am thinking just buy a pcie x1 Intel card like this one --> http://www.newegg.com/Product/Product.aspx?Item=N82E16833106033 Or should I splurge on a server version for another 60 bucks? Or does someone have a better idea to maybe get an official resolution to this for everyone? Thanks again, -D Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes root@Tower:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 50:e5:49:3d:7d:52 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:4500 Metric:1 RX packets:6711 errors:0 dropped:0 overruns:0 frame:0 TX packets:424 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:417610 (407.8 KiB) TX bytes:33021 (32.2 KiB) Interrupt:29 Base address:0x2000 Sep 26 12:15:59 Tower emhttp: shcmd (135): /usr/sbin/hdparm -y /dev/sdh >/dev/null Sep 26 12:21:35 Tower ntpd[1479]: synchronized to 155.101.3.114, stratum 2 Sep 26 17:11:46 Tower dhcpcd[1471]: sending DHCP_REQUEST for 192.168.1.100 to 192.168.1.254 Sep 26 17:11:47 Tower dhcpcd[1471]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Sep 26 17:11:47 Tower dhcpcd[1471]: DHCP_ACK received from (192.168.1.254) Sep 26 18:00:01 Tower logger: mover started Sep 26 18:00:01 Tower logger: . Sep 26 18:00:36 Tower logger: mover finished Sep 26 18:15:36 Tower kernel: mdcmd (609): spindown 2 Sep 26 18:15:37 Tower kernel: mdcmd (610): spindown 4 Sep 26 18:15:47 Tower kernel: mdcmd (611): spindown 0 Sep 26 18:15:47 Tower kernel: mdcmd (612): spindown 1 Sep 26 18:15:48 Tower kernel: mdcmd (613): spindown 3 Sep 26 18:15:48 Tower kernel: mdcmd (614): spindown 5 Sep 26 18:15:49 Tower emhttp: shcmd (136): /usr/sbin/hdparm -y /dev/sdh >/dev/null Sep 26 21:52:28 Tower kernel: mdcmd (615): spindown 4 Sep 26 21:56:22 Tower kernel: mdcmd (616): spindown 1 Sep 26 21:56:23 Tower kernel: mdcmd (617): spindown 2 Sep 26 21:58:24 Tower kernel: ------------[ cut here ]------------ Sep 26 21:58:24 Tower kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0xff/0x17f() Sep 26 21:58:24 Tower kernel: Hardware name: Z68A-D3H-B3 Sep 26 21:58:24 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Sep 26 21:58:24 Tower kernel: Modules linked in: ntfs md_mod xor ahci r8169 mvsas libsas scst scsi_transport_sas Sep 26 21:58:24 Tower kernel: Pid: 0, comm: swapper Tainted: G W 2.6.32.9-unRAID #8 Sep 26 21:58:24 Tower kernel: Call Trace: Sep 26 21:58:24 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 Sep 26 21:58:24 Tower kernel: [<c10244e9>] warn_slowpath_fmt+0x24/0x27 Sep 26 21:58:24 Tower kernel: [<c123b505>] dev_watchdog+0xff/0x17f Sep 26 21:58:24 Tower kernel: [<c1030d4a>] ? insert_work+0x43/0x4b Sep 26 21:58:24 Tower kernel: [<c1031042>] ? __queue_work+0x26/0x2b Sep 26 21:58:24 Tower kernel: [<c1031047>] ? delayed_work_timer_fn+0x0/0x24 Sep 26 21:58:24 Tower kernel: [<c123b406>] ? dev_watchdog+0x0/0x17f Sep 26 21:58:24 Tower kernel: [<c102bb23>] run_timer_softirq+0x105/0x158 Sep 26 21:58:24 Tower kernel: [<c1028261>] __do_softirq+0x84/0xf8 Sep 26 21:58:24 Tower kernel: [<c10282fb>] do_softirq+0x26/0x2b Sep 26 21:58:24 Tower kernel: [<c1028556>] irq_exit+0x29/0x2b Sep 26 21:58:24 Tower kernel: [<c10118f0>] smp_apic_timer_interrupt+0x6f/0x7d Sep 26 21:58:24 Tower kernel: [<c10031f6>] apic_timer_interrupt+0x2a/0x30 Sep 26 21:58:24 Tower kernel: [<c10085f9>] ? mwait_idle+0x4c/0x52 Sep 26 21:58:24 Tower kernel: [<c1001a14>] cpu_idle+0x3a/0x4e Sep 26 21:58:24 Tower kernel: [<c129c662>] start_secondary+0x195/0x19a Sep 26 21:58:24 Tower kernel: ---[ end trace 592abbd31d621522 ]--- Sep 26 21:58:24 Tower kernel: r8169: eth0: link up Sep 26 22:00:48 Tower kernel: r8169: eth0: link up Sep 26 22:02:48 Tower kernel: r8169: eth0: link up Sep 26 22:05:12 Tower kernel: r8169: eth0: link up Sep 26 22:05:17 Tower unmenu[1563]: bad method - 9187416 496652240 4046717248 64821280 289290 17149711 139512008 7962840 0 25158630 727832709187416-^M Sep 26 22:08:24 Tower kernel: r8169: eth0: link up Sep 26 22:08:33 Tower unmenu[1563]: bad method - 9187416 496652240 4046717248 64821280 289290 17149711 139512008 7962840 0 25158630 727832709187416-^M Sep 26 22:11:04 Tower kernel: mdcmd (618): spindown 0 Sep 26 22:11:05 Tower kernel: mdcmd (619): spindown 3 Sep 26 22:11:05 Tower kernel: mdcmd (620): spindown 5 Sep 26 22:11:56 Tower kernel: mdcmd (621): spindown 4 Sep 26 22:12:06 Tower kernel: mdcmd (622): spindown 1 Sep 26 22:12:27 Tower kernel: mdcmd (623): spindown 2 Sep 26 22:13:18 Tower kernel: r8169: eth0: link up syslog-2011-09-26.zip Link to comment
drcorso Posted September 27, 2011 Author Share Posted September 27, 2011 Server keeps dropping now after a reboot. Grabbed some fresh data. I was trying to delete a folder when it came back up again. NIC info (from ethtool) Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes NIC driver info (from ethtool -i) driver: r8169 version: 2.3LK-NAPI firmware-version: bus-info: 0000:03:00.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 50:e5:49:3d:7d:52 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:4500 Metric:1 RX packets:13753 errors:0 dropped:0 overruns:0 frame:0 TX packets:3721 errors:0 dropped:368 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1067526 (1.0 MiB) TX bytes:1336798 (1.2 MiB) Interrupt:29 Base address:0x2000 syslog-2011-09-262.txt Link to comment
dgaschk Posted September 27, 2011 Share Posted September 27, 2011 The cheaper Intel NIC will be fine. You could try the latest beta but your controllers have given some problems with the latest beta. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.