February 4, 201412 yr Hello, Just upgraded to version 5.0.4 5 Drives (4 sata, 1 ide) I'm getting super slow write speeds 1. Copy from drive to drive on the unraid server using Windows Explorer and Teracopy I get about 750KB/s to max 1.5MB/s 2. Copy from my desktop or laptop to unraid over 1gig network wired using Windows Explorer and Teracopy I get about 1.5MB/s max I ran smart and hdparm (see below) on all the drives and notice the 1 ide drive (oldest one) has some error on the Reallocated_Sector_Ct and it also says "FAILING_NOW" However the drive still works, and has been for the past 4 years. Questions 1. Could this be the issue? 2. Any help or suggestions would be truly helpful. 3. Let me know what other info to provide to assist with the help. Thanks Unraid Community! ====================================================== HDPARM WDC_WD5000AAJB-00UHA0_WD-WCAPW1685832 (hdb) 488386552 - 500gb Timing cached reads: 1684 MB in 2.00 seconds = 842.19 MB/sec Timing buffered disk reads: 210 MB in 3.00 seconds = 69.98 MB/sec ====================================================== === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Blue EIDE Device Model: WDC WD5000AAJB-00UHA0 Serial Number: WD-WCAPW1685832 LU WWN Device Id: 5 0014ee 2aaecc061 Firmware Version: 07.01N01 User Capacity: 500,107,862,016 bytes [500 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA/ATAPI-7 (minor revision not indicated) Local Time is: Mon Feb 3 20:42:50 2014 PST 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. 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: (12600) 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: ( 157) minutes. Conveyance self-test routine recommended polling time: ( 6) minutes. SCT capabilities: (0x203f) 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_VA LUE 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 649 3 Spin_Up_Time 0x0003 186 173 021 Pre-fail Always - 5691 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 540 5 Reallocated_Sector_Ct 0x0033 107 107 140 Pre-fail Always FAILING_NOW 741 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 9 Power_On_Hours 0x0032 044 044 000 Old_age Always - 41220 10 Spin_Retry_Count 0x0012 100 100 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 100 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 255 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 128 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 572 194 Temperature_Celsius 0x0022 105 089 000 Old_age Always - 45 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 741 197 Current_Pending_Sector 0x0012 200 191 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 191 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 021 051 Old_age Offline In_the_past 0 SMART Error Log Version: 1 ATA Error Count: 2515 (device log contains only the most recent five errors) 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 2515 occurred at disk power-on lifetime: 17900 hours (745 days + 20 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 -- -- -- -- -- -- -- 40 51 00 97 25 4f e0 Error: UNC at LBA = 0x004f2597 = 5186967 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 97 25 4f 30 08 1d+09:28:04.086 READ DMA EXT 35 00 00 97 21 4f 30 08 1d+09:28:04.053 WRITE DMA EXT 35 00 00 97 1d 4f 30 08 1d+09:28:03.993 WRITE DMA EXT 35 00 00 97 19 4f 30 08 1d+09:28:03.883 WRITE DMA EXT 35 00 00 97 15 4f 30 08 1d+09:28:03.843 WRITE DMA EXT Error 2514 occurred at disk power-on lifetime: 17900 hours (745 days + 20 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 -- -- -- -- -- -- -- 40 51 00 97 19 4f e0 Error: UNC at LBA = 0x004f1997 = 5183895 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 97 19 4f 30 08 1d+09:28:01.758 READ DMA EXT 25 00 00 97 15 4f 30 08 1d+09:28:01.734 READ DMA EXT 25 00 00 97 11 4f 30 08 1d+09:28:01.718 READ DMA EXT 25 00 00 97 0d 4f 30 08 1d+09:28:01.702 READ DMA EXT 35 00 00 97 09 4f 30 08 1d+09:28:01.666 WRITE DMA EXT Error 2513 occurred at disk power-on lifetime: 17899 hours (745 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 -- -- -- -- -- -- -- 40 51 00 7f ab 31 e0 Error: UNC at LBA = 0x0031ab7f = 3255167 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 7f ab 31 2e 08 1d+08:03:51.325 READ DMA EXT 25 00 00 7f a7 31 2e 08 1d+08:03:51.308 READ DMA EXT 25 00 00 7f 8e 31 2e 08 1d+08:03:51.298 READ DMA EXT 35 00 f8 7f a3 31 2e 08 1d+08:03:51.264 WRITE DMA EXT 35 00 00 7f 9f 31 2e 08 1d+08:03:51.233 WRITE DMA EXT Error 2512 occurred at disk power-on lifetime: 17899 hours (745 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 -- -- -- -- -- -- -- 40 51 30 47 8b 31 e0 Error: UNC 48 sectors at LBA = 0x00318b47 = 3246919 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 30 47 8b 31 2e 08 1d+08:03:48.816 READ DMA EXT 25 00 08 e7 1d 00 00 08 1d+08:03:48.786 READ DMA EXT 35 00 00 47 87 31 2e 08 1d+08:03:48.676 WRITE DMA EXT 35 00 00 47 83 31 2e 08 1d+08:03:48.646 WRITE DMA EXT 35 00 00 47 7f 31 2e 08 1d+08:03:48.606 WRITE DMA EXT Error 2511 occurred at disk power-on lifetime: 17899 hours (745 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 -- -- -- -- -- -- -- 40 51 00 47 87 31 e0 Error: UNC at LBA = 0x00318747 = 3245895 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 47 87 31 2e 08 1d+08:03:46.323 READ DMA EXT 25 00 00 47 83 31 2e 08 1d+08:03:46.307 READ DMA EXT 25 00 00 47 7f 31 2e 08 1d+08:03:46.291 READ DMA EXT 25 00 00 47 7b 31 2e 08 1d+08:03:46.253 READ DMA EXT 25 00 00 47 77 31 2e 08 1d+08:03:46.237 READ DMA EXT SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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.
February 4, 201412 yr Author Quick update Just moved file with MC Commander using Putty and it's transfer way faster. So now the questions is how do I get it to move faster with windows? Thanks!
February 4, 201412 yr Author Another updated 1. Transfer are running at about 22MB/s using MC Commander is this normal? or should I be getting something faster. 2. Viewing of images or videos is still extremely slow at 500KB/s to 1.5MB/s Any suggestions? Thanks!
February 4, 201412 yr Can you replicate the problem with different systems? Try to isolate and find a pattern with transferring files with different systems. That should help determine if the problem is with the unRAID server or your Windows workstation. Could be one of the systems simply negotiated a bad connection and needs to be reset/rebooted or something else more complex.
February 4, 201412 yr What motherboard are you using? How Much Memory? Post your syslog If you have a drive that is FAILING NOW... that is a FAIL. Seriously, SMART says SMART overall-health self-assessment test result: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA.See vendor-specific Attribute list for failed Attributes. Time to reconsider that drive's usefulness. Maybe it's time to retire it. You could try and do a SMART LONG test on the drive. You could try and move the data off the drive and do a preclear on it, which would either reallocate bad sectors or refresh them. Is it the reason your array is slow. hard to say. Are you copying to or from this FAILING NOW drive?
February 5, 201412 yr Author Ok here the answers 1. What motherboard are you using? I'm using a MSI motherboard, it's been working fine with version 4.3-4.7 for the past 4 years. 2. How Much Memory? 2gb dual channel 3. CPU - AMD 4. Syslog attached 5. I have tested with 4 different windows machine and a mac running osx mavericks. All trying to View images and video as well as copy from Windows and OSX it still crawls at about 1.5MB/s to 500KB/s 6. Yes I am copying and using the FAILING drive still Moving off all data from this failing drive and going to try a SMART LONG test then preclear it see what happens. Any other suggestions? BTW i'm on a DLINK DIR655 router and hooked up gigabit via lan. Cat 6 cables. Thanks again Unraiders! syslog.txt
February 5, 201412 yr 6. Yes I am copying and using the FAILING drive still I'm betting that it would be faster to remove the drive and run at risk. I'm not recommending that, just stating an opinion. What I'm recommending is replace that drive ASAP. If you have another drive fail right now, you will probably lose data. Since unraid can only deal with 1 drive failure at a time without losing data, it is a really bad idea to continue to run with a questionable drive. Drives can fail without warning, at least this one is giving you time to deal with it.
February 5, 201412 yr Author I'm moving all data off the failing drive now. Non of the others drives report failing from the reports only this really old one. Going to run some test see if I can't get it working going to just replace the drive. Now to figure out why reading is copying is so darn slow. Thanks.
February 5, 201412 yr I'm moving all data off the failing drive now. Now to figure out why reading is copying is so darn slow. It's slow BECAUSE the drive is failing.
February 6, 201412 yr It is very likely that it's not possible to read the failing disk. Replacing and rebuilding the contents is the safest plan. As mentioned, things will go much faster if you stop the array, un-assign the failing drive, and start the array with the drive unassigned. The contents of the missing drive will still be available and can be copied to a different drive. Then reset the array config and rebuild parity without the missing drive. This only makes sense if you do not plan on replacing the dead drive. The Drive is done. I've never seen a drive go from FAILED to PASSED. I'm not sure it's possible.
Archived
This topic is now archived and is closed to further replies.