February 26, 201016 yr Hi, Just got home from work and gone to copy some files across to my server and hit an error. When I went to copy a file across to one of the drives Teracopy got about 1/2 way through a threw up an error about the network resource being unavailable. Went back to my windows explorer window and the drive was unaccessible from the map'd location. Went to the unraid UI and that drive is red-balled. On top of that the UI is going very slow. I stopped and powered down the array and pulled out the drive from the hotswap bay. Blew a bit of dust away but there was no sign of obvious damage. Put the drive back in and turned on the server and it took ages for the system to boot up. Kept trying to access that drive over and over and over.. Attached is my syslog and below is a copy of one of the attempts to access the drive. Does it look like my drive has died or could it be something as simple as a dodgy sata cable? the system has been working fine for ~3 months with no errors on that drive. Just happened today all of a sudden. Feb 26 20:47:07 TheBurrow kernel: res 41/40:00:bf:00:00/82:00:00:00:00/40 Emask 0x409 (media error) <F> Feb 26 20:47:07 TheBurrow kernel: ata12.00: status: { DRDY ERR } Feb 26 20:47:07 TheBurrow kernel: ata12.00: error: { UNC } Feb 26 20:47:07 TheBurrow kernel: ata12.00: configured for UDMA/133 Feb 26 20:47:07 TheBurrow kernel: ata12: EH complete Feb 26 20:47:07 TheBurrow kernel: sd 12:0:0:0: [sdm] 1953523055 512-byte hardware sectors (1000204 MB) Feb 26 20:47:07 TheBurrow kernel: sd 12:0:0:0: [sdm] Write Protect is off Feb 26 20:47:07 TheBurrow kernel: sd 12:0:0:0: [sdm] Mode Sense: 00 3a 00 00 Feb 26 20:47:07 TheBurrow kernel: sd 12:0:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 26 20:47:07 TheBurrow kernel: ata12.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Feb 26 20:47:07 TheBurrow kernel: ata12.00: irq_stat 0x40000008 Feb 26 20:47:07 TheBurrow kernel: ata12.00: cmd 60/a8:00:60:00:00/00:00:00:00:00/40 tag 0 ncq 86016 in System specs are as follows: Asus P5Q-Deluxe - AHCI mode enabled E6400 (currently underclocked to 1.6ghz) 2gb G.Skill Ram 2xAdapatec 1430SA cards - BIOS disabled. Seasonic M12-700W PSU Lian Li PC-A17B 3xNorco SS-500 5in3 hotswap modules Lexar JumpDrive Firefly 4gb Unraid 4.4.2 The drive causing issues is a WD10EACS 1TB and is connected to the motherboard not to the adaptec's. I'm not copying anything further to the array or doing anything at all with it in case it screws up the parity. Any help/advise on where to go from here would be GREATLY appreciated... syslog.zip
February 26, 201016 yr Hi, Just got home from work and gone to copy some files across to my server and hit an error. When I went to copy a file across to one of the drives Teracopy got about 1/2 way through a threw up an error about the network resource being unavailable. Went back to my windows explorer window and the drive was unaccessible from the map'd location. Went to the unraid UI and that drive is red-balled. On top of that the UI is going very slow. I stopped and powered down the array and pulled out the drive from the hotswap bay. Blew a bit of dust away but there was no sign of obvious damage. Good that you powered down before removing the disk, bad that you did not capture a syslog BEFORE you powered down. We'll never know exactly how the initial "write" to the disk failed (and subsequently took it off-line). Put the drive back in and turned on the server and it took ages for the system to boot up. Kept trying to access that drive over and over and over.. Attached is my syslog and below is a copy of one of the attempts to access the drive. Does it look like my drive has died or could it be something as simple as a dodgy sata cable? the system has been working fine for ~3 months with no errors on that drive. Just happened today all of a sudden. Feb 26 20:47:07 TheBurrow kernel: res 41/40:00:bf:00:00/82:00:00:00:00/40 Emask 0x409 (media error) <F> Feb 26 20:47:07 TheBurrow kernel: ata12.00: status: { DRDY ERR } Feb 26 20:47:07 TheBurrow kernel: ata12.00: error: { UNC } Feb 26 20:47:07 TheBurrow kernel: ata12.00: configured for UDMA/133 Feb 26 20:47:07 TheBurrow kernel: ata12: EH complete Feb 26 20:47:07 TheBurrow kernel: sd 12:0:0:0: [sdm] 1953523055 512-byte hardware sectors (1000204 MB) Feb 26 20:47:07 TheBurrow kernel: sd 12:0:0:0: [sdm] Write Protect is off Feb 26 20:47:07 TheBurrow kernel: sd 12:0:0:0: [sdm] Mode Sense: 00 3a 00 00 Feb 26 20:47:07 TheBurrow kernel: sd 12:0:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 26 20:47:07 TheBurrow kernel: ata12.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Feb 26 20:47:07 TheBurrow kernel: ata12.00: irq_stat 0x40000008 Feb 26 20:47:07 TheBurrow kernel: ata12.00: cmd 60/a8:00:60:00:00/00:00:00:00:00/40 tag 0 ncq 86016 in System specs are as follows: Asus P5Q-Deluxe - AHCI mode enabled E6400 (currently underclocked to 1.6ghz) 2gb G.Skill Ram 2xAdapatec 1430SA cards - BIOS disabled. Seasonic M12-700W PSU Lian Li PC-A17B 3xNorco SS-500 5in3 hotswap modules Lexar JumpDrive Firefly 4gb Unraid 4.4.2 The drive causing issues is a WD10EACS 1TB and is connected to the motherboard not to the adaptec's. I'm not copying anything further to the array or doing anything at all with it in case it screws up the parity. Any help/advise on where to go from here would be GREATLY appreciated... UNC errors are typically media errors (a failing disk, not a cable). The only way to know for sure is to get a SMART report for the drive. Please post the output of smartctl -a -d ata /dev/sdm I'm expecting to see a lot of re-allocated sectors and sectors pending re-allocation. In the interim, DO NOT PRESS the button labeled as "Restore." when starting the array. If you do, you will lose the contents of the failed drive and you will have explicitly asked it to invalidate the contents of the parity drive. If the smart report shows a drive that is starting to fail you will need to replace that drive. When you install the new drive make sure you use the "Start" button to begin the reconstruction of data onto the replacement drive. Again, DO NOT PRESS RESTORE. Also, while the array is in a degraded state, do not make changes to the disk assignments. When you replace the drive, as long as it is on the same controller port it should be detected automatically and assigned to the correct slot in the array when you then Start it. (If you use a different disk controller port you will need to assign it on the devices page, but you still will use the "Start" button to reconstruct the old drive contents onto the new.) Until you replace that drive you are in danger of losing data if another drive were to concurrently fail. Don't wait weeks before replacing the drive if it has failed. Now is not the time to wait for a sale. Joe L.
February 26, 201016 yr Author Thanks for the quick reply Joe. Yeah unfortunately I didnt think to grab the syslog before i shut it down.. fool that i am sometimes.. Below is the content of the smartctl report. Doesnt seem to be an reallocated sectors? I havent manually started the array yet so havent pressed restore. I'm just looking at the system as it is after powering back on and auto starting. I'll be ducking out after breakfast to get a replacement drive. Thankfully it happened last night and not tonight coz all the computer stores near me are closed tomorrow. smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD10EACS-00ZJB0 Serial Number: WD-WMASJ0001426 Firmware Version: 01.01B01 User Capacity: 1,000,203,804,160 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Feb 27 06:46:11 2010 GMT-10 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: ( 780) 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: ( 15) minutes. Conveyance self-test routine recommended polling time: ( 6) minutes. SCT capabilities: (0x303f) 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 185 177 021 Pre-fail Always - 7716 4 Start_Stop_Count 0x0032 096 096 000 Old_age Always - 4322 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 189 189 051 Old_age Always - 109 9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 14012 10 Spin_Retry_Count 0x0012 100 100 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 - 60 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 4322 194 Temperature_Celsius 0x0022 122 093 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 1 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: 33 (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 33 occurred at disk power-on lifetime: 14003 hours (583 days + 11 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 c6 53 4f c2 00 Device Fault; 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 d8 00 01 4f c2 00 08 00:25:37.034 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:07:42.199 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:07:02.650 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:40.207 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:31.562 SMART ENABLE OPERATIONS Error 32 occurred at disk power-on lifetime: 14002 hours (583 days + 10 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 61 c6 53 4f c2 00 Device Fault; 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 d8 00 01 4f c2 00 08 00:07:42.199 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:07:02.650 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:40.207 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:31.562 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:22.917 SMART ENABLE OPERATIONS Error 31 occurred at disk power-on lifetime: 14002 hours (583 days + 10 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 61 c6 53 4f c2 00 Device Fault; 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 d8 00 01 4f c2 00 08 00:07:02.650 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:40.207 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:31.562 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:22.917 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:12.452 SMART ENABLE OPERATIONS Error 30 occurred at disk power-on lifetime: 14002 hours (583 days + 10 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 61 c6 53 4f c2 00 Device Fault; 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 d8 00 01 4f c2 00 08 00:06:40.207 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:31.562 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:22.917 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:12.452 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:02.692 SMART ENABLE OPERATIONS Error 29 occurred at disk power-on lifetime: 14002 hours (583 days + 10 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 61 c6 53 4f c2 00 Device Fault; 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 d8 00 01 4f c2 00 08 00:06:31.562 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:22.917 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:12.452 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:06:02.692 SMART ENABLE OPERATIONS b0 d8 00 01 4f c2 00 08 00:05:51.546 SMART ENABLE OPERATIONS 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 27, 201016 yr Author just got back from store with the new drive.. had to wait at store for an extra hour for roadside assistance after car battery was flat when i came back out.. sigh.. not my day.. put the new samsung HD103SI drive in and powered up.. it detected the disc straight away and i ticked I am sure and Start and its currently underway rebuilding as we speak.. will report back in 400 minutes with the results of the rebuild..
February 27, 201016 yr Author array rebuild finished. Just tested a few of the video files and all looks good.. havent seen any errors or anything.. took approx 5.5 hours to reconstruct the 1tb drive so pretty happy with that.. fingers crossed its all good now.. thanks for the help Joe..
Archived
This topic is now archived and is closed to further replies.