Random disk/raid copy slowness

deranjer · 8. Januar 2015

Hello.

I just installed OMV and did a SMB transfer that resulted in speeds from 7MB/s to 9MB/s, which is much slower than acceptable. I unfortunately started out by troubleshooting network connections, replacing switches, etc. However, when that didn't change anything, I started examining the raid setup itself.

Here are my basic specs:
I have RAID5 with EXT4 with 4x2TB Red NAS drives and an SSD for the OS. I came over from FreeNAS, where I was getting 40MB/s (at least), but switched because I was using ZFS without ECC RAM and my processor was a little underpowered (AMD c-60 APU) and was maxing out when transferring via SMB. I have 16GB of RAM in the machine.

After searching the forums I ran a few basic speed tests on the RAID itself, with odd results:

Code

root@OMV-Server:/media/4f85211f-0972-4eb4-8ce3-ac7664a3cd4f# dd if=/dev/zero of=tempfile bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 3.51127 s, 292 MB/s
root@OMV-Server:/media/4f85211f-0972-4eb4-8ce3-ac7664a3cd4f# dd if=/dev/zero of=tempfile bs=1MB count=2048
2048+0 records in
2048+0 records out
2048000000 bytes (2.0 GB) copied, 377.226 s, 5.4 MB/s
root@OMV-Server:/media/4f85211f-0972-4eb4-8ce3-ac7664a3cd4f# dd if=/dev/zero of=tempfile bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 185.531 s, 5.5 MB/s

Alles anzeigen

These tests were all ran directly after eachother, nothing changed in the configuration. It wasn't a fresh reboot of the server either. Going from ~290MB/S to ~5.5MB/S is a LARGE drop...

EDIT:
Just ran the hdparm command on the RAID and found this which is almost exactly the transfer speed I was getting over the network:

Code

hdparm -t /dev/md0


/dev/md0:
 Timing buffered disk reads:  24 MB in  3.18 seconds =   7.54 MB/sec

I delved a little further, finding a post by datadigger on tests to run:

Code

lspci -v
00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40) (prog-if 01 [AHCI 1.0])
        Subsystem: ASUSTeK Computer Inc. Device 8496
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 19
        I/O ports at f190 [size=8]
        I/O ports at f180 [size=4]
        I/O ports at f170 [size=8]
        I/O ports at f160 [size=4]
        I/O ports at f150 [size=16]
        Memory at feb4b000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [70] SATA HBA v1.0
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: ahci


root@OMV-Server:~# hdparm -I /dev/sda | grep -i speed
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Gen3 signaling speed (6.0Gb/s)
root@OMV-Server:~# hdparm -I /dev/sdb | grep -i speed
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Gen3 signaling speed (6.0Gb/s)
root@OMV-Server:~# hdparm -I /dev/sdc | grep -i speed
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Gen3 signaling speed (6.0Gb/s)
root@OMV-Server:~# hdparm -I /dev/sdd | grep -i speed
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Gen3 signaling speed (6.0Gb/s)
root@OMV-Server:~# hdparm -I /dev/sde | grep -i speed
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Gen3 signaling speed (6.0Gb/s)


root@OMV-Server:~# egrep 'ata[0-9]\.|SATA link up' /var/log/dmesg
[    3.124920] ata5.00: ATA-9: WDC WD20EFRX-68AX9N0, 80.00A80, max UDMA/133
[    3.124929] ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    3.125166] ata5.01: ATA-9: WDC WD20EFRX-68AX9N0, 80.00A80, max UDMA/133
[    3.125175] ata5.01: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    3.125190] ata5.00: limited to UDMA/33 due to 40-wire cable
[    3.125196] ata5.01: limited to UDMA/33 due to 40-wire cable
[    3.132901] ata5.00: configured for UDMA/33
[    3.140849] ata5.01: configured for UDMA/33
[    3.416269] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    3.416324] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    3.416365] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    3.417163] ata4.00: ATA-9: WDC WD20EFRX-68AX9N0, 80.00A80, max UDMA/133
[    3.417178] ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    3.417330] ata1.00: ATA-9: SanDisk SDSSDHII240G, X31200RL, max UDMA/133
[    3.417341] ata1.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[    3.417981] ata3.00: ATA-9: WDC WD20EFRX-68AX9N0, 80.00A80, max UDMA/133
[    3.418008] ata3.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    3.418186] ata4.00: configured for UDMA/133
[    3.418388] ata1.00: configured for UDMA/133
[    3.418863] ata3.00: configured for UDMA/133

Alles anzeigen

Now, it seemed odd that two of my drives were limited to UDMA/33, but datadigger had the same output (I think he might have the same board) and he said the speed didn't differ on those disks from the others, so "came to the conclusion that the board maker has used a port multiplier with different capabilities as the other four SATA ports and they seem to run on PATA-mode (A 40-wire cable is an old style flat cable)."

Also "AA" isn't enabled on those two drives, which may be a problem?

Next, he ran speed tests on individual disks, where I once again had another interesting result.

Code

[/coroot@OMV-Server:~# dd conv=fdatasync if=/dev/sdc of=/home/test.imf bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 10.3246 s, 99.2 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sdb of=/home/test.imf bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 10.4696 s, 97.8 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sdd of=/home/test.imf bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 510.71 s, 2.0 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sde of=/home/test.imf bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 10.6054 s, 96.6 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sdd of=/home/test.imf bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 8.03321 s, 127 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sdc of=/home/test.imf bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 8.1168 s, 126 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sde of=/home/test.imf bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 8.05182 s, 127 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sdd of=/home/test.imf bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 8.01716 s, 128 MB/s

Alles anzeigen

Notice that ONE TIME sdd had a copy speed of 2.0MB/S. However, all the times after that it worked fine! Does anyone know what might be going on here??

subzero79 · 8. Januar 2015

Something is going on with the array, is it clean?

What's the status of cat /proc/mdstat

Who long since you format the array? ext4 can take some time to initialize having the journal process in constant writing for a day depending on the size.
You can checj with iostat if any process is writing to the array

deranjer · 8. Januar 2015

Code

root@OMV-Server:/media/4f85211f-0972-4eb4-8ce3-ac7664a3cd4f# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sde[3] sdd[2] sdc[1] sdb[0]
      5860148736 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]


unused devices: <none>

I took a quick look at the IOSTAT manpage, as I am not familiar with the tool, but not sure if that output is high or normal?

Code

iostat
Linux 3.2.0-4-amd64 (OMV-Server)        01/08/2015      _x86_64_        (2 CPU)


avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           2.16    0.00   19.04    3.39    0.00   75.41


Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sdc             665.87     13610.18      2012.14 1961745412  290025818
sdb             812.55     13625.43      2013.41 1963943625  290209286
sdd             144.55     13625.98      2011.18 1964022388  289887298
sda               1.61         2.92        80.41     420232   11589824
sde             146.29     13617.32      2008.05 1962774604  289436958
md0              18.26        55.93      1622.97    8062053  233932100

Alles anzeigen

The ext4 fs was created about 24 hours ago if that helps....

subzero79 · 8. Januar 2015

Sorry besides iostat there is also iotop for process/software read/write.

iotop -a will run collecting accumulated read/write

Also the read is very very slow for md0. Did you create this array with OMV?

deranjer · 8. Januar 2015

Code

Total DISK READ:       0.00 B/s | Total DISK WRITE:       0.00 B/s
  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
  260 be/3 root          0.00 B    204.00 K  0.00 %  0.04 % [jbd2/sda1-8]
21626 be/4 root          0.00 B      8.00 K  0.00 %  0.00 % rsyslogd -c5
 2217 be/4 root          0.00 B     16.00 K  0.00 %  0.00 % monit -c /etc/monit/monitrc
 1832 be/4 root          0.00 B     84.00 K  0.00 %  0.00 % rrdcached -l unix:/var/run/rrdcached.sock -j /var/lib/rrdcached/journal~-F -b /var/lib/rrdcached/db/ -B -w 900 -f 3600 -p /var/run/rrdcached.pid
    1 be/4 root          0.00 B      0.00 B  0.00 %  0.00 % init [2]
    2 be/4 root          0.00 B      0.00 B  0.00 %  0.00 % [kthreadd]

Not much showing in

Code

iotop -a

. I see a max of maybe 30kb/s at times (but that is on jbd2/sda), which should be the OS disk, not the RAID.

Yes, this is what I did.
1) Backed up my FreeNAS ZFS archive to external USB drives
2) Powered off PC, unclipped all drives, installed SSD drive
3) Installed OMV to the SSD drive, shut down PC, plugged in all WD Red drives.
4) Configured OMV with date/time, etc
5) Used OMV web-ui to wipe all 4 physical disks
6) Created RAID5 with my 4 2TB WD Red drives using OMV web-ui
7) Created EXT4 FS on the RAID
Copied ~250GB to the RAID (from USB) for testing
9) Started testing RAID and ran into issues.

subzero79 · 8. Januar 2015

Looks normal...unless the stripe cache udev is not loading

cat /sys/block/md0/md/stripe_cache_size What does it gives you?

deranjer · 8. Januar 2015

Code

root@OMV-Server:/media/4f85211f-0972-4eb4-8ce3-ac7664a3cd4f# cat /sys/block/md0/md/stripe_cache_size
8192

subzero79 · 8. Januar 2015

Thats the default tuned value.

Could be something in particular with sdd (faulty cable or drive)? faulty cable might show CRC errors in smart section.

Also make sure all drives are AHCI in BIOS

Other than that I am out of ideas, you could try upgrading to backport kernel 3.16 so check if it makes a difference.

deranjer · 8. Januar 2015

Well I replaced almost all of the sata connections and changed their ports around on the mobo and found that AHCI was not set in the BIOS, so changed that. Then checked all the smart settings and found some CRC errors on one of my drives... seems rather excessive, is this my issue? I'm re-running a full test on the drive now. Before I ran the test i did retry the test and the results were MUCH better, but network tranfers were only aroun 11-12MB/S... which is odd, if the on server transfers appear to be better, but not the network transfers.

Code

hdparm -t /dev/md0


/dev/md0:
 Timing buffered disk reads: 788 MB in  3.00 seconds = 262.40 MB/sec
root@OMV-Server:~# hdparm -t /dev/md0


/dev/md0:
 Timing buffered disk reads: 762 MB in  3.01 seconds = 253.49 MB/sec
root@OMV-Server:~# dd conv=fdatasync if=/dev/sda of=/home/test.img bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 12.8891 s, 79.4 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sdb of=/home/test.img bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 8.90729 s, 115 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sdc of=/home/test.img bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 9.55264 s, 107 MB/s
root@OMV-Server:~# dd conv=fdatasync if=/dev/sde of=/home/test.img bs=1MB count=1024
1024+0 records in
1024+0 records out
1024000000 bytes (1.0 GB) copied, 8.78346 s, 117 MB/s
root@OMV-Server:~# hdparm -t /dev/md0


/dev/md0:
 Timing buffered disk reads: 970 MB in  3.00 seconds = 322.93 MB/sec
root@OMV-Server:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sde[0] sdb[3] sda[2] sdc[1]
      5860148736 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

Alles anzeigen

And here is the smartctl report for /dev/sda:

Code

smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net


=== START OF INFORMATION SECTION ===
Device Model:     WDC WD20EFRX-68AX9N0
Serial Number:    WD-WMC301314573
LU WWN Device Id: 5 0014ee 0ae3453fd
Firmware Version: 80.00A80
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   9
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Jan  8 16:57:29 2015 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED


General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever 
                    been run.
Total time to complete Offline 
data collection:         (27420) seconds.
Offline data collection
capabilities:              (0x7b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine 
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      ( 255) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x70bd)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.


SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   179   175   021    Pre-fail  Always       -       4050
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       38
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   080   080   000    Old_age   Always       -       14916
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       38
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       30
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       7
194 Temperature_Celsius     0x0022   120   112   000    Old_age   Always       -       27
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   199   000    Old_age   Always       -       7888
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0


SMART Error Log Version: 1


ATA Error Count: 1
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.


Error 1 occurred at disk power-on lifetime: 14875 hours (619 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 01 00 00 00 00  Error: ABRT


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d5 01 e1 4f c2 00 00      01:13:55.408  SMART READ LOG
  b0 d6 01 e0 4f c2 00 00      01:13:55.406  SMART WRITE LOG
  b0 d6 01 e0 4f c2 00 00      01:13:55.405  SMART WRITE LOG
  b0 d5 01 e0 4f c2 00 00      01:13:55.405  SMART READ LOG
  b0 d5 01 e0 4f c2 00 00      01:13:55.404  SMART READ LOG


SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     13498         -
# 2  Short offline       Completed without error       00%     13486         -
# 3  Short offline       Completed without error       00%     13233         -
# 4  Short offline       Completed without error       00%     13221         -
# 5  Short offline       Completed without error       00%     12993         -
# 6  Short offline       Completed without error       00%     12981         -
# 7  Short offline       Completed without error       00%     12753         -
# 8  Short offline       Completed without error       00%     12741         -
# 9  Short offline       Completed without error       00%     12514         -
#10  Short offline       Completed without error       00%     12502         -
#11  Short offline       Completed without error       00%     12274         -
#12  Short offline       Completed without error       00%     12262         -
#13  Short offline       Completed without error       00%     12034         -
#14  Short offline       Completed without error       00%     12022         -


#15  Extended offline    Interrupted (host reset)      10%     11912         -
#16  Short offline       Completed without error       00%     11770         -
#17  Short offline       Completed without error       00%     11758         -
#18  Short offline       Completed without error       00%     11531         -
#19  Short offline       Completed without error       00%     11519         -
#20  Short offline       Completed without error       00%     11291         -
#21  Short offline       Completed without error       00%     11279         -


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Alles anzeigen

subzero79 · 8. Januar 2015

Ok. Speed looks good now for md0
crc issues in what drive?
The network speed seems to be capped at fast ethernet. What does ethtool eth0 indicates?

deranjer · 8. Januar 2015

CRC issues in one of my 2TB WD RAID drives, not my SSD drive

Code

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE




199 UDMA_CRC_Error_Count    0x0032   200   199   000    Old_age   Always       -       7888

Code

root@OMV-Server:/media/4f85211f-0972-4eb4-8ce3-ac7664a3cd4f# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Half 1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner 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)
                               drv probe ifdown ifup
        Link detected: yes

Alles anzeigen

subzero79 · 9. Januar 2015

Seems alright there, but the driver didn't appear ethtool -i eth0

For testing the network I would try maybe a different cat5e cable, also a direct connect a gigabit laptop to OMV with no switch in between.
Are you sure the client receiving the data is at gigabit speed?

Also for the CRC errors try and get a new Sata cable.

deranjer · 9. Januar 2015

Hey..... so thanks so much for your help! I did look at my client and was shocked to realize I wasn't running gigabit. I double checked the switch the client was on and it was a gigabit switch, so I replaced the LAN cable and it went to gigabit immediately, must have been a bad cable. Now I'm getting 60-70MB/s down (haven't tried up yet) and everything appears to be working fine.

I'll still check on that drive, since I already replaced 4 of the 5 cables in the case, there is a slim chance that the one drive I didn't replace it on is the one that is having issues. I'll have to confirm the serial number to verify the exact drive and check the cable... if a cable replacement and port move on the MB doesn't resolve it I assume it is time to order another drive?

subzero79 · 9. Januar 2015

It could be something of moment maybe, like loose connector or bad cable.
Also you can try move the drive outside of the case to check if the error stops. Just check that the error value doesn't keep increasing.
Crc error is data communication fail in between the controller and disk.

Random disk/raid copy slowness

Jetzt mitmachen!

Tags