September 16, 201015 yr I'm running unraid beta 5.2 with 3 drivers; I've just been testing and "playing" with the whole unraid thing adn sofar I like it alot This morning when I checked to see how it was doing I saw I had 14 error on a drive that's completely empty... When I checked the syslog I saw the following error messages--does this mean my drive is bad? Or just a sync error I shouldn't worry about? ep 16 05:31:58 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:31:58 Tower kernel: ata1.00: port_status 0x20200000 Sep 16 05:31:58 Tower kernel: ata1.00: failed command: READ DMA EXT Sep 16 05:31:58 Tower kernel: ata1.00: cmd 25/00:f8:f7:4a:38/00:03:3a:00:00/e0 tag 0 dma 520192 in Sep 16 05:31:58 Tower kernel: res 51/40:00:81:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:31:58 Tower kernel: ata1.00: status: { DRDY ERR } Sep 16 05:31:58 Tower kernel: ata1.00: error: { UNC } Sep 16 05:31:58 Tower kernel: ata1.00: configured for UDMA/133 Sep 16 05:31:58 Tower kernel: ata1: EH complete Sep 16 05:32:00 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:32:00 Tower kernel: ata5.00: BMDMA stat 0x24 Sep 16 05:32:00 Tower kernel: ata5.00: failed command: READ DMA EXT Sep 16 05:32:00 Tower kernel: ata5.00: cmd 25/00:00:f7:4a:38/00:04:3a:00:00/e0 tag 0 dma 524288 in Sep 16 05:32:00 Tower kernel: res 51/40:00:75:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:32:00 Tower kernel: ata5.00: status: { DRDY ERR } Sep 16 05:32:00 Tower kernel: ata5.00: error: { UNC } Sep 16 05:32:00 Tower kernel: ata5.00: configured for UDMA/133 Sep 16 05:32:00 Tower kernel: ata5: EH complete Sep 16 05:32:01 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:32:01 Tower kernel: ata1.00: port_status 0x20200000 Sep 16 05:32:01 Tower kernel: ata1.00: failed command: READ DMA EXT Sep 16 05:32:01 Tower kernel: ata1.00: cmd 25/00:f8:f7:4a:38/00:03:3a:00:00/e0 tag 0 dma 520192 in Sep 16 05:32:01 Tower kernel: res 51/40:00:81:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:32:01 Tower kernel: ata1.00: status: { DRDY ERR } Sep 16 05:32:01 Tower kernel: ata1.00: error: { UNC } Sep 16 05:32:02 Tower kernel: ata1.00: configured for UDMA/133 Sep 16 05:32:02 Tower kernel: ata1: EH complete Sep 16 05:32:04 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:32:04 Tower kernel: ata1.00: port_status 0x20200000 Sep 16 05:32:04 Tower kernel: ata1.00: failed command: READ DMA EXT Sep 16 05:32:04 Tower kernel: ata1.00: cmd 25/00:f8:f7:4a:38/00:03:3a:00:00/e0 tag 0 dma 520192 in Sep 16 05:32:04 Tower kernel: res 51/40:00:81:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:32:04 Tower kernel: ata1.00: status: { DRDY ERR } Sep 16 05:32:04 Tower kernel: ata1.00: error: { UNC } Sep 16 05:32:04 Tower kernel: ata1.00: configured for UDMA/133 Sep 16 05:32:04 Tower kernel: ata1: EH complete Sep 16 05:32:04 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:32:04 Tower kernel: ata5.00: BMDMA stat 0x24 Sep 16 05:32:04 Tower kernel: ata5.00: failed command: READ DMA EXT Sep 16 05:32:04 Tower kernel: ata5.00: cmd 25/00:00:f7:4a:38/00:04:3a:00:00/e0 tag 0 dma 524288 in Sep 16 05:32:04 Tower kernel: res 51/40:00:71:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:32:04 Tower kernel: ata5.00: status: { DRDY ERR } Sep 16 05:32:04 Tower kernel: ata5.00: error: { UNC } Sep 16 05:32:04 Tower kernel: ata5.00: configured for UDMA/133 Sep 16 05:32:04 Tower kernel: ata5: EH complete Sep 16 05:32:07 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:32:07 Tower kernel: ata1.00: port_status 0x20200000 Sep 16 05:32:07 Tower kernel: ata1.00: failed command: READ DMA EXT Sep 16 05:32:07 Tower kernel: ata1.00: cmd 25/00:f8:f7:4a:38/00:03:3a:00:00/e0 tag 0 dma 520192 in Sep 16 05:32:07 Tower kernel: res 51/40:00:81:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:32:07 Tower kernel: ata1.00: status: { DRDY ERR } Sep 16 05:32:07 Tower kernel: ata1.00: error: { UNC } Sep 16 05:32:07 Tower kernel: ata1.00: configured for UDMA/133 Sep 16 05:32:07 Tower kernel: ata1: EH complete Sep 16 05:32:09 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:32:09 Tower kernel: ata5.00: BMDMA stat 0x24 Sep 16 05:32:09 Tower kernel: ata5.00: failed command: READ DMA EXT Sep 16 05:32:09 Tower kernel: ata5.00: cmd 25/00:00:f7:4a:38/00:04:3a:00:00/e0 tag 0 dma 524288 in Sep 16 05:32:09 Tower kernel: res 51/40:00:71:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:32:09 Tower kernel: ata5.00: status: { DRDY ERR } Sep 16 05:32:09 Tower kernel: ata5.00: error: { UNC } Sep 16 05:32:09 Tower kernel: ata5.00: configured for UDMA/133 Sep 16 05:32:09 Tower kernel: ata5: EH complete Sep 16 05:32:10 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:32:10 Tower kernel: ata1.00: port_status 0x20200000 Sep 16 05:32:10 Tower kernel: ata1.00: failed command: READ DMA EXT Sep 16 05:32:10 Tower kernel: ata1.00: cmd 25/00:f8:f7:4a:38/00:03:3a:00:00/e0 tag 0 dma 520192 in Sep 16 05:32:10 Tower kernel: res 51/40:00:81:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:32:10 Tower kernel: ata1.00: status: { DRDY ERR } Sep 16 05:32:10 Tower kernel: ata1.00: error: { UNC } Sep 16 05:32:10 Tower kernel: ata1.00: configured for UDMA/133 Sep 16 05:32:10 Tower kernel: ata1: EH complete Sep 16 05:32:12 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:32:12 Tower kernel: ata5.00: BMDMA stat 0x24 Sep 16 05:32:12 Tower kernel: ata5.00: failed command: READ DMA EXT Sep 16 05:32:12 Tower kernel: ata5.00: cmd 25/00:00:f7:4a:38/00:04:3a:00:00/e0 tag 0 dma 524288 in Sep 16 05:32:12 Tower kernel: res 51/40:00:71:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:32:12 Tower kernel: ata5.00: status: { DRDY ERR } Sep 16 05:32:12 Tower kernel: ata5.00: error: { UNC } Sep 16 05:32:12 Tower kernel: ata5.00: configured for UDMA/133 Sep 16 05:32:12 Tower kernel: ata5: EH complete Sep 16 05:32:13 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 16 05:32:13 Tower kernel: ata1.00: port_status 0x20200000 Sep 16 05:32:13 Tower kernel: ata1.00: failed command: READ DMA EXT Sep 16 05:32:13 Tower kernel: ata1.00: cmd 25/00:f8:f7:4a:38/00:03:3a:00:00/e0 tag 0 dma 520192 in Sep 16 05:32:13 Tower kernel: res 51/40:00:81:4e:38/40:00:3a:00:00/e0 Emask 0x9 (media error) Sep 16 05:32:13 Tower kernel: ata1.00: status: { DRDY ERR } Sep 16 05:32:13 Tower kernel: ata1.00: error: { UNC } Sep 16 05:32:13 Tower kernel: ata1.00: configured for UDMA/133 Sep 16 05:32:13 Tower kernel: sd 0:0:0:0: [sda] Unhandled sense code Sep 16 05:32:13 Tower kernel: sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Sep 16 05:32:13 Tower kernel: sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Sep 16 05:32:13 Tower kernel: Descriptor sense data with sense descriptors (in hex): Sep 16 05:32:13 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Sep 16 05:32:13 Tower kernel: 3a 38 4e 81 Sep 16 05:32:13 Tower kernel: sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4 Sep 16 05:32:13 Tower kernel: sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 3a 38 4a f7 00 03 f8 00 Sep 16 05:32:13 Tower kernel: end_request: I/O error, dev sda, sector 976768641 Sep 16 05:32:13 Tower kernel: ata1: EH complete Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768576/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768576 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768584/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768584 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768592/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768592 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768600/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768600 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768608/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768608 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768616/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768616 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768624/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768624 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768632/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768632 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768640/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768640 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768648/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768648 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768656/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768656 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768664/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768664 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768672/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768672 Sep 16 05:32:17 Tower kernel: md: disk2 read error Sep 16 05:32:17 Tower kernel: handle_stripe read error: 976768680/2, count: 1 Sep 16 05:32:17 Tower kernel: md: parity incorrect: 976768680 Sep 16 05:32:19 Tower kernel: md: sync done. time=11943sec rate=40893K/sec Sep 16 05:32:19 Tower kernel: md: recovery thread sync completion status: 0
September 16, 201015 yr Those are un-readable sectors on that disk. Did you pre-clear the disk with those errors uising the preclear_disk.sh script? (Just curious, as it typically will find the bad sectors before you put the disk in the array) I'd get a smart report on that disk to see its current health, and to allow you to compare it in a week/month/year to see if it is constantly re-allocating sectors. smartctl -d ata -a /dev/sda Look specifically for re-allocated sectors and sectors pending re-allocation. Odds are the sectors are already re-allocated and were re-written by unRAID's OS with the contents re-constituted from parity in combination with the other data drives.
September 16, 201015 yr Author I didn't run the preclear script--can I run it now or will it wipe everything? The smartctl -d shows the same error (for the last 5 errors) : Error 8 occurred at disk power-on lifetime: 28334 hours (1180 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 40 17 4c 38 e0 Error: UNC 64 sectors at LBA = 0x00384c17 = 3689495 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 40 17 4c 38 3a 00 19:05:55.104 READ DMA EXT 27 00 00 00 00 00 00 00 19:05:55.104 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 00 00 19:05:55.083 IDENTIFY DEVICE ef 03 46 00 00 00 00 00 19:05:55.064 SET FEATURES [set transfer mode] 27 00 00 00 00 00 00 00 19:05:55.064 READ NATIVE MAX ADDRESS EXT but what the heck does that mean? thanks! rwc
September 16, 201015 yr I didn't run the preclear script--can I run it now or will it wipe everything? It will erase everything on the drive. You cannot run it on a drive already assigned to the array. The smartctl -d shows the same error (for the last 5 errors) : Error 8 occurred at disk power-on lifetime: 28334 hours (1180 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 40 17 4c 38 e0 Error: UNC 64 sectors at LBA = 0x00384c17 = 3689495 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 40 17 4c 38 3a 00 19:05:55.104 READ DMA EXT 27 00 00 00 00 00 00 00 19:05:55.104 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 00 00 19:05:55.083 IDENTIFY DEVICE ef 03 46 00 00 00 00 00 19:05:55.064 SET FEATURES [set transfer mode] 27 00 00 00 00 00 00 00 19:05:55.064 READ NATIVE MAX ADDRESS EXT but what the heck does that mean? thanks! rwc You did not post the ENTIRE smartctl output as requested. Specifically those lines describing re-allocated sectors and sectors pending re-allocation. UNC 64 sectors at LBA = 0x00384c17 UN-Correctable read errors a logical block address 0x00384c17
September 16, 201015 yr Author Sorry about not posting the whole thing--just thought I posted the "relevant" parts but as you can tell, I don't know much about this... Here's the whole thing: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Alle n Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Second Generation Serial ATA family Device Model: WDC WD5000AAKS-00TMA0 Serial Number: WD-WMAPW1143205 Firmware Version: 12.01C01 User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Sep 16 22:44:59 2010 Local time zone must be set--see zic m 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: (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: (12000) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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: ( 150) minutes. Conveyance self-test routine recommended polling time: ( 6) minutes. SCT capabilities: (0x103f) 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 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 180 166 021 Pre-fail Always - 5975 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 75 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 9 Power_On_Hours 0x0032 062 062 000 Old_age Always - 28340 10 Spin_Retry_Count 0x0012 100 253 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 253 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 73 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 72 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 76 194 Temperature_Celsius 0x0022 118 099 000 Old_age Always - 32 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 200 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 200 051 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 12 (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 12 occurred at disk power-on lifetime: 28334 hours (1180 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 40 17 4c 38 e0 Error: UNC 64 sectors at LBA = 0x00384c17 = 3689495 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 40 17 4c 38 3a 00 19:06:06.053 READ DMA EXT 27 00 00 00 00 00 00 00 19:06:06.053 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 00 00 19:06:06.032 IDENTIFY DEVICE ef 03 46 00 00 00 00 00 19:06:06.013 SET FEATURES [set transfer mode] 27 00 00 00 00 00 00 00 19:06:06.013 READ NATIVE MAX ADDRESS EXT Error 11 occurred at disk power-on lifetime: 28334 hours (1180 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 40 17 4c 38 e0 Error: UNC 64 sectors at LBA = 0x00384c17 = 3689495 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 40 17 4c 38 3a 00 19:06:03.355 READ DMA EXT 27 00 00 00 00 00 00 00 19:06:03.355 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 00 00 19:06:03.334 IDENTIFY DEVICE ef 03 46 00 00 00 00 00 19:06:03.316 SET FEATURES [set transfer mode] 27 00 00 00 00 00 00 00 19:06:03.316 READ NATIVE MAX ADDRESS EXT Error 10 occurred at disk power-on lifetime: 28334 hours (1180 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 40 17 4c 38 e0 Error: UNC 64 sectors at LBA = 0x00384c17 = 3689495 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 40 17 4c 38 3a 00 19:06:00.658 READ DMA EXT 27 00 00 00 00 00 00 00 19:06:00.658 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 00 00 19:06:00.637 IDENTIFY DEVICE ef 03 46 00 00 00 00 00 19:06:00.618 SET FEATURES [set transfer mode] 27 00 00 00 00 00 00 00 19:06:00.618 READ NATIVE MAX ADDRESS EXT Error 9 occurred at disk power-on lifetime: 28334 hours (1180 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 40 17 4c 38 e0 Error: UNC 64 sectors at LBA = 0x00384c17 = 3689495 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 40 17 4c 38 3a 00 19:05:57.801 READ DMA EXT 27 00 00 00 00 00 00 00 19:05:57.801 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 00 00 19:05:57.780 IDENTIFY DEVICE ef 03 46 00 00 00 00 00 19:05:57.761 SET FEATURES [set transfer mode] 27 00 00 00 00 00 00 00 19:05:57.761 READ NATIVE MAX ADDRESS EXT Error 8 occurred at disk power-on lifetime: 28334 hours (1180 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 40 17 4c 38 e0 Error: UNC 64 sectors at LBA = 0x00384c17 = 3689495 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 40 17 4c 38 3a 00 19:05:55.104 READ DMA EXT 27 00 00 00 00 00 00 00 19:05:55.104 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 00 00 19:05:55.083 IDENTIFY DEVICE ef 03 46 00 00 00 00 00 19:05:55.064 SET FEATURES [set transfer mode] 27 00 00 00 00 00 00 00 19:05:55.064 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 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.
September 16, 201015 yr Very interesting in that there are no sectors re-allocated and none pending re-allocation, indicating to me that when unRAID wrote the re-constructed contents back to the disk it was able to successfully write the original sector locations.
September 16, 201015 yr Author So should I worry? Reformat the drives and see what happens? (I'm just "learning" at this point so I won't lose any "important" data.)'
September 16, 201015 yr So should I worry? Reformat the drives and see what happens? (I'm just "learning" at this point so I won't lose any "important" data.)' No, re-formatting is not something you do on Linux to fix problems.. (actually it does not help on windows either, but that is a whole different subject as it just hides problems) It indicates the server fixed itself. Just use the server and keep an eye on the error counters on the management web-interface. A poor "write" could have been cause by nearly anything. Vibration, power supply regulation, or a drive issue internally. The fact that it was able to be successfully re-written in place is good.
September 17, 201015 yr You may have had a loose cable while you "I've just been testing and "playing" with the whole unraid thing" six hours ago - this HD reports 28340 power on hours and the visible errors are at the 28334 hours mark.
October 4, 201015 yr This is the classic symptom of a bad connection from the computer to the drive. The drive is reporting no reallocated sectors, but is logging a bunch of messages complaining about commands it does not understand. It likely is a bad or loose SATA cable, but could be something more serious.
October 8, 201015 yr This is the classic symptom of a bad connection from the computer to the drive. ... It likely is a bad or loose SATA cable, but could be something more serious. I have had to return 5 (out of 6) drives I bought in the past few months to WD for irrepairable bad sectors... and the way I found out was from similar errors in my syslog. Then I removed the offending drive (one at a time of course so my array was still intact) and tested them with WDC's Data LifeGuard Diagnostics software on Windows. It confirmed in each case that the drives had bad sectors. Then when I tried to use the software to "repair" (should read re-allocate) the bad sectors, it claimed it could not, and that I should contact the manufacturer. So if you're not having issues with cables and connectors (check power and data both for solid connections and cable integrity) then it just may be irrepairable bad sectors.
Archived
This topic is now archived and is closed to further replies.