Jump to content

Danieluwe

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by Danieluwe

  1. As requested

     

    Linux 3.9.11p-unRAID.

    root@Tower:~# ethtool eth0

    Settings for eth0:

            Supported ports: [ TP ]

            Supported link modes:  10baseT/Half 10baseT/Full

                                    100baseT/Half 100baseT/Full

                                    1000baseT/Full

            Supports auto-negotiation: Yes

            Advertised link modes:  10baseT/Half 10baseT/Full

                                    100baseT/Half 100baseT/Full

                                    1000baseT/Full

            Advertised pause frame use: Symmetric

            Advertised auto-negotiation: Yes

            Speed: 1000Mb/s

            Duplex: Full

            Port: Twisted Pair

            PHYAD: 0

            Transceiver: internal

            Auto-negotiation: on

            MDI-X: Unknown

            Supports Wake-on: pumbg

            Wake-on: g

            Current message level: 0x00000033 (51)

            Link detected: yes

     

     

    root@Tower:~# ifconfig

    eth0      Link encap:Ethernet  HWaddr 50:e5:49:55:8e:1a

              inet addr:192.168.1.50  Bcast:192.168.1.255  Mask:255.255.255.0

              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

              RX packets:10149549 errors:0 dropped:2683 overruns:0 frame:0

              TX packets:18892241 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:1000

              RX bytes:398421917 (379.9 MiB)  TX bytes:3622961068 (3.3 GiB)

              Interrupt:43 Base address:0xe000

     

    lo        Link encap:Local Loopback

              inet addr:127.0.0.1  Mask:255.0.0.0

              UP LOOPBACK RUNNING  MTU:65536  Metric:1

              RX packets:95 errors:0 dropped:0 overruns:0 frame:0

              TX packets:95 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:0

              RX bytes:7773 (7.5 KiB)  TX bytes:7773 (7.5 KiB)

    syslog.txt

  2. Hi looking for some help with transfer speeds for my unraid server,

     

    Ive been running my server for a few years now without issue apart from I have always maxed out my read speed at around 15MB/s (this is on a cat 7 wired gigabit network)

    (Write speed is around 14MB/s which I'm more than happy with)

     

    The read speed was never an issue due to streaming small files from the server,

     

    Lately i've been trying to stream blu-ray iso's from the server and am occasionaly getting stutter, I have played the files locally and found playback to be fine,

    I'm guessing that the low read speed of my server is creating an issue with streaming the large iso files,

     

    I have replaced pretty much every component in the server over the last few years including motherboard/cpu/sas card/ and replaced all lan cables with cat 7, but still hitting the 15MB/s limit on read,

     

    I'm starting to pull my hair out trying to solve this one,

     

    Any help would be greatly appreciated,

     

    Currently running Unraid 5.0.5 Pro with a 17 disk array consisting of mainly WD reds and greens

    On an intel I5 2500k cpu, 8gb Ram, Gigabyte GA-Z68AP-D3 Motherboard, Using on-board lan. Onboard SATA, LSI 9211-8i flashed to latest IT firmware and 2x SIL3132 cards.

     

    Many thanks

     

    Dan

  3. There is nothing else connected to the controller and the server hasn't even been doing anything, I've left it alone during the pre-clear,

     

    I checked the syslog, but there was nothing out of the ordinary on it, just normal ip lease requests and disc spindowns since the preclear started,

     

    I will wait for the preclear to finish before I start to worry too much, but is quite unusual never seen a drive speed vary so much during a preclear 

     

    Ps just hit post read and back up to 120MB/s very strange

  4. Just fitted a sil3132 card into my server to give a couple of extra slots,

     

    attached a new IBm 3tb coolspin and started the preclear,

     

    pre read ran through at between 120MB/s and 80MB/s pretty normal for my server,

     

    it has moved onto stage 2 copying zeros but has been running at 36MB/s consistently for the entire time I'm onto 22hrs elapsed and only 50% into writing zeros,

     

    Anyone have any idea what can cause this behaviour??

     

    Many thanks in advance

     

    Dan

  5. Quick question,

     

    Just received 2 new 2TB Drives a WD EARS and a Samsung F3, stuck them in the server and started the preclear on both, (my server has happily precleared multiple drives before)

     

    My Samsung is running fine at around 80MB/s, the EARS starts at around 100MB/s but within a few minutes drops to 5MB/s and after an hour is not even registering a speed, I have stopped and retried preclear twice on this drive,

     

    I have smartctl'd the drive and although it shows a pass it also shows 1670 ATA errors in the five hours it has been powered up,

     

    Any suggestions?

     

    Thanks in advance!

  6. Just got the following result on a preclear, not sure how to interpret the results

     

    Any help would be appreciated.

     

    preclearresult.jpg

     

    Uploaded with ImageShack.us

     

    Many thanks in advance  :)

    It indicates that three of the blocks read back DID NOT have all zeros as expected.   This is the type of situation that causes hair loss (and parity checks that occasionally/constantly return parity errors)

     

    The cause can be a bad drive (we've seen this several times with other users) or a bad disk controller (also seen several times) or a bad power supply (power supply noise caused the writes to not function properly) or temperature (disks got too hot and were unable to read their own tracks because of thermal expansion) or vibration (disks shaking made them unable to write accurately) or even the motherboard chipset (nforce4 chipsets on early motherboards were prone to this)

     

    It cold also be your RAM, if it is not configured properly in your BIOS with the correct voltage, clock speed, and timing.  (run a memtest overnight to eliminate it as a suspect)

     

    Good luck in isolating the issue.  I'd not use that drive in that server connected/configured as it current is until you can get through several more pre-clear cycles with NO errors.   

     

    Unfortunately, this class of error is frequently not detectable by any other test other than reading the contents of the disk.  You might be lucky and see actual errors in the system log, but there are odds you will not see any error in the syslog and no errors in the smart report.

     

    I know, it is not good news... but I would not trust a server where the data I wrote was not readable accurately, even if it was only four times during the post-read.    This class of error is EXACTLY why I added the post-read verify to the pre-clear script.  Prior to it being added, there was no way to learn of the bad disk/controller/??? until AFTER it was in the array and you had stored data on it and subsequently dis a parity check.  By then, it is MUCH harder to figure out which disk is causing the intermittent parity errors.

     

    Joe L.

     

    Many thanks for the quick reply, I've run a thorough memtest returning no errors and have run three WD EARS drives through a preclear with no problems, i will try another preclear before i get rid of the drive but pretty happy that the server hardware is up to scratch,

     

    Thanks again for the input it is appreciated.

×
×
  • Create New...