April 3, 201115 yr Hi all, Just installed a bigger 2TB parity drive. Ran through all the clearing formatting and parity checks without issues but when i come to move data over onto the server it runs briefly then hangs. It becomes very unresponive after that. Can anyone help? Setup is: Asus P5QL Pro 4gig Ram E8400 Generic GPU Syslog Apr 3 14:35:41 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 3 14:35:41 Tower kernel: ata4.00: BMDMA stat 0x64 Apr 3 14:35:41 Tower kernel: ata4.00: failed command: READ DMA EXT Apr 3 14:35:41 Tower kernel: ata4.00: cmd 25/00:00:8f:f0:32/00:04:00:00:00/e0 tag 0 dma 524288 in Apr 3 14:35:41 Tower kernel: res 51/40:c7:c8:f3:32/40:00:00:00:00/e0 Emask 0x9 (media error) Apr 3 14:35:41 Tower kernel: ata4.00: status: { DRDY ERR } Apr 3 14:35:41 Tower kernel: ata4.00: error: { UNC } Apr 3 14:35:41 Tower kernel: ata4.00: configured for UDMA/133 Apr 3 14:35:41 Tower kernel: ata4.01: configured for UDMA/133 Apr 3 14:35:41 Tower kernel: ata4: EH complete Apr 3 14:35:46 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 3 14:35:46 Tower kernel: ata4.00: BMDMA stat 0x64 Apr 3 14:35:46 Tower kernel: ata4.00: failed command: READ DMA EXT Apr 3 14:35:46 Tower kernel: ata4.00: cmd 25/00:00:8f:f0:32/00:04:00:00:00/e0 tag 0 dma 524288 in Apr 3 14:35:46 Tower kernel: res 51/40:c7:c8:f3:32/40:00:00:00:00/e0 Emask 0x9 (media error) Apr 3 14:35:46 Tower kernel: ata4.00: status: { DRDY ERR } Apr 3 14:35:46 Tower kernel: ata4.00: error: { UNC } Apr 3 14:35:46 Tower kernel: ata4.00: configured for UDMA/133 Apr 3 14:35:46 Tower kernel: ata4.01: configured for UDMA/133 Apr 3 14:35:46 Tower kernel: ata4: EH complete Apr 3 14:35:51 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 3 14:35:51 Tower kernel: ata4.00: BMDMA stat 0x64 Apr 3 14:35:51 Tower kernel: ata4.00: failed command: READ DMA EXT Apr 3 14:35:51 Tower kernel: ata4.00: cmd 25/00:00:8f:f0:32/00:04:00:00:00/e0 tag 0 dma 524288 in Apr 3 14:35:51 Tower kernel: res 51/40:c7:c8:f3:32/40:00:00:00:00/e0 Emask 0x9 (media error) Apr 3 14:35:51 Tower kernel: ata4.00: status: { DRDY ERR } Apr 3 14:35:51 Tower kernel: ata4.00: error: { UNC } Apr 3 14:35:51 Tower kernel: ata4.00: configured for UDMA/133 Apr 3 14:35:51 Tower kernel: ata4.01: configured for UDMA/133 Apr 3 14:35:51 Tower kernel: ata4: EH complete Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt/user/Movies (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt/user (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt/user/Movies/desktop.ini (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt/user/Movies/desktop.ini (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt/user/Movies (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt/user (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt/user/Movies/ (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt/user/Movies/desktop.ini (/): not exported Apr 3 14:35:55 Tower mountd[1730]: refused mount request from 192.168.0.8 for /mnt/user (/): not exported Apr 3 14:35:56 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 3 14:35:56 Tower kernel: ata4.00: BMDMA stat 0x64 Apr 3 14:35:56 Tower kernel: ata4.00: failed command: READ DMA EXT Apr 3 14:35:56 Tower kernel: ata4.00: cmd 25/00:00:8f:f0:32/00:04:00:00:00/e0 tag 0 dma 524288 in Apr 3 14:35:56 Tower kernel: res 51/40:c7:c8:f3:32/40:00:00:00:00/e0 Emask 0x9 (media error) Apr 3 14:35:56 Tower kernel: ata4.00: status: { DRDY ERR } Apr 3 14:35:56 Tower kernel: ata4.00: error: { UNC } Apr 3 14:35:56 Tower kernel: ata4.00: configured for UDMA/133 Apr 3 14:35:56 Tower kernel: ata4.01: configured for UDMA/133 Apr 3 14:35:56 Tower kernel: ata4: EH complete Apr 3 14:36:01 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 3 14:36:01 Tower kernel: ata4.00: BMDMA stat 0x64 Apr 3 14:36:01 Tower kernel: ata4.00: failed command: READ DMA EXT Apr 3 14:36:01 Tower kernel: ata4.00: cmd 25/00:00:8f:f0:32/00:04:00:00:00/e0 tag 0 dma 524288 in Apr 3 14:36:01 Tower kernel: res 51/40:c7:c8:f3:32/40:00:00:00:00/e0 Emask 0x9 (media error) Apr 3 14:36:01 Tower kernel: ata4.00: status: { DRDY ERR } Apr 3 14:36:01 Tower kernel: ata4.00: error: { UNC } Apr 3 14:36:01 Tower kernel: ata4.00: configured for UDMA/133 Apr 3 14:36:01 Tower kernel: ata4.01: configured for UDMA/133 Apr 3 14:36:01 Tower kernel: ata4: EH complete Apr 3 14:36:06 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 3 14:36:06 Tower kernel: ata4.00: BMDMA stat 0x64 Apr 3 14:36:06 Tower kernel: ata4.00: failed command: READ DMA EXT Apr 3 14:36:06 Tower kernel: ata4.00: cmd 25/00:00:8f:f0:32/00:04:00:00:00/e0 tag 0 dma 524288 in Apr 3 14:36:06 Tower kernel: res 51/40:c7:c8:f3:32/40:00:00:00:00/e0 Emask 0x9 (media error) Apr 3 14:36:06 Tower kernel: ata4.00: status: { DRDY ERR } Apr 3 14:36:06 Tower kernel: ata4.00: error: { UNC } Apr 3 14:36:06 Tower kernel: ata4.00: configured for UDMA/133 Apr 3 14:36:07 Tower kernel: ata4.01: configured for UDMA/133 Apr 3 14:36:07 Tower kernel: sd 4:0:0:0: [sdc] Unhandled sense code Apr 3 14:36:07 Tower kernel: sd 4:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 Apr 3 14:36:07 Tower kernel: sd 4:0:0:0: [sdc] Sense Key : 0x3 [current] [descriptor] Apr 3 14:36:07 Tower kernel: Descriptor sense data with sense descriptors (in hex): Apr 3 14:36:07 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Apr 3 14:36:07 Tower kernel: 00 32 f3 c8 Apr 3 14:36:07 Tower kernel: sd 4:0:0:0: [sdc] ASC=0x11 ASCQ=0x4 Apr 3 14:36:07 Tower kernel: sd 4:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 00 32 f0 8f 00 04 00 00 Apr 3 14:36:07 Tower kernel: end_request: I/O error, dev sdc, sector 3339208 Apr 3 14:36:07 Tower kernel: ata4: EH complete Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339144/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339152/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339160/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339168/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339176/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339184/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339192/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339200/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339208/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339216/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339224/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339232/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339240/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339248/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339256/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339264/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339272/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339280/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339288/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339296/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339304/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339312/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339320/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339328/0, count: 1 Apr 3 14:36:07 Tower kernel: md: disk0 read error Apr 3 14:36:07 Tower kernel: handle_stripe read error: 3339336/0, count: 1 Apr 3 14:36:12 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 3 14:36:12 Tower kernel: ata4.00: BMDMA stat 0x64 Apr 3 14:36:12 Tower kernel: ata4.00: failed command: READ DMA EXT Apr 3 14:36:12 Tower kernel: ata4.00: cmd 25/00:00:8f:fc:32/00:04:00:00:00/e0 tag 0 dma 524288 in Apr 3 14:36:12 Tower kernel: res 51/40:5f:30:ff:32/40:01:00:00:00/e0 Emask 0x9 (media error) Apr 3 14:36:12 Tower kernel: ata4.00: status: { DRDY ERR } Apr 3 14:36:12 Tower kernel: ata4.00: error: { UNC } Apr 3 14:36:12 Tower kernel: ata4.00: configured for UDMA/133 Apr 3 14:36:12 Tower kernel: ata4.01: configured for UDMA/133 Apr 3 14:36:12 Tower kernel: ata4: EH complete Apr 3 14:36:17 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 3 14:36:17 Tower kernel: ata4.00: BMDMA stat 0x64 Apr 3 14:36:17 Tower kernel: ata4.00: failed command: READ DMA EXT Apr 3 14:36:17 Tower kernel: ata4.00: cmd 25/00:00:8f:fc:32/00:04:00:00:00/e0 tag 0 dma 524288 in Apr 3 14:36:17 Tower kernel: res 51/40:5f:30:ff:32/40:01:00:00:00/e0 Emask 0x9 (media error) Apr 3 14:36:17 Tower kernel: ata4.00: status: { DRDY ERR } Apr 3 14:36:17 Tower kernel: ata4.00: error: { UNC } Apr 3 14:36:17 Tower kernel: ata4.00: configured for UDMA/133 Apr 3 14:36:17 Tower kernel: ata4.01: configured for UDMA/133 Apr 3 14:36:17 Tower kernel: ata4: EH complete Apr 3 14:36:22 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 3 14:36:22 Tower kernel: ata4.00: BMDMA stat 0x64 Apr 3 14:36:22 Tower kernel: ata4.00: failed command: READ DMA EXT Apr 3 14:36:22 Tower kernel: ata4.00: cmd 25/00:00:8f:fc:32/00:04:00:00:00/e0 tag 0 dma 524288 in Apr 3 14:36:22 Tower kernel: res 51/40:5f:30:ff:32/40:01:00:00:00/e0 Emask 0x9 (media error) Apr 3 14:36:22 Tower kernel: ata4.00: status: { DRDY ERR } Apr 3 14:36:22 Tower kernel: ata4.00: error: { UNC } Apr 3 14:36:22 Tower kernel: ata4.00: configured for UDMA/133 Apr 3 14:36:22 Tower kernel: ata4.01: configured for UDMA/133 Apr 3 14:36:22 Tower kernel: ata4: EH complete
April 3, 201115 yr Author Smart log below for the parity drive. I'm running version 4.5.6 of Unraid. smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD204UI Serial Number: S2H7JD1B216345 Firmware Version: 1AQ10001 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x28 Local Time is: Sun Apr 3 14:57:43 2011 Local time zone must be set--see zic m ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: (20580) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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. SCT capabilities: (0x003f) SCT Status 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 095 095 051 Pre-fail Always - 483 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 068 065 025 Pre-fail Always - 9964 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 8 5 Reallocated_Sector_Ct 0x0033 085 085 010 Pre-fail Always - 1872 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 15 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 6 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5 181 Unknown_Attribute 0x0022 100 100 000 Old_age Always - 5171109 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 3 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 061 056 000 Old_age Always - 39 (Lifetime Min/Max 16/44) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 085 085 000 Old_age Always - 1872 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 3 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 1256 223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 6 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 14 SMART Error Log Version: 1 ATA Error Count: 6 (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 6 occurred at disk power-on lifetime: 14 hours (0 days + 14 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 08 3f 00 50 e4 Error: UNC 8 sectors at LBA = 0x0450003f = 72351807 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 3f 00 50 e4 08 00:00:19.594 READ DMA 27 00 00 00 00 00 e0 08 00:00:19.594 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:19.594 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:19.594 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:19.594 READ NATIVE MAX ADDRESS EXT Error 5 occurred at disk power-on lifetime: 14 hours (0 days + 14 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 08 3f 00 50 e4 Error: UNC 8 sectors at LBA = 0x0450003f = 72351807 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 3f 00 50 e4 08 00:00:19.589 READ DMA 27 00 00 00 00 00 e0 08 00:00:19.589 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:19.589 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:19.589 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:19.589 READ NATIVE MAX ADDRESS EXT Error 4 occurred at disk power-on lifetime: 14 hours (0 days + 14 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 08 3f 00 50 e4 Error: UNC 8 sectors at LBA = 0x0450003f = 72351807 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 3f 00 50 e4 08 00:00:19.584 READ DMA 27 00 00 00 00 00 e0 08 00:00:19.584 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:19.584 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:19.584 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:19.584 READ NATIVE MAX ADDRESS EXT Error 3 occurred at disk power-on lifetime: 14 hours (0 days + 14 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 08 3f 00 50 e4 Error: UNC 8 sectors at LBA = 0x0450003f = 72351807 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 3f 00 50 e4 08 00:00:19.579 READ DMA 27 00 00 00 00 00 e0 08 00:00:19.579 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:19.578 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:19.578 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:19.578 READ NATIVE MAX ADDRESS EXT Error 2 occurred at disk power-on lifetime: 14 hours (0 days + 14 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 08 3f 00 50 e4 Error: UNC 8 sectors at LBA = 0x0450003f = 72351807 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 3f 00 50 e4 08 00:00:19.573 READ DMA 27 00 00 00 00 00 e0 08 00:00:19.573 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:19.573 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:19.573 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:19.571 READ NATIVE MAX ADDRESS 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 (0) should be 1 SMART Selective self-test log data structure revision number 0 Warning: ATA Specification requires selective self-test log data structure revision number = 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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.
April 3, 201115 yr I have the same drive, did you upgrade the firmware? Did you make sure cable are snug and secure?
April 3, 201115 yr Author Cables are snug and secure. The firmware has not been upgraded though. Should the drive not run without having to do this? Regards Mike
April 3, 201115 yr Your drive should work without the update, but you will be vunerable to the silent data corruption bug. I would definitely recommend doing the update. And according to your serial number you are affected. Here is the site http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=386 5 Reallocated_Sector_Ct 0x0033 085 085 010 Pre-fail Always - 1872 Your drive may be failing.
April 3, 201115 yr Author Firmware is now updated but still getting the errors Thanks for the suggestion. Regards
April 3, 201115 yr Firmware is now updated but still getting the errors Thanks for the suggestion. Regards It has nothing to do with the firmware, the drive is failing... It is well on its way to failing the SMART tests. It has already re-allocated over 1800 sectors and there are 3 more pending. 5 Reallocated_Sector_Ct 0x0033 085 085 010 Pre-fail Always - 1872 RMA the drive. Question? Did you let unRAID clear the drives?, or did you pre-clear the parity drive with the preclear_disk.sh script? Joe L.
April 3, 201115 yr Author Bugger, this drive is brand new! Could there be any other reason for it doing what its doing? Regards
April 3, 201115 yr This is a smart report of one of my Samsung drives === START OF INFORMATION SECTION === Device Model: SAMSUNG HD204UI Serial Number: S2H7J1BZC20131 Firmware Version: 1AQ10001 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x28 Local Time is: Sun Apr 3 12:00:53 2011 EDT ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: (20700) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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. SCT capabilities: (0x003f) SCT Status 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 100 100 051 Pre-fail Always - 1 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 068 067 025 Pre-fail Always - 9998 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 146 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 380 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 22 181 Unknown_Attribute 0x0022 252 252 000 Old_age Always - 0 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 8935 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 063 061 000 Old_age Always - 37 (Lifetime Min/Max 7/39) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 132 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 148 SMART Error Log Version: 1 No Errors Logged 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 (0) should be 1 SMART Selective self-test log data structure revision number 0 Warning: ATA Specification requires selective self-test log data structure revision number = 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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.
April 3, 201115 yr Bugger, this drive is brand new! Could there be any other reason for it doing what its doing? Regards unfortunately, no. I've got a Seagate here that did had the exact same issue in its first few hours of life. It is why most of us pre-clear the disks, before we put data on them. It alerts you to the early failures before the drive is assigned to the array. (and it saves on the down-time when adding a new drive to an existing array too)
April 3, 201115 yr Author Well thanks for the help folks. Will have a look at this pre-clearing. Many Thanks Mike
Archived
This topic is now archived and is closed to further replies.